Ext Ops Panel
Open dashboard
Comparison

Garmin Connect Personal API vs Garmin Connect

Garmin Connect Personal API is an MCP server published by DynamicsNinja. Marketplaces we read that list it: 1 (Official MCP Registry). Garmin Connect is an MCP server published by happyc0der. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-26. 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
MarketplaceGarmin Connect Personal APIGarmin Connect
Official MCP Registry Listed
Version: 1.0.0
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
Listed
Version: 0.3.1
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

Garmin Connect Personal API vs Garmin Connect
FactGarmin Connect Personal APIGarmin Connect
Marketplaces that list it11
Stars (GitHub)00
Forks (GitHub)00
Last release (differs)Not published2026-10-20
Where it runs (differs)On your machine (garmin-connect-personal-api-mcp)On your machine (garmin-connect-api)
Transportstdiostdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)1, secrets among them: 11, secrets among them: 0
LicenceNot statedNot stated
Repository (differs)github.com/dynamicsninja/connect-personal-api-jsgithub.com/happyc0der/garmin-connect-api
Changes in the last 7 days (differs)28
First seen (differs)2026-10-232026-10-19

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

Garmin Connect Personal API

In its own words, on Official MCP Registry:

Read your Garmin sleep, HRV, steps, stress, Body Battery, and activities (unofficial)

Garmin Connect

In its own words, on Official MCP Registry:

Read and write Garmin Connect: activities, strength sets, health data, workouts and weigh-ins.

How to run each

Garmin Connect Personal API As a local MCP server: npm package

Claude Code
claude mcp add --env "GARMIN_PERSONAL_API_KEY=<YOUR_GARMIN_PERSONAL_API_KEY>" --transport stdio garmin-connect-personal-api -- npx -y garmin-connect-personal-api-mcp

Requires: GARMIN_PERSONAL_API_KEY (secret)

Garmin Connect As a local MCP server: PyPI package

Claude Code
claude mcp add --transport stdio garmin-connect-api -- uvx garmin-connect-api

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 Garmin Connect Personal API asks for

  • GARMIN_PERSONAL_API_KEY (secret)

Only Garmin Connect asks for

  • GARMINTOKENS

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

What it can do: Garmin Connect Personal API · What it can do: Garmin Connect · 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