Futureweb Intervals MCP vs io.github.layergen/eodly-mcp
Futureweb Intervals MCP is an MCP server published by futureweb. Marketplaces we read that list it: 2 (Official MCP Registry, PyPI (MCP servers)). io.github.layergen/eodly-mcp is an MCP server published by layergen. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-27. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.
Where each is published
| Marketplace |   Futureweb Intervals MCP |  io.github.layergen/eodly-mcp |
|---|---|---|
| Official MCP Registry | Listed Version: 1.0.0b2 Downloads/month (PyPI): 0 Downloads/week (PyPI): 118 Forks (GitHub): 0 Stars (GitHub): 10 Not marked · First seen |
Listed Version: 0.2.2 Downloads/month (npm): 339 Downloads/week (npm): 31 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
| PyPI (MCP servers) | Listed Version: 1.0.0b2 Downloads/month (PyPI): 0 Downloads/week (PyPI): 118 Forks (GitHub): 0 Stars (GitHub): 10 Not marked · First seen |
Not listed |
Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.
The facts side by side
| Fact | Futureweb Intervals MCP | io.github.layergen/eodly-mcp |
|---|---|---|
| Marketplaces that list it (differs) | 2 (better) | 1 (worse) |
| Stars (GitHub) (differs) | 10 (better) | 0 (worse) |
| Forks (GitHub) | 0 | 0 |
| Last release (differs) | 2026-10-15 | Not published |
| Where it runs (differs) | On your machine (futureweb-intervals-mcp) | Remote server (eodly.io/mcp) |
| Transport (differs) | stdio | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | 5, secrets among them: 1 | 1, secrets among them: 1 |
| Licence (differs) | GPL-3.0-only | Not stated |
| Repository (differs) | github.com/futureweb/intervals-mcp-server | github.com/layergen/eodly-mcp |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Responded 6 days ago |
Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.
What each says it does
Futureweb Intervals MCP
Self-hosted Intervals.icu MCP server: training analytics, Garmin data, wellness, workout planning
io.github.layergen/eodly-mcp
Read your team's end-of-day reports and roster from Eodly. Sign in with OAuth or use an API key.
How to run each
Futureweb Intervals MCP As a local MCP server: PyPI package
claude mcp add --env "API_KEY=<YOUR_API_KEY>" --env "ATHLETE_ID=<YOUR_ATHLETE_ID>" --transport stdio intervals-mcp-server -- uvx futureweb-intervals-mcpRequires: API_KEY (secret), ATHLETE_ID
io.github.layergen/eodly-mcp As a remote MCP server
claude mcp add --transport http eodly-mcp https://eodly.io/mcpRequires: EODLY_API_KEY (secret)
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only io.github.layergen/eodly-mcp has a remote endpoint we check. How we check endpoints
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
Only Futureweb Intervals MCP asks for
API_KEY (secret)ATHLETE_IDATHLETE_TIMEZONEMCP_PERMISSIONSMCP_TOOLSET
Only io.github.layergen/eodly-mcp asks for
EODLY_API_KEY (secret)
Settings as each marketplace publishes them. Asking for fewer is not better in itself.
What it can do: Futureweb Intervals MCP · What it can do: io.github.layergen/eodly-mcp · Compare two other plugins
Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Package data comes from the Python Package Index (pypi.org). Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.