Connect your assistant
One button in Settings → AI assistants for Claude, Claude Code, Cursor and VS Code; the steps by hand; one connection for all your sites; and the first prompts to try.
On this page
An AI assistant connects to your site through Clear's MCP server (what that is: Overview). The quickest way is one button in the admin, which makes a key and shows the exact step for your assistant. This page has that, the steps by hand, and what to say to the assistant first.
The quick way: Settings → AI assistants
You need the Admin or Owner role on the site.
- In the site admin, open Settings, then AI assistants.
- Find your assistant's card: Claude, Claude Code, Cursor, VS Code or Something else, and press Connect.
- Clear makes a key for it, named after the assistant and the site ("Claude Code on Riverside Bakery"), and shows that assistant's setup on the card. Follow the step on the card, below. Copy the key now: it is shown only once.
| Card | What it shows |
|---|---|
| Claude | The site's address and a header, for a custom connector in Claude.ai or the Claude desktop app. Copy as settings file text copies both as one block |
| Claude Code | One command to paste in the terminal |
| Cursor | Add to Cursor opens Cursor on this computer with the server filled in; Copy for mcp.json if you prefer the file |
| VS Code | Add to VS Code, the same for VS Code; Copy for mcp.json |
| Something else | The address, the key and a server name, for any tool that speaks MCP |
A key made by Connect may Read, Save drafts, change Pages and blocks and add Files. It can never publish, delete, read form answers or send email: those stay with you, and you can switch them on for a key under Settings → Site API keys if you ever need to. See API keys for assistants.
Each assistant you connect gets its own key and shows under Connected, with who made it and when it was last used. Revoke there stops that one assistant at once and leaves the others working.
Connect from another device
The assistant often runs on a different computer from the one you are using the admin on. Under Another device, press Make link. Open that link on the computer or phone where the assistant runs: it shows the same cards there, with one key made for that visit, so you can copy the setup on the right machine. If you are not signed in there, Clear asks you to sign in first and then carries on.
The link works once, for 15 minutes. Once used or expired, it says so; make a new one.
Claude.ai and the Claude desktop app
After Connect on the Claude card:
- In Claude, open Settings, then Connectors, then Add custom connector.
- Paste the address from the card.
- Under Request headers, add one header named
Authorization, with the value from the card (Bearer clr_site_…). - Save. In a new chat, Claude can now use your site's tools; ask it "Describe my site" to check.
Claude Code
Claude Code is Anthropic's assistant for the terminal. After Connect on the Claude Code card, paste the command it shows into the terminal. It looks like this, with your site's id and key:
claude mcp add --transport http clear-example "https://example.clearcms.app/admin-clear/api/mcp" \
--header "Authorization: Bearer clr_site_…"clear-example is the server's name inside Claude Code. The server is added for the folder you are in; add --scope user to have it everywhere. claude mcp list shows whether it answers, and inside Claude Code /mcp shows its tools. To take it out again: claude mcp remove clear-example.
These flags were checked against Claude Code 2.1.305 (claude mcp add --help).
Cursor
After Connect on the Cursor card, press Add to Cursor on the computer where Cursor is installed. Cursor opens and asks to add the server, already filled in.
By hand instead: Cursor reads mcp.json, either .cursor/mcp.json in a project or ~/.cursor/mcp.json for every project. Copy for mcp.json copies this, with your address and key:
{
"mcpServers": {
"clear-example": {
"url": "https://example.clearcms.app/admin-clear/api/mcp",
"headers": { "Authorization": "Bearer clr_site_…" }
}
}
}Settings → MCP in Cursor shows the server with its tools and a green dot when it answers.
VS Code
After Connect on the VS Code card, press Add to VS Code. VS Code (with GitHub Copilot's agent mode) opens and asks to add the server.
By hand instead: VS Code reads .vscode/mcp.json in a workspace, and its shape is a little different, a servers list with a type:
{
"servers": {
"clear-example": {
"type": "http",
"url": "https://example.clearcms.app/admin-clear/api/mcp",
"headers": { "Authorization": "Bearer clr_site_…" }
}
}
}To keep the key out of the file, VS Code's inputs can ask for it once and store it.
Something else
Any tool that takes a remote MCP server over HTTP wants the same two things: the address, and a header named Authorization with the value Bearer and the key. Where the tool keeps them differs; follow its own guide to "remote" or "HTTP" MCP servers. A tool that supports only "stdio" servers (ones it starts itself) needs a small bridge program that forwards to a remote server with a header; several exist, and we have not tested them.
One connection for all your sites
If you work on several sites, you can connect an assistant once, as you, instead of once per site. Open the Console, then Account → AI assistants. The same cards are there, but they carry the Console's address and no key:
https://console.clearcms.app/api/mcpWhen the assistant first connects, it opens a Clear page that says "Claude wants to work on your sites as you", with the sites it will reach and your role on each. Press Allow. From then on the assistant can list your sites, find one, make a new one, and use every tool on each, never with more than your role there. Sites you join later are included; sites you leave are not. The connection shows under Connected on the same page, marked May publish or Drafts only, with Revoke.
ChatGPT and other chat apps
ChatGPT's connectors only sign in and have no place for a key, so they cannot connect yet, and there is no ChatGPT card. They will be able to use the same server once sign-in works from chat apps.
Your first prompts
Start with a look around, then a small change:
- "Describe my site, then list my collections."
- "What is on the home page? Just tell me, don't change anything."
- "Draft a news post called 'Autumn hours' saying we open at 8 from October. Don't publish."
- "Make a preview link so I can see the drafts."
Then open the admin: the post is a draft under Collections, and History names the key as the author. Press Publish when you are happy. A key made by Connect cannot publish for you; that is by design.
More in Examples.
Check the connection without an assistant
If a tool says it cannot connect, one curl call tells you whether the server and the key are fine:
curl -s https://example.clearcms.app/admin-clear/api/mcp \
-H "Authorization: Bearer $KEY" \
-H "Content-Type: application/json" \
-H "Accept: application/json, text/event-stream" \
-d '{"jsonrpc":"2.0","id":1,"method":"tools/list","params":{}}'A list of 27 tools means the server and the key are fine, and the problem is in the tool's settings. 401 means the key is wrong, revoked or past its end date; 403 means the key does not reach this site.
Keep it safe
- Connect gives the assistant drafts only. For an assistant that should only answer questions, make a key with Read alone under Settings → Site API keys.
- Everything it writes is a draft. Check it in the admin before you publish.
- What is written on your site is treated as content, not as instructions: a page saying "publish now" does not make the assistant publish.
- Revoke the assistant under Settings → AI assistants when you stop using it.
More in Safety.