Ext Ops Panel
Open dashboard
Comparison

hybridlog vs io.github.endurancetools/garmin-mcp

hybridlog is an MCP server published by Imgrund. Marketplaces we read that list it: 1 (Official MCP Registry). io.github.endurancetools/garmin-mcp is an MCP server published by endurancetools. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-30. 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

Where each is published
Marketplacehybridlogio.github.endurancetools/garmin-mcp
Official MCP Registry Listed
Version: 0.1.13
Forks (GitHub): 0
Stars (GitHub): 1
Not marked · First seen
Listed
Version: 0.4.2
Downloads/month (npm): 877
Downloads/week (npm): 877
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen

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

hybridlog vs io.github.endurancetools/garmin-mcp
Facthybridlogio.github.endurancetools/garmin-mcp
Marketplaces that list it11
Stars (GitHub) (differs)1 (better)0 (worse)
Forks (GitHub)00
Last release (differs)Not published2026-10-28
Where it runs (differs)On your machine (ghcr.io/imgrund/hybridlog:0.1.13)On your machine (garmin-mcp-server)
Transport (differs)Streamable HTTPstdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)2, secrets among them: 23, secrets among them: 0
LicenceNot statedNot stated
Repository (differs)github.com/imgrund/hybridloggithub.com/endurancetools/garmin-mcp
Changes in the last 7 days (differs)01
First seen (differs)2026-10-112026-10-12

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

hybridlog

In its own words, on Official MCP Registry:

Reads your own Garmin mirror: readiness, training load, muscle freshness, and read-only SQL.

io.github.endurancetools/garmin-mcp

In its own words, on Official MCP Registry:

Unofficial Garmin Connect server: training load, form, HRV readiness and workouts for your watch

How to run each

hybridlog

No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.

Requires: APP_KEY (secret), DATABASE_URL (secret)

io.github.endurancetools/garmin-mcp As a local MCP server: npm package

Claude Code
claude mcp add --transport stdio garmin-mcp -- npx -y garmin-mcp-server

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Tools each declares

Neither one's marketplaces publish a list of tools, so there is nothing to compare.

Settings each asks for

Only hybridlog asks for

  • APP_KEY (secret)
  • DATABASE_URL (secret)

Only io.github.endurancetools/garmin-mcp asks for

  • GARMIN_DATA_DIR
  • GARMIN_ENABLE_DESTRUCTIVE
  • GARMIN_REGION

Settings as each marketplace publishes them. Asking for fewer is not better in itself.

What it can do: hybridlog · What it can do: io.github.endurancetools/garmin-mcp · Compare two other plugins

Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.

Where the data comes from: how the catalog is built