CARRIER MCP

Carrier MCP — Documentation

Programmable connectivity for AI agents. Carrier exposes 161 natural-language tools over the Model Context Protocol, letting Claude and other MCP-aware clients manage MVNO and eSIM fleets without touching the underlying OCS REST API.

Quick Start

Carrier runs as a hosted MCP server at https://mcp.carrier.llc. Connect from Claude Desktop, Claude Code, the Claude API, or any MCP-compatible client.

Claude Desktop / Claude Code

{
  "mcpServers": {
    "carrier": {
      "url": "https://mcp.carrier.llc",
      "transport": "streamable-http"
    }
  }
}

On first connection, your MCP client redirects to /oauth/authorize. Sign in with your Carrier account, grant the requested scopes, and Claude receives a bearer token scoped to your reseller. No shared credentials — every user gets an isolated token vault.

Authentication

Carrier implements OAuth 2.1 with PKCE and RFC 7591 Dynamic Client Registration. MCP clients self-register at /register — there is no static client_id to provision.

Sign-in provider

Clerk-hosted at accounts.carrier.llc

Token transport

Bearer in Authorization header (HTTPS only)

Scopes

read, write, admin

MFA

Required for admin-scope grants (15-minute freshness)

Tool Catalog

161 tools total — split across reseller account management, package assignment, SIM status control, usage telemetry, and revenue analysis.

Bucket Count Scope Examples
Read 72 read list_reseller_accounts, get_account_data_usage, get_reseller_info
Write 53 write modify_account_package, suspend_account, activate_sim
Admin 20 admin (MFA-gated) modify_account_balance, delete_account
Intelligence 9 (in Read) read Server-side composites: get_revenue_breakdown, fleet_health_report

The canonical tool registry is maintained inside the Carrier monorepo; CI fails on any drift between the registry and the live server's tool exports. The /.well-known/mcp.json discovery manifest is the authoritative live source for connecting clients.

Tiers & Limits

Tier Calls / month Scopes Status
Free 1,000 read Available
Pro 100,000 credits read, write Waitlist
Enterprise Unlimited read, write, admin Contact sales

Example Prompts

Error Semantics

Carrier surfaces OCS-level errors as structured MCP tool errors — HTTP 200 from the upstream OCS does not imply success. The wrapper validates status.code === 0 on every response and rejects otherwise with the OCS error payload attached to the tool result.

Rate Limits & Quotas

Per-tier call quotas reset on the first day of each UTC month. Quota exhaustion returns a quota_exceeded error with retryAt set to the quota reset timestamp. Enterprise clients have custom limits configured per-account; contact support to adjust.

Support

Email support@carrier.llc for account, billing, integration help, and bug reports. We aim to respond within one business day.

Carrier is operated by Lifecycle Innovations Limited. Read the privacy policy for data handling details.