ESIM.Dog MCP Server
Let your agent provision eSIM data and real mobile numbers worldwide when the product needs cellular connectivity without manual carrier portals.
Overview
eSIM.dog MCP is a Build-phase MCP server that provisions global eSIM data plans and real mobile phone numbers for AI agents across 200+ countries.
What is this MCP server?
- eSIM.dog MCP Server v1.0.0 for AI agent workflows
- Global eSIM data plan provisioning across 200+ countries
- Real mobile phone numbers for agents that need SMS or voice reachability
- Purpose-built for autonomous agents via MCP rather than human-only dashboards
- Documented at esim.dog/ai-agents for agent integration patterns
- 200+ countries coverage (catalog claim)
- Server version 1.0.0
- GitHub package io.github.elliot-esimdog/mcp-esim
What problem does it solve?
Agents that need SMS verification or mobile data cannot complete flows when builders only have web APIs and no programmatic SIM or number supply.
Who is it for?
Agent products that verify accounts by phone, operate internationally, or run devices that need a real mobile identity.
Skip if: Static web apps with email-only auth and no mobile or roaming requirements.
What do I get? / Deliverables
Your MCP client can request plans and numbers through tools so connectivity steps happen inside the agent loop instead of manual carrier shopping.
- Provisioned eSIM data plans via MCP tools
- Assignable real mobile numbers for agent workflows
- Country-scoped connectivity without manual carrier UI
Recommended MCP Servers
Journey fit
Telephony and mobile data for agents are built as external API integrations before ship and operate. eSIM.dog MCP wraps plan purchase and number provisioning so build-time agent workflows can allocate connectivity programmatically.
How it compares
Telecom provisioning MCP, not a UX or code-review skill.
Common Questions / FAQ
Who is mcp-esim for?
Builders shipping agents that need real phone numbers or travel data without managing carrier contracts by hand.
When should I use mcp-esim?
Use it in build when integrating telephony or eSIM into agent toolchains for verification, alerts, or global deployment tests.
How do I add mcp-esim to my agent?
Register the eSIM.dog MCP server from the GitHub repo in your Claude Code or Cursor MCP settings, add any API keys the provider requires, and enable stdio or hosted transport per their docs.