Carrier

llc.carrierPublished by carrier.llcOfficial publisherv0.13.89Updated Nov 17, 2026

Programmable eSIM and mobile connectivity: manage fleets, plans and orders from your agent.

VerifiedStreamable HTTPWeb executableCloud & InfrastructureBusiness & Commerce

Overview

AI-generated overview

Carrier lets an assistant manage programmable eSIM and mobile connectivity — fleets, plans and orders — through the Carrier API.

What you can do
  • Manage eSIM fleets, plans and orders for mobile connectivity
  • Use storefront management tools enabled by the Carrier API key
  • Use durable inventory tools such as package assignment with an API token
  • Call explicit OCS tools with a separate OCS API token
When to use it
Useful when you want an assistant to look after eSIM fleets, data plans or connectivity orders for devices and IoT deployments without switching to the Carrier dashboard.
Requirements
Runs as a remote endpoint or as a local npm package over stdio. OAuth is declared as required. At least one credential must be set or the server will not start: CARRIER_API_KEY (storefront tools), CARRIER_API_TOKEN (durable inventory tools) or CARRIER_OCS_API_TOKEN (OCS tools).
Before you install
The server handles several distinct secrets: CARRIER_API_KEY, CARRIER_API_TOKEN and CARRIER_OCS_API_TOKEN, the last being an OCS credential rather than a Carrier API credential. Tools can change fleets, plans, orders and inventory, so writes may affect live connectivity and billing. No tool list is published, so review the actual tools before granting access.

Installation

In SourceWeft

  1. Open Carrier in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/llc.carrier%2Fmcp/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "carrier": {
      "type": "http",
      "url": "https://mcp.carrier.llc/mcp"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v0.13.89LatestNov 17, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts

    Publish an icon in the registry entry.

  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.

Other Carrier integrations