Carrier
Example conversation

Watch Carrier MCP run.

This is what a real Claude conversation looks like when it drives the Carrier MCP server. 125 type-safe tools, one auth, every MNO. No SDK glue. No swagger. Just plain English.

The terminal on the right is an illustrative scripted example — not a recorded session. Real responses depend on your eSIMVault fleet.

claude · carrier-mcp · exampleIllustrative
>Activate ICCID 89049032100012345678 in Japan with 5GB for 30 days.
*Calling carrier-mcp...
modify_subscriber_status{ "status": "active" }
assign_package{ "package_id": "jp_5gb_30d" }
Subscriber active on NTT Docomo JP.
Package: jp_5gb_30d · expires 2026-06-08.
>How much data did they use yesterday?
get_subscriber_usage{ "window": "24h" }
·0 MB used. Travel package activated — no traffic yet.
>
connected · mcp.carrier.llc
104 tools available · read+write
Tool surface
125type-safe MCP tools
  • Read62
  • Write42
  • Admin21
What you can ask

Six conversations that ship today.

Carrier MCP collapses dozens of OCS REST calls into a handful of high-level intents. Tap a card to see a real prompt.

  • Activate eSIM

    Provision a subscriber and assign a regional package in a single prompt.

  • Diagnose Subscriber

    Get a full health report on any line — registration, usage, balance, errors.

  • Fleet Health Report

    Aggregate health across thousands of subscribers in one pass.

  • Revenue Analysis

    Break down ARPU, churn, and package mix across the reseller tree.

  • Coverage Analysis

    Inspect which networks a package can attach to and where it falls back.

  • Bulk Operations

    Move populations of subscribers between packages, statuses, and accounts.

Try it yourself

Probe the live endpoint.

Drop in your own eSIMVault token, run the snippet, and Carrier will hand back the full tool manifest.

probe mcp.carrier.llc
curl -X POST https://mcp.carrier.llc/mcp \
  -H "Authorization: Bearer <your-esimvault-token>" \
  -H "Content-Type: application/json" \
  -d '{
    "jsonrpc": "2.0",
    "id": 1,
    "method": "tools/list"
  }'
Pass tools/list to introspect the full tool registry. Each tool is JSON-Schema typed and ready for any MCP-aware client.
Install in 30 seconds

One click, or one block.

Cursor and VS Code install from a link. Claude Code and Codex take the command below. Or copy the prompt and let an agent do the whole thing, verification included.

Step 0 · required

Create a Carrier account first. MCP tools need Clerk auth (OAuth) or an org API key — install configs alone will not work.

Step 1 · one click

Add to CursorAdd to VS Code

Cursor and VS Code install on click. Claude Code and Codex publish no install URL, so those buttons copy the exact command. “Copy prompt” hands any agent the install and a read-only check to prove it worked.

recommended · Clerk signs you in

# 1) Create a Carrier account (Google / GitHub / email)
#    → https://app.carrier.llc/sign-up?redirect_url=https%3A%2F%2Fapp.carrier.llc%2Fonboarding
#
# 2) Add the remote MCP server (Claude Code / Cursor / clients with OAuth)
claude mcp add --transport http carrier https://mcp.carrier.llc/mcp
#
# On first tool call your client opens OAuth:
#   mcp.carrier.llc/oauth/authorize → Clerk sign-in (Google/GitHub/email)
#   → consent → access token stored by the client
# No static eSIMVault token required for managed accounts.