Developer Documentation

Build with Carrier MCP

103 tools. 5 prompts. OAuth 2.1 + PKCE. One API your AI can talk to — every eSIM, subscriber, package, and network event.

Search docs… (coming soon)

Quick start

Install snippets for Claude Desktop, Claude Code, Cursor, Windsurf, and Smithery. Up in under 30 seconds.

All 103 tools with input schemas, scope requirements, and example invocations. Filterable by read / write / admin.

Carrier MCP runs at mcp.carrier.llc as a Cloudflare Worker with StreamableHTTP transport and Durable Object session state.

OAuth 2.1 + PKCE per-user token vault. Each user authenticates once; Carrier stores their eSIMVault token encrypted in KV.

Five production-ready prompt workflows: fleet_health_report, subscriber_deep_dive, revenue_optimization, coverage_analysis, bulk_operations_planner.

Version history. v0.1.0: first public release — 103 tools, 5 prompts, OAuth 2.1, npm @carrierllc/mcp.

Pick your AI client. Paste the snippet. Authenticate once via OAuth.

Claude Desktop

{
  "mcpServers": {
    "carrier": {
      "command": "npx",
      "args": ["-y", "@carrierllc/mcp"]
    }
  }
}

Claude Code

claude mcp add --transport http carrier https://mcp.carrier.llc/mcp

Cursor / Windsurf

{
  "mcpServers": {
    "carrier": {
      "command": "npx",
      "args": ["-y", "@carrierllc/mcp"]
    }
  }
}

Smithery

npx -y @smithery/cli install @carrierllc/mcp --client claude

After installing, type Run fleet_health_report in Claude to verify everything is connected.

Carrier uses OAuth 2.1 with PKCE. The flow:

01Your AI client initiates an OAuth flow to mcp.carrier.llc/oauth/authorize
02You log in and paste your eSIMVault API token. Carrier encrypts it and stores it in the CARRIER_USERS KV namespace — bound to your session.
03All subsequent tool calls use your stored token. Carrier never holds a shared OCS credential.

Carrier does not store your eSIMVault password — only the API token you explicitly provide. You can revoke access at any time by rotating your token.