eSIMfly MCP Server已验证已精选

Listing URL: https://mcp.so/servers/esimfly-mcp Edit: mcp.so → My submissions → eSIMfly MCP. Paste each block into the matching field.

Description (one-line field)

Official MCP server for the eSIMfly Business API: search wholesale eSIM plans for 200+ countries, check balance and usage, diagnose eSIM connectivity from live network data, and (opt-in, with a confirmation step) order and top up eSIMs. Read-only by default.

Fields

• Type: MCP Server
• Project name: eSIMfly MCP
• Repository: https://github.com/eSimfly-Official/esimfly-mcp
• Website: https://esimfly.net/esim-api
• Docs (if separate field): https://docs.esimfly.net/docs/mcp-server
• Tags: esim, travel, telecom, connectivity, api, typescript, official

Config (JSON field)

{
  "mcpServers": {
    "esimfly": {
      "command": "npx",
      "args": ["-y", "@esimfly/mcp"],
      "env": {
        "ESIMFLY_ACCESS_CODE": "esf_...",
        "ESIMFLY_SECRET_KEY": "sk_..."
      }
    }
  }
}

Content (markdown field) — copy from the next line to the end of the file

What is eSIMfly MCP?

The official Model Context Protocol server for the eSIMfly Business API — the wholesale eSIM platform resellers use to sell travel data plans for 200+ countries. Once connected, Claude, Cursor, ChatGPT or any other MCP client can work with your eSIMfly account directly: search plans with your wholesale prices, check balance and usage, diagnose "no data" problems from live network data, and — only if you enable it — place orders and top-ups with an explicit confirmation step.

Published by eSIMfly (github.com/eSimfly-Official) and listed in the official MCP Registry as io.github.eSimfly-Official/esimfly-mcp. Built on the official @esimfly/sdk.

How to use eSIMfly MCP

1. Get API credentials from the eSIMfly Business Dashboard → Settings → API Keys (access code esf_… and secret key sk_…). Sign up at esimfly.net/esim-api.
2. Add the server to your client. The server runs locally over stdio, so your key never leaves your machine.

Claude Desktop (claude_desktop_config.json):

{
  "mcpServers": {
    "esimfly": {
      "command": "npx",
      "args": ["-y", "@esimfly/mcp"],
      "env": {
        "ESIMFLY_ACCESS_CODE": "esf_...",
        "ESIMFLY_SECRET_KEY": "sk_..."
      }
    }
  }
}

Claude Code:

claude mcp add esimfly -e ESIMFLY_ACCESS_CODE=esf_... -e ESIMFLY_SECRET_KEY=sk_... -- npx -y @esimfly/mcp

Cursor / Windsurf / other clients: the same command / args / env block in the client's mcp.json.

3. Ask your assistant things like:
   • "Find the cheapest 5 GB plan for Turkey and tell me my margin at €9.99."
   • "Which of my eSIMs are active and below 200 MB?"
   • "ICCID 8948010010036785060 says no data — diagnose it."
   • "Build me a Node.js integration for eSIMfly." (uses the built-in integration-guide prompt)
4. To allow orders, top-ups, cancellations, SMS and webhook changes, add "ESIMFLY_MCP_ALLOW_WRITES": "true" to env. Without it, those tools are not even registered.

Key features of eSIMfly MCP

• 11 read tools: search_packages (catalogue with your cost price), get_balance, list_esims, get_esim_usage, get_esim_live_status (live from the network: install state, last network, device, IMEI, usage), get_network_events (7-day attach/data-session log with wrong-network flag), get_usage_report (daily usage by country and operator), list_orders, get_order, get_topup_packages, get_webhook_settings.
• 7 opt-in write tools: create_order, topup_esim, cancel_esim, suspend_esim, activate_esim, send_sms, set_webhook.
• Read-only by default. Nothing can spend your balance unless you set ESIMFLY_MCP_ALLOW_WRITES=true.
• Two-step writes. Every write tool returns a preview — package, cost, current balance — until it is called again with confirm: true. create_order also requires the idempotency key from its own preview, so an agent can never place the same order twice.
• Safety annotations. Reads are marked readOnlyHint; cancel and suspend are marked destructiveHint, so MCP hosts that ask for approval on risky tools do so.
• Two prompts: esimfly_integration_guide — the complete, always-current prompt for building an eSIMfly integration (fetched live from docs.esimfly.net) — and diagnose_esim — a guided "no data" troubleshooting workflow.
• Zero telemetry, no logging of credentials, TypeScript, MIT-licensed, Node.js 18+, Dockerfile included.

Use cases of eSIMfly MCP

• Support teams: answer "why does this customer's eSIM have no data?" in one question — live network status, wrong-network events and remaining data, with the fix explained in plain language.
• Resellers and ops: compare plans and margins, keep an eye on balance and low-data eSIMs, sell top-ups from the assistant with a confirmation step.
• Developers: explore the real catalogue and your own eSIMs from the IDE while the assistant writes the integration with the official SDK.
• Agents and automations: give an internal agent read access to your eSIM fleet without handing it purchasing power.