DocsClaude, ChatGPT & editors

Connect to Claude, ChatGPT and editors

Your workspace speaks the Model Context Protocol (MCP). Connect it once and you can ask about your agents, read conversations, check who is waiting for a human and add to a knowledge base — from inside Claude, ChatGPT or your editor, without opening the dashboard.

Anyone who would rather ask than open the dashboardNeeds an API key and an MCP client — Claude, ChatGPT or an editor5 minutes to connect

On this page

What you need#

  • An API key. Create one in the agent studio under Developer → API keys. It starts with sk_live_ and is shown once.
  • An MCP client: Claude Desktop, Claude Code, ChatGPT, Cursor, or anything else that speaks MCP.

The server address is:

Code
https://api.integrable.cloud/mcp

Claude Desktop#

Open Settings → Connectors → Add custom connector, paste the URL above, and give it your API key when prompted for a bearer token.

If you prefer to edit the config file directly, add this to claude_desktop_config.json:

claude_desktop_config.json
{
  "mcpServers": {
    "integrable-cloud": {
      "type": "http",
      "url": "https://api.integrable.cloud/mcp",
      "headers": {
        "Authorization": "Bearer sk_live_your_key_here"
      }
    }
  }
}

Restart Claude Desktop. The tools appear under the connector menu.

Claude Code#

terminal
claude mcp add --transport http integrable-cloud \
  https://api.integrable.cloud/mcp \
  --header "Authorization: Bearer sk_live_your_key_here"

Cursor, Windsurf and other editors#

Most editors read the same shape as Claude Desktop. Point them at https://api.integrable.cloud/mcp over HTTP transport with an Authorization: Bearer header.

What you can ask#

Once connected, these all work in plain language — the client picks the right tool:

  • “How many conversations did my agent have this week?”
  • “Did anyone ask about refunds in the last few days?”
  • “Is anybody waiting to talk to a human right now?”
  • “Why did my agent say that? Show me the transcript.”
  • “Add our opening hours to the knowledge base.”
  • “Am I close to my plan limit?”

The tools, precisely#

Nine tools, deliberately. Each one answers a question people actually ask:

ToolDoesNeeds scope
list_agentsEvery agent, with status and volumeagents:read
get_agentOne agent's full configuration and promptagents:read
search_conversationsFind conversations, searching inside transcriptsconversations:read
get_transcriptThe full message-by-message transcriptconversations:read
list_handoffsWho is waiting for a human, oldest firstconversations:read
list_knowledgeWhat an agent has been taughtdocuments:read
add_knowledgeTeach an agent something newdocuments:write
get_analyticsVolume, resolution rate, leads, topicsanalytics:read
get_usagePlan usage against limitsanalytics:read

What it will not do#

Eight of the nine tools only read. The one that writes, add_knowledge, adds text to a knowledge base and nothing else.

Publishing an agent, deleting anything, changing billing and managing your team all stay in the dashboard. Those are the actions where the review step that makes them safe is a screen showing you the whole picture — not a sentence in a chat.

Limiting what a connection can do#

An API key carries scopes, and the MCP connection can do exactly what the key can do — no more. If you want a connection that can read but never write, mint a read-only key and use that one.

Give each connection its own key. One key per device or per person means revoking a lost laptop does not disconnect everything else. Keys are revoked from Developer → API keys, and revocation takes effect on the next call.

Usage and limits#

MCP calls are ordinary API calls underneath, so they use the same allowances — there is no separate MCP quota to track. Reads cost no usage credits and are governed only by your key's rate limit. Anything that would consume credits through the API consumes the same credits through MCP.

If it will not connect#

  • “Authentication required” or a login loop. The credential must be an sk_live_ API key. A dashboard session token will be refused — it expires in minutes, so a connector built on one would die shortly after you set it up.
  • It worked, then stopped. The key was probably revoked or has expired. Check Developer → API keys and mint a new one.
  • A tool says it lacks a scope. The message names the scope. Create a key that includes it and reconnect.
  • The client sees no tools. Nearly always a missing or malformed Authorization header — the server advertises nothing until the connection authenticates.

Something unclear or missing? Tell us and we’ll fix it.