esimfly-mcp
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ESIMFLY_BASE_URL | No | Override the API base URL | |
| ESIMFLY_SECRET_KEY | Yes | API secret key (sk_…) | |
| ESIMFLY_ACCESS_CODE | Yes | API access code (esf_…) | |
| ESIMFLY_MCP_ALLOW_WRITES | No | Set to 'true' to register write tools |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| prompts | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_packagesA | Find eSIM data packages you can sell, with your wholesale price. Filter by destination name (search), type (local / regional / global) and page. Returns compact rows; use limit up to 100. |
| get_balanceA | Current prepaid balance (or enterprise balance) and currency. |
| list_esimsB | eSIMs on the account with status, data left and validity. Search by ICCID, package name or code; filter by status. |
| get_esim_usageA | Stored data usage and validity for one eSIM (cheap; fresh as of the last sync). Identify by ICCID or order reference. |
| get_esim_live_statusA | LIVE status straight from the mobile network: lifecycle status, profile install state, last network (operator, country, MCC/MNC, 4G/5G), device model and IMEI, activation and last-usage dates, data used. Expensive — use for diagnosis ("no data", "is it installed?"), not routinely. |
| get_network_eventsA | Attach and data-session events for one eSIM, newest first, each flagged is_allowed. wrong_network_count > 0 means the device latched onto a network outside the plan — the usual cause of "connected but no data" (fix: airplane-mode toggle or manual network selection). |
| get_usage_reportA | Daily data usage for one eSIM over the last N days (default 7, max 90) with per-country and per-operator breakdown. |
| list_ordersB | Order history with filters (status, date range ISO 8601, search by reference / package) and a revenue summary. |
| get_orderA | One order by reference, including its eSIM (ICCID, install links, pending state). |
| get_topup_packagesB | Top-up options for ONE eSIM (they depend on its provider and location), with your price. Returns ESIM_NOT_TOPPABLE when the eSIM state does not allow top-ups. |
| get_webhook_settingsB | Configured webhook URL, subscribed events, available events and the last deliveries. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| esimfly_integration_guide | The complete, always-current prompt for building an eSIMfly integration (all endpoints, recommended architecture, webhooks, SDK). Fetched from docs.esimfly.net. |
| diagnose_esim | Walks through the live status, network events and usage of one eSIM and explains what the customer should do. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 11 tools
Tools are mostly distinct by resource and action. The main potential confusion is among usage-related tools (get_esim_usage, get_esim_live_status, get_usage_report), but their descriptions clearly differentiate stored summary, live network diagnosis, and daily reporting.
All tools use consistent snake_case with predictable verb_noun patterns: get_*, list_*, search_*. The convention is uniform throughout the set.
11 tools is well-scoped for an eSIM reseller management server. Each tool maps to a useful query or monitoring operation without excessive redundancy.
The server covers read/monitoring well: packages, top-ups, eSIMs, usage, orders, balance, and webhook settings. However, it lacks any write/mutation operations such as creating orders, purchasing top-ups, configuring webhooks, or activating eSIMs, which are notable gaps for the domain.