@carrierllc/mcp-intent

One MCP tool: create_connectivity_intent. It posts POST /v1/connectivity/intents through @carrierllc/sdk.

This process is not the operator server at https://mcp.carrier.llc/mcp. Connecting that server loads the fleet catalog. Connect this one when the task is a single eSIM.

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

Set CARRIER_API_KEY in that env block on the machine. Do not commit the key. Optional CARRIER_API_BASE_URL overrides https://api.carrier.llc.

test_global_1gb never calls the network. The same idempotency_key returns the original intent. npm can run carrier-intent after the connectivity release on main publishes this version. Until then, call the HTTP intent. The bin is carrier-intent, so the invocation is npx -y -p @carrierllc/mcp-intent carrier-intent.