Powered by Keepgo
Travel & Tourism
TravelTECHNOLOGY & FINANCE
FintechTELECOMMUNICATION
TelecomEmployee Connectivity
EnterprisePlug Claude, Cursor, GitHub Copilot or your own agent into your esimba account through MCP. It checks your eSIMs, balance and usage live. You approve every order and top-up.
MCP (Model Context Protocol) is an open standard that connects AI assistants to other systems, like a plug. Our MCP server plugs your assistant into your esimba partner account, so it can look things up and act with your permission. One address works with any MCP-compatible tool.
Same task, with and without MCP: top up the eSIMs that are running out of data.
Every check and top-up is done by hand.
The assistant checks usage across your eSIMs and tops up the ones you approve.
Data is pulled directly from your account.
Combine steps in one request: pull usage, spot eSIMs running low, then top them up or set auto-refill.
An eSIM was blocked by mistake? Check its status and restore it in the same chat.
Anyone on your team can connect and prompt the assistant.
Type it the way you'd say it. A few requests to start with:
“What's my balance?”
“Which eSIMs will run out of data this week?”
“Show bundles for Thailand with prices.”
“Order 5 Lifetime eSIMs for Thailand.”
“Turn on auto-refill with 1 GB packages.”
“Give me the QR code for this eSIM.”
You choose what the assistant can do when you connect. By default it can only view your account: ordering, top-ups and activation codes stay off until you turn them on. Change permissions or disconnect at any time.
Before any order or top-up, it shows the eSIM, package and price, and waits for you to confirm.
Each purchase has its own key, so a repeated request isn't charged again. If a result is unclear, it checks your transactions before trying again.
You enter your API key and token on the esimba sign-in page. The assistant never sees them.
Only your own eSIMs and transactions. Activation and QR codes stay hidden unless you allow them.
You need an esimba partner account with its API key and access token.
https://myaccount.keepgo.com/mcp/partnerWebstore partners: use your own partner portal domain instead, e.g. https://myaccount.your-domain.com/mcp/partner.
Add a custom (remote) MCP server and paste the address.
Enter your API key and access token, tick permissions, then ask.
| Claude Desktop | Settings → Connectors → Add custom connector → paste the address → Connect |
|---|---|
| Claude Code | claude mcp add --transport http esimba https://myaccount.keepgo.com/mcp/partner, then /mcp → esimba → Authenticate |
| Cursor | ~/.cursor/mcp.json → { "mcpServers": { "esimba": { "url": "https://myaccount.keepgo.com/mcp/partner" } } } |
| GitHub Copilot in VS Code | .vscode/mcp.json → { "servers": { "esimba": { "type": "http", "url": "https://myaccount.keepgo.com/mcp/partner" } } }, then use Copilot Chat in Agent mode |
| Your own agent | Connect with any MCP client library and sign in once. Read tools from tools/list on each connection. For production, use the esimba.ai API. |
Permissions, limits and troubleshooting: read the full MCP documentation →
No. Setup takes a few minutes and requires no coding: add the server address to your AI tool, sign in with your API key and access token, and choose the permissions. From then on, you work with the assistant in plain language.
Claude Desktop, Claude Code, Cursor, GitHub Copilot in VS Code and custom agents. Any MCP client that supports remote servers with OAuth sign-in can connect. On GitHub Copilot Business or Enterprise, your organization's administrator needs to enable MCP servers first.
No. Orders and top-ups require a separate permission that is off by default. Even when it is enabled, the assistant shows the eSIM, package and price before every purchase and proceeds only after you confirm.
Yes. Any MCP client library can connect over HTTP after a one-time sign-in. The server is designed with a person in the loop, though: purchases require confirmation, and sign-in must be renewed at least every 90 days. For fully automated integrations, we recommend the esimba.ai API.
Yes. Connect a sandbox account, which comes with a test balance and involves no real charges, or connect your live account with view-only access.
Remove the esimba server in your AI tool's settings. To end every active connection at once, refresh your API credentials in your partner account. This also changes the keys used by your existing API integration, so update it as well. To end connections without changing your keys, contact your account manager.
Connect in two minutes. Not an esimba partner yet? Sign up for free.
Get free platform accessesimba.ai, a subsidiary of Keepgo, gives you the opportunity to offer your customers top-quality connectivity in 150+ countries.