Using COORDINATOR inside other AI apps (MCP)

Last updated: September 9, 2026

What this is

COORDINATOR runs an MCP (Model Context Protocol) server — a standard way for other AI apps to use your COORDINATOR account. Once connected, an agent like Claude, Codex, or Muse can read your chats, Studio workspaces, library, groups, and health/fitness activities, ask COORDINATOR questions on your behalf, and draft new workspace content for you to approve.

Per-client setup lives in its own guide:

• Claude (app, Desktop, and Code)
• Codex (CLI and IDE extension)
• Muse

This page covers what all of them share: keys, permissions, and safety.

Get a key

MCP access needs a Base subscription or higher — the key creation screen will point you at Billing if you're on the free plan. (Calls are re-checked server-side too, so downgrading pauses existing keys rather than leaving them live.)

Every connection authenticates with a personal API key. Keys are created in the app — never by email, never by support.

1. Sign in to COORDINATOR.
2. Go to Settings → Developer.
3. Under Connect via MCP, give the key a name (e.g. "Claude Code") and select Create MCP key.
4. Copy the key and the snippet for your client. The key is shown once — if you lose it, revoke it and make a new one.

One key per client is the norm (a "Claude Code" key, a "Codex" key). That way revoking one doesn't break the others, and the key list shows which client last used what.

What a key can do

MCP keys carry two coarse scopes, always together:

• Read — list and read chats, Studio workspaces, library items, groups, drafts, activities and wearable data, and integration status.
• Write — start chats, send messages (each one spends an engine turn), pull wearable history, and propose workspace changes.

Three things a key can never do:

1. Save silently. Workspace creates and edits come back as drafts. Nothing is saved until you approve the draft card in COORDINATOR — the same human-in-the-loop rule the in-app AI follows.
2. Spend for free. Every engine turn an external agent triggers counts against your plan quota exactly like a message you send yourself. MCP rate limits (60 requests per minute per key, at most two simultaneous turns) protect you from runaway clients.
3. Reach other people. A key sees only your account and the groups you belong to. Group reads respect the same visibility rules as the app.

What data is shared

Only what the connected agent actually uses: the chats, workspaces, library items, and group content it reads, plus the messages it sends. Integration data (wearables, Drive, Notion) is visible to it only the way it's visible to COORDINATOR itself — connected providers, never stored passwords or tokens.

Data you never touch through the agent is never sent. Revoking the key stops all access immediately (in-flight requests finish within about a minute).

Revoking a key

1. Go to Settings → Developer.
2. Find the key under API keys and revoke it.

The agent's side will start failing with authentication errors. Its own stored copy of your data (conversation history in that app) is governed by that app's terms — revoking here stops new access, it doesn't erase what you already discussed there.

Common issues

Key creation says I need a subscription

MCP keys require a Base subscription or higher. Upgrade in COORDINATOR Settings → Billing, then create the key. If you downgrade later, existing keys stop working until you resubscribe.

"Invalid API key" / 401 errors

The key was revoked, pasted incompletely, or the Authorization: Bearer … header didn't reach the server. Re-copy the key from a fresh creation (keys are shown once) and check the header spelling. Bearer tokens are case-sensitive and whitespace-sensitive.

The agent says it can't see a workspace or group

Keys see what you see. If the content is in a group, confirm you're a member of it, and for private shared items confirm they were shared with you. Personal content from a different account is never visible.

Rate limit errors

You're past 60 requests per minute on that key, or two turns are already running. Wait a minute and retry. If it happens constantly, the client is polling too aggressively — lengthen its retry interval.

I pasted my key somewhere public

Revoke it immediately in Settings → Developer and create a fresh one. Treat a posted key the way you'd treat a posted password.

Contact support

Email [email protected] from the address on your COORDINATOR account. Include which client you're connecting, the exact error text, and when it started. Never send us your API key — we will never ask for it.

For privacy questions, data export, or deletion requests, see Privacy Policy.