Home / AI / CMS Chat MCP Server

CMS Chat MCP Server

Connect your AI agent to your website. Read the site, change catalog content and wording, translate, and review the change log, right inside Claude, ChatGPT, Claude Code, Codex, Cursor and any other tool that supports MCP.

Set up in your agent See what you can do

What is the CMS Chat MCP Server

CMS Chat’s official server built on the Model Context Protocol, the open standard that lets AI agents use external services as tools. Add it once to your agent, sign in with your CMS Chat account, and the agent can work on your website on your behalf with exactly the tools and safety rules the built-in Copilot uses.

You are in control

OAuth 2.1 sign-in with your CMS Chat account. You choose the site the agent may touch and can revoke access any time.

Writes are previewed

Database changes are shown before they are applied and need your confirmation in the chat. Risky code edits become a review request.

Everything is logged

Every change lands in the change log under your name and can be undone in CMS Chat or through the agent.

What you can do

One connector, everything the Copilot can do, for site owners and agencies alike.

Site owner

Read the site: The site map: pages, sections, catalog entities, translatable fields and where each text lives.
Change catalog content: Products, services, articles, prices, availability, descriptions. Previewed first, applied after your yes.
Fix wording in pages: Headlines, paragraphs, buttons, message files across all languages in one go.
Translate: See which entries are missing a language and draft the translations in place.
Change log and undo: List what changed, by whom, and undo any database change.

Agency

Every client site from one connection: Pick a site per call, or bind the connection to one client.
Review requests: Edits outside the safe zones become an agency request instead of a silent change.
Personal tokens for automation: Headless machines and CI use a revocable token instead of the browser sign-in.

Shared across roles

Same guardrails as the Copilot: Zone classification, escalation and the read-before-edit rule are inside the tools, not in the client.
Attribution: Each change is recorded under the signed-in person with the client name that made it.
Revocation: Disconnect in the assistant or under Connect AI in CMS Chat. Immediate.

Set up in your agent

Server URL for every client: https://mcp.cmschat.ai. Sign in with your CMS Chat account when the client asks; no token to copy.

Claude (claude.ai and Claude Desktop)

Add as a custom connector

1.Open claude.ai/settings/connectors (in Claude Desktop: Settings → Connectors).
2.Click Add custom connector.
3.Name: cmschat · URL: https://mcp.cmschat.ai
4.Click Add, then Connect. cmschat opens: sign in, pick the site the AI may edit, click Allow.
5.In a chat, click + → Connectors and enable cmschat.

Plan requirements: Free plan allows one custom connector; Pro, Max, Team and Enterprise allow several. On Team/Enterprise an owner adds the connector under Organization settings → Connectors first, then each member connects.

ChatGPT

Add as a custom connector

1.In ChatGPT go to Settings → Connectors → Advanced and switch Developer mode on.
2.Back in Connectors, click Create.
3.Name: cmschat · Server URL: https://mcp.cmschat.ai · Authentication: OAuth.
4.Click Create, then Sign in. A browser window opens: sign in to cmschat, pick the site, click Allow.
5.In a new chat open the + menu → Connectors and turn cmschat on.

Plan requirements: Custom connectors need Plus, Pro, Team, Business or Enterprise and Developer mode. Set reasoning effort to Medium or High (Model → Effort); Instant does not call tools. On Business/Enterprise a workspace admin must enable Developer mode first.

Claude Code

Option A — Sign in (recommended)

1.Run the command below in your terminal.
2.Start claude and run /mcp to complete the sign-in in your browser.

Terminal

claude mcp add --transport http cmschat https://mcp.cmschat.ai

Option B — Personal token (headless machines, CI)

1.Create a personal token under Connect AI in your cmschat account, then run:

Terminal

claude mcp add --transport http cmschat https://mcp.cmschat.ai --header "Authorization: Bearer cms_your-token-here"

Codex (app and CLI)

Option A — CLI command

1.Run the two commands below. The second opens a browser window to sign in to cmschat.
2.Verify with /mcp inside Codex.

Terminal

codex mcp add cmschat --url https://mcp.cmschat.ai
codex mcp login cmschat

Option B — Edit ~/.codex/config.toml

1.Add the block below, save, then run codex mcp login cmschat.

~/.codex/config.toml

[mcp_servers.cmschat]
url = "https://mcp.cmschat.ai"

Cursor (app and CLI)

Option A — Via Settings

1.Open Cursor Settings → Tools & MCP → New MCP Server.
2.Add the block below under mcpServers and save.
3.Cursor shows cmschat with “Needs login”. Click it and complete the sign-in in your browser.

mcp.json

{
  "mcpServers": {
    "cmschat": {
      "url": "https://mcp.cmschat.ai"
    }
  }
}

Option B — Personal token instead of sign-in

1.For a shared or headless machine, use a token from Connect AI in your cmschat account:

~/.cursor/mcp.json

{
  "mcpServers": {
    "cmschat": {
      "url": "https://mcp.cmschat.ai",
      "headers": {
        "Authorization": "Bearer cms_your-token-here"
      }
    }
  }
}

Other MCP-compatible tools

Option A — Remote MCP server (Streamable HTTP)

1.Any agent that supports remote MCP servers with OAuth can connect with the URL below. Clients that only support stdio can bridge with mcp-remote.

Server URL

https://mcp.cmschat.ai

Option B — stdio bridge

1.For clients without remote-server support:

Command

npx mcp-remote https://mcp.cmschat.ai

Personal tokens for headless use are created under Connect AI in your account, where every snippet is pre-filled.

Common questions

FAQ

Do I need to be technical to use this?: No. If you can describe the change in a sentence, you can use it. There is nothing to configure beyond connecting once.
What does it cost?: Nothing extra. Connecting an assistant is included in every cmschat plan. Your assistant’s own subscription (Claude, ChatGPT, Cursor) is separate.
Can I connect cmschat to my own AI agent?: Yes. cmschat is a standard MCP server with OAuth 2.1. Any agent that supports remote MCP servers can connect with the server URL.
Can I still edit in cmschat the normal way?: Yes. This is another door, not a replacement. The workbench, the change log and your agency’s review flow work exactly the same.
Can the AI break my site?: It gets the same guarded tools as the built-in Copilot: safe zones it may edit directly, risky areas that turn into a review request for your agency, and system files it can never touch.
Does the AI decide what goes live?: No. Database changes are applied only after you confirm in the chat. Code changes land on a review branch, and your agency keeps the final say on anything risky.
Is my site data shared with OpenAI or Anthropic?: The assistant sees what it needs to answer your request: the site map, the records or files you ask about, and the result of each change. Credentials, tokens and your database keys never leave cmschat.
Does this work for an agency with several clients?: Yes. When you connect, you pick which site the assistant may work on, or all the sites you can access. Each client’s users connect with their own login and see only their sites.
How do I disconnect?: Remove the connector in your assistant, or revoke it under Connect AI in cmschat. Both take effect immediately.