Fillo vs Hungry eSIM
A side-by-side look at the Fillo and Hungry eSIM MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
H
Hungry eSIMDeveloper ToolsSearch travel eSIM data plans for 190+ destinations, create checkout links, and track your eSIMs.37FairAuth: not declaredVerdict: choose Fillo for developer tools work as a local process; choose Hungry eSIM for developer tools. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Fillo when
- You need dedicated capabilities in the Developer Tools domain.
- You prefer a local stdio subprocess transport.
HChoose Hungry eSIM when
- You need dedicated capabilities in the Developer Tools domain.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | H Hungry eSIM | |
|---|---|---|
| Category | Developer Tools | Developer Tools |
| Quality signal | 44/100 · Fair | 37/100 · Fair |
| Install command | Confirmed | Not confirmed yet |
| Transport | Local subprocess (stdio) | — |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | — |
| Directory activity | 2 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View Fillo | View Hungry eSIM |
Tools & capabilities
Fillo tools
No tool names declared yet. Check the project README from the listing page.
Hungry eSIM tools
No tool names declared yet. Check the project README from the listing page.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Fillo
{
"mcpServers": {
"fillo": {
"command": "npx",
"args": [
"-y",
"@usefillo/cli@latest"
]
}
}
}
Hungry eSIM
No confirmed install command for Hungry eSIM yet — follow the setup steps linked from its listing page rather than a guessed package name.
Frequently asked questions
Fillo is categorized under Developer Tools and uses a local stdio subprocess. Hungry eSIM belongs to Developer Tools and uses an install path we have not confirmed yet. Pick Fillo for developer tools work and Hungry eSIM for developer tools.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client. Hungry eSIM has no confirmed install command yet — follow its own setup instructions.
Fillo has no declared pricing — check the project's own site. Hungry eSIM has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add fillo and hungry-esim as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Fillo has a quality signal of 44/100 (Fair) with 2 views, 0 installs and 0 GitHub stars. Hungry eSIM has 37/100 (Fair) with 0 views, 0 installs and 0 GitHub stars.