Connect your AI (MCP)

Every Jun desk serves an MCP server at /mcp. Connect your own AI to it and ask in plain words: it reads your agent, writes tasks and actions, builds cards, runs the tests and makes the change live. Each change is checked like a save on the desk and kept as a version you can restore. It’s the easiest way to edit with your own AI: nothing to clone or install, and the AI works on the live agent with the same checks the Agent page uses.

Connect

The quickest way is the MCP page in the desk’s sidebar: pick your app (Claude Code, Cursor, Codex or Others) and press its one button. It creates an API token named after the app and then copies the command or configuration, or for Cursor opens Cursor’s install prompt, with your address and the token filled in. The token is listed on the page’s API tokens tab, where you can revoke it. Its value is shown only there, once. To set it up by hand instead:

Create an API token

On MCP → API tokens, create a token. It acts as you, for this workspace’s agent only. Copy it: it’s shown once.

Add the server to your AI

Your MCP address is your desk’s address plus /mcp, like https://support.acme.com/mcp.

Claude Code
Cursor
Codex
Claude Desktop

claude mcp add --transport http jun https://support.acme.com/mcp \
  --header "Authorization: Bearer jun_…"

Then claude mcp list should show jun … ✔ Connected.

In .cursor/mcp.json (this project) or ~/.cursor/mcp.json (every project):

{
  "mcpServers": {
    "jun": {
      "url": "https://support.acme.com/mcp",
      "headers": { "Authorization": "Bearer jun_…" }
    }
  }
}

In ~/.codex/config.toml:

[mcp_servers.jun]
url = "https://support.acme.com/mcp"
bearer_token_env_var = "JUN_DESK_TOKEN"

and in the shell you start Codex from: export JUN_DESK_TOKEN=jun_….

Claude Desktop’s own connectors sign in with OAuth, which the desk doesn’t offer yet. Until then, use a local bridge such as mcp-remote in claude_desktop_config.json:

{
  "mcpServers": {
    "jun": {
      "command": "npx",
      "args": ["mcp-remote", "https://support.acme.com/mcp", "--header", "Authorization: Bearer jun_…"]
    }
  }
}

Ask

Try: “Add a refund task that looks up the order with our orders API (here’s the curl command from our docs: …), test it, and make it live.”

What you can ask for

The AI gets a guide to the agent’s files when it connects, and these tools. Tools that change something save a new version that’s live at once; each takes dryRun: true to show the result without saving, and message for the version’s line in History.

Group	Tools
The agent	`get_agent` (everything at a glance), `read_file`, `write_file`, `delete_file`, `check` (problems, no save), `history`, `restore`, `connections`
Instructions	`get_instructions`, `update_instructions` (the body, `maxReplies`, `handoffTopics`)
Tasks	`list_tasks`, `get_task`, `create_task`, `update_task`, `delete_task`, `task_uses` (its actions, whether they’re set up, their cards)
Actions	`list_actions`, `get_action`, `create_action`, `action_from_curl` (from your API docs), `update_action`, `delete_action`, `try_action` (one real call), `action_status`, `set_key`
Widgets	`list_widgets`, `get_widget`, `create_widget` (blank, your template, or a gallery one), `update_widget`, `delete_widget`, `widget_templates`, `get_widget_template`, `preview_widget` (problems, an outline of the card, what each button does, a link to see it), `widget_from_data` (a card from an example result)
Tests	`list_tests`, `get_tests`, `add_test_case`, `update_test_case`, `delete_test_case`, `run_tests` (the test cases; `replay: true` also replays recent conversations), `test_chat` (chat as a customer, press card buttons)
Your website	`website_actions` (what your site offers the agent), `set_website_action` (auto, confirm or human, and the line shown while it runs)
Desk settings	`get_desk_settings`, `update_desk_settings` (the AI’s switches, the chat widget, business hours, assignment; applied at once)

It can also read these resources: the file format (jun://guide/files), ChatKit’s widget authoring guide (jun://guide/chatkit-widgets), the Jinja filters widget templates can use (jun://guide/jinja) and every file of the live agent (jun://file/<path>).

Knowledge

The websites and documents the AI answers from (the desk’s Knowledge page) have their own tools. They do exactly what the Knowledge page does, with the same limits.

Tool	What it does
`list_knowledge`	Every source: type (website, page, file, text), URL or name, state (queued, crawling, indexing, ready, failed), pages and chunks, last sync, errors
`add_website`	Crawls a site, or one page with `maxPages: 1`. Answers at once; the crawl runs in the background
`add_document`	Adds a document: `name` plus `text` (plain text or Markdown), or `base64` and `filename` for a PDF, DOCX, Markdown or text file up to 10 MB. Indexed in the background
`resync_source`	Re-crawls a website or re-indexes a file, like the sync button
`remove_source`	Deletes a source and everything indexed from it. Needs `confirm: true`
`search_knowledge`	Runs a question through the same search the support AI uses and shows what it would find

Anyone’s token can list and search; adding, re-syncing and removing need an owner’s or admin’s.

Knowledge isn’t versioned: there’s no History or restore for it, and a removed source can’t be brought back. remove_source refuses until it’s called with confirm: true, and the AI is told to ask you first.

Some things to ask

“What does our agent do today? Anything broken?”
“When someone asks to cancel, offer the annual discount first, then hand off. Add a test for it.”
“Here’s our orders API: curl https://api.acme.com/v2/orders/1042 -H 'Authorization: Bearer sk_live_…'. Make an action that looks up an order, try it with order 1042, and show the result as a card.”
“Start from the ride status template for our delivery tracker and show me what its buttons do.”
“Change the chat widget’s greeting to ‘Hi! Ask us anything.’ and close on Sundays.”
“Run the tests. Fix what fails, but show me the change with a dry run first.”
“Can the AI answer ‘do you have an EU data center?’ from our docs? If not, add our security page.”

Safety

Keys are write-only. set_key (and action_from_curl, for a key in the command) stores a key on the desk; no tool ever returns it. Files only ever say {secrets.NAME}, and answers mask keys a request carried.
Nothing broken is saved. Each change is checked like a save on the desk; when the files have problems, nothing is saved and the AI gets the problems file by file.
Every change is a version. History on the Agent page shows the AI’s changes as Changed by an AI (MCP), with who owns the token. restore (or History on the desk) brings any version back.
Look before it’s live. dryRun: true shows the resulting file without saving; test_chat answers changes (POST actions) without making them unless you ask for real: true; run_tests with mockTools: true doesn’t call your APIs. try_action does make a real call.
Only the agent and its knowledge. A token reaches the agent’s config, its tests and the knowledge tools, nothing else: not the inbox, conversations or contacts. Reading needs any teammate’s token; changing needs an owner’s or admin’s. Revoke a token on MCP → API tokens at any time.

Your AI client usually asks before it calls a tool; keep that on for tools that change things.

How it works

The server is stateless MCP over Streamable HTTP (protocol versions 2025-11-25, 2025-06-18 and 2025-03-26): each request is one JSON-RPC message sent with POST, answered with JSON. It runs inside your desk’s Worker, so it’s on your Cloudflare account like the rest of Jun. A request without a valid token gets 401.

OAuth sign-in, for connectors in claude.ai and Claude Desktop without a bridge, is planned.

Get started

Deploy and run

Website widget

AI agent

Inbox and team

Agent as code

Reference

Connect your AI (MCP)

Connect

What you can ask for

Knowledge

Some things to ask

Safety

How it works

​Connect

​What you can ask for

​Knowledge

​Some things to ask

​Safety

​How it works

Connect

What you can ask for

Knowledge

Some things to ask

Safety

How it works