Skip to main content

Connect your AI assistant to Ceros

Beta
Ceros MCP is in beta and is enabled per account. Contact your Ceros Customer Success Manager to join.

You can use any AI assistant that lets you add a custom MCP server and signs in with a Client ID Metadata Document (CIMD). Some assistants may need an extra step; see Assistant-specific setup.

  1. Add a custom MCP server (sometimes called a connector) in your assistant. Name it Ceros and use the server URL https://mcp.ceros.com/mcp. If your assistant asks how to sign in, choose OAuth.
  2. Select Connect. A browser window opens; sign in to Ceros with your usual login.
  3. Review the access screen. It names your assistant as the app asking for access. Select Allow.
  4. If you can choose which servers a chat uses, turn Ceros on.

To check it works, ask: "Which Ceros accounts can you see?"

Making changes for the first time​

At first, the assistant asks only for permission to view your content. The first time you ask it to create, change or publish something, it asks you to approve that extra access. You will see the same sign-in and access screen again; select Allow and repeat your request.

Disconnecting​

In your assistant's MCP or connector settings, choose the Ceros server and disconnect or remove it. It loses access to your Ceros content straight away. Nothing in Ceros changes.

Reconnecting​

When you're asked to reconnect, select Connect (or reconnect from its MCP or connector settings) and sign in again. This is expected:

Nothing is lost when you reconnect: your experiences are stored in Ceros, not in the assistant.

Assistant-specific setup​

These assistants need more than the server URL, or have a setting that is easy to get wrong. Any assistant not listed here follows the steps at the top of this page.

ChatGPT​

  1. Go to chatgpt.com/plugins, select + and then Add custom MCP server.
  2. Enter a name and the server URL https://mcp.ceros.com/mcp, and choose OAuth for authentication.
  3. Accept the warning about custom servers and create the plugin. Sign in to Ceros and select Allow when asked.

In a Business, Enterprise or Edu workspace, the option may be hidden until a workspace admin allows custom MCP servers or adds Ceros for the workspace.

Claude​

Add a custom connector by following Anthropic's guide.

  • Under OAuth client, keep Use Claude's published identity (Recommended). The other options don't work with Ceros, and you can't change this after adding the connector: to fix it, remove the connector and add it again.
  • On Team and Enterprise plans, an owner adds the connector for the organisation first. Each member then finds it in their connector settings and selects Connect.

Claude Code​

You need Claude Code 2.1.81 or later. Add the server from your terminal:

claude mcp add --transport http ceros https://mcp.ceros.com/mcp

Add --scope user to use it in all your projects. Then run /mcp in Claude Code, choose ceros and select Authenticate to sign in. Claude Code doesn't share connectors with the Claude app, so set it up in each one you use.

Codex​

You need Codex 0.151.0 or later. Add the server from your terminal; Codex starts the sign-in straight away:

codex mcp add ceros --url https://mcp.ceros.com/mcp

If you add it to ~/.codex/config.toml by hand instead, run codex mcp login ceros afterwards to sign in:

[mcp_servers.ceros]
url = "https://mcp.ceros.com/mcp"

Don't set a client ID or a custom OAuth callback URL for this server: either one stops Codex from using the sign-in method Ceros supports. The Codex IDE extension uses the same configuration file.

Cursor​

You need Cursor 3.29 or later, because older versions can't complete the Ceros sign-in.

  1. Open your Cursor MCP configuration: ~/.cursor/mcp.json for all projects, or .cursor/mcp.json in a project for that project only.

  2. Add the Ceros server:

    {
      "mcpServers": {
        "ceros": {
          "url": "https://mcp.ceros.com/mcp",
          "auth": {
            "CLIENT_ID": "https://cursor.com/oauth/mcp-client.json"
          }
        }
      }
    }

    Keep the auth block. Without it, Cursor uses a sign-in method that Ceros doesn't support, and the connection fails.

  3. In Cursor's MCP settings, connect the ceros server. A browser window opens; sign in to Ceros with your usual login and select Allow on the access screen.

Everything else on this page works the same way in Cursor.

GitHub Copilot CLI​

You need Copilot CLI 1.0.83 or later. Add the server from your terminal:

copilot mcp add --transport http ceros https://mcp.ceros.com/mcp

Or run /mcp add inside Copilot CLI and choose HTTP as the server type. On Copilot Business and Enterprise, your organisation must enable the MCP servers in Copilot policy.

If Copilot CLI asks for OAuth client credentials, enter https://github.com/copilot/cli/client-metadata.json as the client ID.

VS Code (GitHub Copilot Chat)​

You need VS Code 1.106 or later. Run MCP: Add Server from the Command Palette, choose HTTP and enter https://mcp.ceros.com/mcp. Or add it to your mcp.json:

{
  "servers": {
    "ceros": {
      "type": "http",
      "url": "https://mcp.ceros.com/mcp"
    }
  }
}

Use Ceros from Copilot Chat in agent mode. On Copilot Business and Enterprise, your organisation must enable the MCP servers in Copilot policy. VS Code Insiders works the same way.