Connect your coding agent

Coworkkit runs an MCP server your coding agent (Claude Code, Cursor, or any MCP-capable client) can connect to. It gives your agent three things, in order of how much trust each needs: live docs with no account at all, then session diagnostics and small config changes for your own workspace after a one-time browser sign-in.

1 · Add the server

One command, then restart your agent so it picks up the new server:

claude mcp add coworkkit https://app.coworkkit.ai/api/mcp

In Cursor (or any client that edits a JSON config), point an HTTP MCP server at the same URL:

{
  "mcpServers": {
    "coworkkit": {
      "url": "https://app.coworkkit.ai/api/mcp"
    }
  }
}

2 · Ask for docs — no account needed

Straight away, with no sign-in, your agent can read the live documentation and the integration recipe. Ask it something like “using the Coworkkit MCP, add voice to this app” and it pulls the current getting-started guide (the same one you’re reading) through the get_docs and get_started tools. These stay in sync with the shipped docs automatically.

3 · Sign in once for your own workspace

The moment you ask your agent to do something workspace-specific — “why was my last session silent?” or “switch to the calmer voice” — it needs to act as you. Your client opens a browser to the Coworkkit portal, you sign in with your normal account, and you approve the connection on a consent screen. That’s the whole setup: there is no API key to paste anywhere. Your agent receives a short-lived, auto-rotating token; your secret key stays only in your backend, where it mints sessions.

After that one approval, your agent can:

• Diagnose sessions — check_setup, list_sessions, get_session, and diagnose_session read your session health (why a call was rejected, whether a mic ever published, connect rates).
• Adjust configuration — list_voices and update_config change the allowed settings (voice, language, greeting/persona text, timeouts). Config changes are marked high-impact, so your agent confirms with you before making one.

Everything is scoped to your own workspace and your own permissions — the agent can never reach another tenant’s data, delete your workspace, touch API keys, or spend credits.

4 · Revoke any time

Each connected agent is listed under Settings → Connected agents, with the date you approved it and when it was last used. Revoke one there and its access stops on the next call — to reconnect, your agent walks the browser sign-in again.