Natural language fleet control.
103 tools. Zero clicks.
Carrier MCP is a Cloudflare-hosted Model Context Protocol server that exposes every OCS operation as a natural-language tool. Connect your AI agent once; talk to every network indefinitely.
Every MVNO and eSIM brand eventually hits the same wall: the OCS API is powerful but unforgiving. Each operation requires knowing the exact method, the right parameter shape, and the error code taxonomy. That knowledge lives in a handful of engineers who become the bottleneck for every fleet change. Carrier MCP removes that bottleneck.
The server maps 43 OCS v1 methods and 8 intelligence composites to named, schema-validated MCP tools. An AI agent — Claude, GPT-4o, or anything that speaks MCP — can activate subscribers, assign packages, query usage, and run fleet reports entirely in natural language. No API console. No custom scripts. The operations your engineers used to script in an afternoon happen in a conversation.
The outcome is shorter ops cycles, fewer human-in-the-loop blockers, and a fleet that moves as fast as the prompts that drive it. Carrier MCP is the foundation every Carrier product surface builds on — the same 103 tools, the same auth, the same latency guarantee.
What you get
103 type-safe tools
43 OCS v1 methods + 8 intelligence composites. Read, write, and admin tiers. Zod v4 validated end-to-end.
450+ MNOs, 196 countries
Every activation, package assignment, and usage query routes through a single authenticated session.
Per-user token vault
OAuth 2.1 thin layer. Each user supplies their own eSIMVault credential — the server never holds a shared OCS key.
Scope tiers
Read-only tools are free forever. Write scope requires a connected account. Admin tools (balance, delete) need explicit flag.
StreamableHTTP transport
Stateful session via Cloudflare Durable Objects. Persistent tool context. Sub-200ms P50 latency.
Three install paths
Claude Desktop, mcp.json config, or .mcpb package from the R2 registry. Pick what fits your workflow.
Scope tiers
| Scope | Tools | Requirement |
|---|---|---|
| Read | 22 tools | Free — no account required |
| Write | 13 tools | Connected eSIMVault account |
| Admin | 8 tools | CARRIER_ADMIN_ENABLED flag + account |
| Intelligence | 8 composites | Write scope |
Three install paths
{
"mcpServers": {
"carrier": {
"url": "https://mcp.carrier.llc/mcp",
"headers": { "Authorization": "Bearer <your-token>" }
}
}
}claude mcp add --transport http carrier https://mcp.carrier.llc/mcp# Download from carrier R2 registry
curl -L https://registry.carrier.llc/carrier-mcp.mcpb -o carrier.mcpb
# Install locally
mcpb install ./carrier.mcpbSelf-hosted path keeps credentials on your infra. No outbound auth call to Carrier servers.
OAuth 2.1 + per-user token vault
Carrier MCP uses a thin OAuth 2.1 layer. You connect your eSIMVault account once; your credential is stored encrypted in an isolated KV namespace. The server never holds a shared OCS token — every tool call is authenticated with your own key, in your own scope. Admin tools require an additional explicit flag at server startup.
Use cases
MVNO ops automation
An ops agent activates a batch of ICCIDs, assigns regional packages, and notifies the subscriber — all from a single prompt. No dashboard open, no API console, no ticket.
Roaming fleet management
Ask 'which of our subscribers are actively roaming in Japan right now?' and get a live list with data balances. Filter, sort, and act on the output in the same conversation.
eSIM brand builders
A white-label eSIM brand provisions new subscribers, handles top-ups, and runs churn analysis — all driven by an AI layer that speaks plain English to the OCS.
Developer iteration
Test OCS method calls interactively before writing a single line of integration code. Carrier MCP is the fastest path from idea to working OCS integration.
The full picture is at mcp.carrier.llc
Tool reference, endpoint docs, auth walkthrough, and the MVNO operator playbook. Everything you need to go from zero to running fleet ops in an afternoon.
Go to mcp.carrier.llc