roamzy-io/mcp-server

MCP server for Roamzy — buy and manage a global eSIM
through Claude Desktop, Cursor, Continue, Cline, Windsurf, Zed, or any other
Model Context Protocol client. Anonymous
flow by default: no account required to use it.
**Agents don't just buy — they earn.** A built-in referral pays you 20% of every
payment from anyone you refer — a human user *or* another AI agent — forever. Even
anonymous agents earn from day one, no signup. That's the distribution flywheel:
an agent that earns has a reason to tell the next agent.
> One eSIM for 193 countries. Pay per actual MB used. USDT or USDC on your
> preferred network. No packages. No expiry. No subscription.
---
What it does
This MCP server lets an agent (running in any MCP-compatible client) call the
Roamzy HTTP API on the user's behalf. Sample conversation in Claude Desktop:
> **User:** I'm going to Thailand for a week, buy me an eSIM.
>
> **Claude:** Roamzy — one universal eSIM, works in 193 countries. Billed per
> MB at the local rate, no packages, no expiry. For Thailand the rate is
> ~$1.43/GB. Which stablecoin / network do you want to pay with?
> (USDT on TRON, BSC, Polygon, Optimism, Arbitrum, TON — or USDC on Solana,
> BSC, Polygon, Optimism, Arbitrum.) Minimum top-up is $20 USDT.
>
> **User:** USDC on Solana, $20.
>
> **Claude:** Order created. eSIM number 2040XXXXXX. Pay here: [pay-link].
> After ~1 minute on Solana, I'll fetch your QR.
> ❗ Save this recovery URL so you can return to this eSIM from another
> Claude chat: [claim-link].
>
> *User pays $20 USDC.*
>
> **Claude:** Paid. Here's your activation QR — open Settings → Cellular →
> Add eSIM and scan it with your phone camera. [QR PNG attached]
The server doesn't run a backend itself — it's a thin client to
https://roamzy.io/api/v1/*, mapped 1:1 to MCP tools.
---
Install
Add this to your MCP client's configuration (e.g. ~/Library/Application
Support/Claude/claude_desktop_config.json for Claude Desktop on macOS):
Restart your MCP client. The first authed tool call will mint an anonymous
Roamzy account automatically — no signup required.
Alternative: install from a hosted tarball
If you can't reach the npm registry, want to pin a pre-release, or prefer to
fetch a specific version directly from Roamzy's CDN, swap the args to a URL:
Both forms run the same code — the npm registry path is the recommended
default because it integrates with npm view, version pinning, and MCP
registries (Smithery, modelcontextprotocol/servers, etc.).
Optional environment variables
| Variable | Default | Purpose |
|---------------------------|------------------------------------|--------------------------------------------------------------------------------------------------------|
| ROAMZY_API_TOKEN | _(unset → anonymous mode)_ | Use a pre-existing API token from /dashboard/settings instead of an anonymous account. |
| ROAMZY_ENABLE_PURCHASE | false _(but true in anon mode)_| When using a non-anonymous token, opt-in flag required to expose purchase tools. |
| ROAMZY_API_BASE | https://roamzy.io/api/v1 | Override for staging / self-hosted backends. |
---
Tools
Public (no auth required)
| Tool | Purpose |
|----------------------------|------------------------------------------------------------------------------------------|
| roamzy_status | Service status + agent-pause flags. Call before any purchase attempt. |
| roamzy_list_countries | Reference list of all 193 supported countries with per-MB rates. |