Connect Hungry eSIM to Claude, Cursor or VS Code
Hungry eSIM runs a hosted remote MCP server over streamable HTTP. There is nothing to install and no API key to request — point your client at the endpoint below and the tools show up in the next conversation.
Endpoint
https://api.hungry-esim.com/mcpTransport: streamable HTTP (remote). Authentication: none for the six public tools; OAuth for the account tools, which the assistant starts for you the first time it needs them.
Claude (claude.ai and Claude Desktop)
- Open Settings → Connectors. The same screen exists on claude.ai and in Claude Desktop, and connectors added in one appear in the other.
- Choose Add custom connector and paste the endpoint.
- Name it Hungry eSIM and save. Leave the OAuth fields empty — the server advertises its own authorization metadata.
- Start a new chat and ask for a plan. Claude asks permission before the first tool call.
Custom connectors are a paid-plan feature and the setting moves around occasionally — search settings for "connector" if you do not see it.
Cursor
Add the server to ~/.cursor/mcp.json for every project, or to .cursor/mcp.json inside one repository:
{
"mcpServers": {
"hungry-esim": {
"url": "https://api.hungry-esim.com/mcp"
}
}
}Reload Cursor, then check Settings → MCP — the server should be listed with its tools enabled.
VS Code (GitHub Copilot)
Run MCP: Add Server… from the Command Palette and pick HTTP, or edit mcp.json directly:
{
"servers": {
"hungry-esim": {
"type": "http",
"url": "https://api.hungry-esim.com/mcp"
}
}
}Switch Copilot Chat to Agent mode — tools are only offered there.
Check that it worked
Ask something the public tools can answer without signing in — for example "I'm going to Japan for 10 days, find me an eSIM with unlimited data" or "what's the cheapest data plan for France?" You should get named plans with prices, not a generic answer.
Signing in for account tools
Searching, plan details, checkout links and order status work with no account. The four account tools — your eSIMs, your orders, top-up options and buying a top-up — need a one-time OAuth sign-in. The assistant opens a Hungry eSIM consent screen in your browser, you approve, and the connection stays until you revoke it.
If something goes wrong
- The client lists the server but no tools — restart it. Most clients only read the tool list when the connection is first established.
- Opening the endpoint in a browser shows a page instead of JSON — that is expected. MCP clients POST to it; browsers get a human-readable notice.
- Account tools return 401 — the OAuth sign-in has not finished or was revoked. Ask the assistant to retry and complete the consent screen.
- Still stuck — email [email protected] or open an issue on the public repository.