Connecting Muse to COORDINATOR (MCP)

Last updated: September 9, 2026

Before you start

You need an MCP key from Settings → Developer → Connect via MCP in COORDINATOR. If you don't have one, read Using COORDINATOR inside other AI apps first — key setup takes a minute.

Muse reads remote MCP servers from its MCP config file (mcp.json). The Settings → Developer card in COORDINATOR generates the exact block for you — paste it rather than typing it by hand.

Add the server

Open Muse's MCP settings (the mcp.json config file) and add COORDINATOR under mcpServers:

{
  "mcpServers": {
    "coordinator": {
      "url": "https://api.coordinator.co/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_KEY"
      }
    }
  }
}

Replace YOUR_KEY with your full coord_sk_live_… key, save, and restart Muse (or reload its MCP servers, if it offers that). COORDINATOR's tools — chats, Studio, library, groups, drafts — should appear in its tool list.

Prefer not to keep a secret in the file? Most setups expand ${VAR} references in config values:

{
  "mcpServers": {
    "coordinator": {
      "url": "https://api.coordinator.co/mcp",
      "headers": {
        "Authorization": "Bearer ${COORDINATOR_API_KEY}"
      }
    }
  }
}

with COORDINATOR_API_KEY exported in the environment that launches Muse.

What Muse can do once connected

Read and ask about your chats, Studio workspaces, library, and groups; check which integrations are connected; draft new documents, sheets, and apps for your approval. The full permission and quota picture is in the overview.

Common issues

The server won't connect / 401 errors

The header didn't arrive or the key is dead. Confirm the header name is exactly Authorization, the value is exactly Bearer plus the full key (one space, no extra quotes), the key still exists under Settings → Developer, and you restarted Muse after saving — most clients only read mcp.json at startup.

Tools don't appear after adding

Save the file, then fully restart the client. If they still don't show, validate the JSON — one trailing comma or a missing brace silently drops the whole file in many clients.

Rate limit errors

You're past 60 requests per minute on that key, or two turns are already running. Wait a minute and retry.

Contact support

Email [email protected] from the address on your COORDINATOR account with which client and version you're on, the exact error, and when it started. Never send your API key.