Garmin Connect Personal API vs io.github.cphoskins/cronometer
Garmin Connect Personal API is an MCP server published by DynamicsNinja. Marketplaces we read that list it: 1 (Official MCP Registry). io.github.cphoskins/cronometer is an MCP server published by cphoskins. Marketplaces we read that list it: 2 (Official MCP Registry, PyPI (MCP servers)). As of our marketplace pass on 2026-10-24. 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 | ||
|---|---|---|
| Official MCP Registry | Listed Version: 1.0.0 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
Listed Version: 2.3.0 Downloads/month (PyPI): 3 239 Downloads/week (PyPI): 388 Forks (GitHub): 15 Stars (GitHub): 26 Not marked · First seen |
| PyPI (MCP servers) | Not listed | Listed Version: 2.3.0 Downloads/month (PyPI): 3 239 Downloads/week (PyPI): 388 Forks (GitHub): 15 Stars (GitHub): 26 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
| Fact | Garmin Connect Personal API | io.github.cphoskins/cronometer |
|---|---|---|
| Marketplaces that list it (differs) | 1 (worse) | 2 (better) |
| Stars (GitHub) (differs) | 0 (worse) | 26 (better) |
| Forks (GitHub) (differs) | 0 (worse) | 15 (better) |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (garmin-connect-personal-api-mcp) | On your machine (cronometer-mcp) |
| Transport | stdio | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | 1, secrets among them: 1 | 3, secrets among them: 1 |
| Licence (differs) | Not stated | MIT |
| Repository (differs) | github.com/dynamicsninja/connect-personal-api-js | github.com/cphoskins/cronometer-mcp |
| Changes in the last 7 days (differs) | 2 | 0 |
| First seen (differs) | 2026-10-23 | 2026-10-11 |
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
Read your Garmin sleep, HRV, steps, stress, Body Battery, and activities (unofficial)
io.github.cphoskins/cronometer
MCP server for Cronometer — food logs, macros, fasting, biometrics, and recurring foods
How to run each
Garmin Connect Personal API As a local MCP server: npm package
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)
io.github.cphoskins/cronometer As a local MCP server: PyPI package
claude mcp add --env "CRONOMETER_PASSWORD=<YOUR_CRONOMETER_PASSWORD>" --env "CRONOMETER_USERNAME=<YOUR_CRONOMETER_USERNAME>" --transport stdio cronometer -- uvx cronometer-mcp
Requires: CRONOMETER_PASSWORD (secret), CRONOMETER_USERNAME
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 io.github.cphoskins/cronometer asks for
CRONOMETER_DATA_DIRCRONOMETER_PASSWORD (secret)CRONOMETER_USERNAME
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: io.github.cphoskins/cronometer · 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.