Run Coordinator from the AI you already use

ChatGPT

API-key connectors are a first-class, documented ChatGPT feature — no beta involved. You need a paid plan with developer mode on.

1. Open Settings → Connectors → Advanced and enable Developer mode.
2. Back in Connectors, choose Create and paste the server URL — exactly. A missing path segment is the most common cause of a connector that silently never connects.
3. For Authentication choose API key / custom header and enter the header below. Don't put the token in the URL.
4. Save, enable the connector in a chat, and ask “which invoices are overdue in Coordinator?”

https://www.coordinator.one/api/mcp

X-Coordinator-Token: cct_…your token…

Claude

Custom connectors exist on every Claude plan, including Free (one connector at a time there). No add-on, no extra API key — the assistant you already pay for does the thinking.

1. Open Settings → Connectors (Team/Enterprise: an owner adds it once under Organization settings → Connectors, members click Connect).
2. Choose Add custom connector and paste the server URL.
3. Under Advanced settings, add the request header below. Leave OAuth Client ID and Secret empty — Coordinator doesn't use OAuth.
4. Save, then ask Claude “what's unbilled in Coordinator?”

https://www.coordinator.one/api/mcp

Authorization: Bearer cct_…your token…

claude mcp add --transport http coordinator https://www.coordinator.one/api/mcp --header "Authorization: Bearer cct_…your token…"

Gemini CLI

The Gemini CLI takes a fixed header directly — one command, no beta, no OAuth, available in every session.

gemini mcp add --transport http coordinator https://www.coordinator.one/api/mcp --header "Authorization: Bearer cct_…your token…" --scope user

{
  "mcpServers": {
    "coordinator": {
      "httpUrl": "https://www.coordinator.one/api/mcp",
      "headers": { "Authorization": "Bearer cct_…your token…" }
    }
  }
}

The key is httpUrl, not url. In Gemini's config they select different transports — httpUrl is Streamable HTTP (what this server speaks); url is the older SSE transport (which it doesn't). The wrong one fails with an error that mentions neither.

Grok

The Grok CLI takes the header directly — same shape as the others. That's the path to use.

grok mcp add --transport http coordinator https://www.coordinator.one/api/mcp --header "Authorization: Bearer cct_…your token…"

[mcp_servers.coordinator]
url = "https://www.coordinator.one/api/mcp"
headers = { "Authorization" = "Bearer cct_…your token…" }

{
  "type": "mcp",
  "server_label": "coordinator",
  "server_url": "https://www.coordinator.one/api/mcp",
  "authorization": "cct_…your token…"
}

xAI sends authorization as the Bearer header itself — don't prefix the token.

Codex (OpenAI)

Codex reads MCP servers from its config file — one TOML block and the tools are available in the CLI and the IDE extension alike.

[mcp_servers.coordinator]
url = "https://www.coordinator.one/api/mcp"
http_headers = { "Authorization" = "Bearer cct_…your token…" }

Prefer keeping the token out of the file? Put it in an environment variable and use bearer_token_env_var = "COORDINATOR_TOKEN" instead of http_headers — Codex reads it at connect time and sends it as the Bearer header.

Antigravity (Google)

Antigravity's IDE, CLI and agent surfaces share one MCP config file. Reach it from the agent panel, or edit it directly.

1. In the editor's agent side panel, click … → MCP Servers → Manage MCP Servers → View raw config.
2. Add the block below and save. (The file lives at ~/.gemini/config/mcp_config.json, or per-workspace under .agents/mcp_config.json.)

{
  "mcpServers": {
    "coordinator": {
      "serverUrl": "https://www.coordinator.one/api/mcp",
      "headers": { "Authorization": "Bearer cct_…your token…" }
    }
  }
}

The key is serverUrl — Antigravity's name for a remote HTTP server. A plain url key won't connect.

Everything else

Any MCP client that speaks Streamable HTTP and can set a header works — Claude Desktop, Cursor, the MCP Inspector, and whatever ships next week.

{
  "mcpServers": {
    "coordinator": {
      "type": "http",
      "url": "https://www.coordinator.one/api/mcp",
      "headers": { "Authorization": "Bearer cct_…your token…" }
    }
  }
}

Two facts cover most integrations: the transport is Streamable HTTP, and authentication is a fixed bearer token in the Authorization header. If your client can express those, it can run Coordinator.