Model Context Protocol server for Garmin Connect
Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.
Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"garmin-connect-mcp-server","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.
Everything here was measured by our prober or read from a registry. Nothing is self-reported.
Attributed to the source that supplied each field. Treated as claims, not facts.
# Garmin Connect MCP Server [](https://github.com/BojanMakivic/garminconnect-mcp-pypi/actions/workflows/publish-to-pypi.yml)  [](https://www.gnu.org/licenses/gpl-3.0) [](https://www.python.org/downloads/) [](https://pypistats.org/packages/garmin-connect-mcp-server) [](https://pepy.tech/projects/garmin-connect-mcp-server) [](https://github.com/BojanMakivic/garminconnect-mcp-pypi/blob/main/CHANGELOG.md)  ## Quick start with uvx Run first-time Garmin authentication once in a normal terminal: ```powershell uvx --from garmin-connect-mcp-server garmin-connect-mcp-server-auth ``` Then run the MCP server: ```powershell uvx garmin-connect-mcp-server ``` The auth command prompts for Garmin credentials and MFA if Garmin requires it. Tokens stay local on your machine, usually in: ```text ~/.garminconnect ``` On Windows, that is usually: ```text C:\Users\YOUR_WINDOWS_USERNAME\.garminconnect ``` The MCP server itself never prompts on stdin. For stdio MCP servers, stdout/stdin are reserved for protocol messages. ## Dependencies When using `uvx`, users do not need to install Python libraries manually. `uvx` reads the package metadata from PyPI and installs the required libraries in its own manag…
Mapped onto the structured taxonomy from declared text and observed tool names. Confidence shown for derived entries.
Every source is kept verbatim. Field changes are logged as events.