MCP server

Overview

Inspra runs a remote MCP server: the same operations as the API reference, exposed as tools an AI assistant can call. Connect it once and you can ask an assistant to list agents, read call transcripts, check credits or pause a campaign, without writing a request by hand.

It suits work that is awkward in a dashboard and tedious in code — reading across many calls at once, or checking something quickly mid-task in your editor.

What you can do

Seventeen tools in total. Campaign creation, SMS and knowledge-base tools are not exposed yet — use the API or the dashboard for those.

How it works

The server is hosted at $BASE_URL/api/mcp and speaks Streamable HTTP. $BASE_URL is the address you use for the dashboard, so a white-label host works exactly the same way.

It authenticates with a workspace API key sent as a bearer token — the same key the API uses. A key resolves to exactly one workspace, so an assistant can only ever read and change that workspace. There is nothing to scope or misconfigure, and no way for a prompt to reach another workspace's data.

Your assistant fetches the tool list when it starts, which is why a configuration change needs a restart before it takes effect.

Before you start

• A workspace API key — Configuration → General → API Keys. See API keys.
• An MCP-capable assistant: Claude Code, Claude Desktop, Cursor, or any client that supports a remote Streamable HTTP server.
• The server URL: $BASE_URL/api/mcp.

Connect your client

Pick the tab for your client. Each does the same thing: point the client at $BASE_URL/api/mcp and send your key as a bearer token. Restart the client afterwards — every one of them reads its tool list at startup.

claude mcp add --scope user --transport http inspra $BASE_URL/api/mcp --header "Authorization: Bearer $API_KEY"

{
  "mcpServers": {
    "inspra": {
      "type": "http",
      "url": "$BASE_URL/api/mcp",
      "headers": { "Authorization": "Bearer $API_KEY" }
    }
  }
}

export INSPRA_API_KEY="<your key>"
codex mcp add inspra --url $BASE_URL/api/mcp --bearer-token-env-var INSPRA_API_KEY

[mcp_servers.inspra]
url = "$BASE_URL/api/mcp"
bearer_token_env_var = "INSPRA_API_KEY"

opencode mcp add inspra --url $BASE_URL/api/mcp --header "Authorization=Bearer $API_KEY"

{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "servers": {
      "inspra": {
        "type": "remote",
        "url": "$BASE_URL/api/mcp",
        "oauth": false,
        "headers": { "Authorization": "Bearer {env:INSPRA_API_KEY}" }
      }
    }
  }
}

{
  "mcpServers": {
    "inspra": {
      "type": "http",
      "url": "$BASE_URL/api/mcp",
      "headers": { "Authorization": "Bearer $API_KEY" }
    }
  }
}

What to ask

• Which of my agents are inactive?
• How did yesterday's calls go? Anything I should worry about?
• Show me the transcript of my longest call this week.
• What is my credit balance, and how much have I used this month?
• Pause the follow-up campaign.

Reading across calls is where it earns its keep: an assistant can open many transcripts at once and summarise what went wrong, which a dashboard does not do well.

Actions that cost money

Three tools are marked destructive, so a well-behaved client asks before running them.

Limits

• Page sizes clamp to 100, with a default of 20.
• Tool results are capped and truncate with a marker that says how much was dropped. list_calls therefore returns a summary of each call; use get_call for the transcript.
• Rate limits and credit checks are shared with the API and counted per workspace, not per key — an assistant and a server integration on the same workspace draw on the same allowance. See API keys.
• Requests are stateless: a tool returns as soon as the work is accepted. After resume_campaign, poll get_campaign for progress.

Troubleshooting