Hungry eSIM
Travel eSIMs: unlimited data, pick your days, top up existing eSIMs, card checkout, no API key.
Install
Add this to your client's MCP configuration (Claude Desktop: claude_desktop_config.json; Cursor: .cursor/mcp.json; VS Code and others use the same "mcpServers" shape).
claude mcp add --transport http hungry-esim 'https://api.hungry-esim.com/mcp'{
"mcpServers": {
"hungry-esim": {
"type": "http",
"url": "https://api.hungry-esim.com/mcp"
}
}
}Documentation
From the project's README on GitHub, refreshed weekly. Links open on GitHub.
Hungry eSIM — MCP Server
Buy and manage travel eSIMs from AI assistants like Claude, Cursor, and VS Code via the Model Context Protocol.
Endpoint: https://api.hungry-esim.com/mcp (remote, streamable HTTP — no install, no API key)
Unlimited data plans where you pick your days, top-ups for eSIMs you already own, and plain credit-card checkout on hungry-esim.com. No crypto wallet, no prepaid balance, no API key required.
This repository is the public home of the server: docs, manifest, and setup guides. The server itself is a hosted remote service.
What you can do
| Tool | What it does | Auth |
|---|---|---|
search_esim_plans | Search travel eSIM data plans by destination, data amount, and validity | — |
check_destination_coverage | "Does it work in …?" — coverage check for a destination with representative plans | — |
find_cheapest_plan | Cheapest plan(s) for a destination and trip length (total-trip cost ranking) | — |
get_plan_details | Full details for one plan (coverage, speed, top-up support) | — |
create_checkout | Create a card checkout link for a plan — for unlimited plans, choose how many days | — |
get_order_status | Check an order and eSIM installation status | — |
my_esims | List eSIMs on your account with status and usage | OAuth |
my_orders | List your past orders | OAuth |
list_esim_topups | Top-up options for an eSIM you already own | OAuth |
topup_esim | Buy a top-up for an existing eSIM — no new QR code needed | OAuth |
Public tools work immediately with no sign-in. Account tools use OAuth: the assistant sends you to hungry-esim.com to sign in once, then can see your eSIMs and orders.
Payment always happens on hungry-esim.com in a normal browser checkout with a credit card. The assistant never touches your payment details.
Setup
Claude (claude.ai / Claude Desktop)
Settings → Connectors → Add custom connector → paste:
https://api.hungry-esim.com/mcpCursor
Add to ~/.cursor/mcp.json:
{
"mcpServers": {
"hungry-esim": {
"url": "https://api.hungry-esim.com/mcp"
}
}
}VS Code (GitHub Copilot)
Add to your mcp.json (Command Palette → “MCP: Add Server” → HTTP):
{
"servers": {
"hungry-esim": {
"type": "http",
"url": "https://api.hungry-esim.com/mcp"
}
}
}Then ask things like:
- “I’m going to Japan for 10 days — find me an eSIM with unlimited data.”
- “What’s the cheapest data plan for France?”
- “Top up the eSIM I bought last month.”
Registry listings
- Official MCP Registry:
com.hungry-esim/esim - Smithery
The manifest in this repo (server.json) mirrors the official registry entry.
Support
- Guides for agents and humans: hungry-esim.com/for-agents
- Email: support@hungryesim.com (24/7 intake, replies usually within 24 hours)
License
Docs in this repository are released under the MIT License.
Frequently asked questions
What is Hungry eSIM?
Travel eSIMs: unlimited data, pick your days, top up existing eSIMs, card checkout, no API key.
How do I install Hungry eSIM?
It runs as a remote server. In Claude Code: claude mcp add --transport http hungry-esim 'https://api.hungry-esim.com/mcp'. For other clients, paste the JSON configuration from this page into their MCP settings.
Does Hungry eSIM need an API key?
Its registry entry lists no required key or secret. Some features may still need an account with the service it connects to.
Is Hungry eSIM open source?
Yes. Its code is on GitHub under the MIT license.
Who maintains Hungry eSIM?
It is published by kangih90. AI.tn lists it but does not maintain or endorse it.
From the official MCP Registry. Listing is not an endorsement: review a server's code and permissions before giving it access to your data.