Garmin MCP Server is a Model Context Protocol server that connects Garmin Connect to Claude and other compatible clients, allowing them to access fitness and health data. It supports users who want to inspect and manage activities, health metrics, training information, workouts, gear, and related performance data through an MCP client. The catalogue includes one skill and one instruction for working with the server.
Borrowing it
Nothing to install: this file belongs to Taxuspt/garmin_mcp. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/Taxuspt/garmin_mcp/main/CLAUDE.mdgit clone --depth 1 https://github.com/Taxuspt/garmin_mcpWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/instructions/taxuspt/garmin_mcp/claude-md)<a href="https://agentmods.dev/instructions/taxuspt/garmin_mcp/claude-md"><img src="https://agentmods.dev/badge/instructions/taxuspt/garmin_mcp/claude-md/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/instructions/taxuspt/garmin_mcp/claude-md"><img src="https://agentmods.dev/badge/instructions/taxuspt/garmin_mcp/claude-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.02382 | $0.02382 |
| Opus 5.5 | $0.00953 | $0.00953 |
| Sonnet 5.5 | $0.00476 | $0.00476 |
| Haiku 4.5 | $0.00238 | $0.00238 |
Grade A, and why
garmin_mcp CLAUDE.md scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 16d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 300 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Garmin MCP Server - Project Guide
Overview
This is a Model Context Protocol (MCP) server that connects to Garmin Connect and exposes fitness and health data to Claude and other MCP-compatible clients. The server provides 122 tools organized into 15 functional modules.
Critical: Garmin API Integration
The integration with Garmin's API is done via the python-garminconnect library.
When Debugging or Implementing New Tools
ALWAYS reference the python-garminconnect repository and these two files:
- example.py - Contains examples for many available API endpoints
- demo.py - Comprehensive demo with 100+ API methods organized by category
These files are your source of truth for:
- Available API endpoints - Check if a method actually exists in the library
- Correct method signatures - Verify parameter names and types
- Expected output formats - See what data structure each endpoint returns
- Method names - Confirm the exact name of Garmin client methods
Library Version
Currently using: garminconnect==0.3.2 (see pyproject.toml)
Important Note
Not all Garmin Connect API endpoints have corresponding methods in python-garminconnect. Before implementing a new tool:
- Check example.py
- Check demo.py
- Search the library source code
If a method doesn't exist in python-garminconnect, you'll need to either:
- Use an alternative method that provides similar data
- Request the feature in the python-garminconnect repository
- Implement a custom API call if absolutely necessary
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 16d ago First seen · 300 lines · 2,382 tokens per session scan A a8c4f16a2a84
garmin_mcp CLAUDE.md is an instructions file published in the GitHub repository Taxuspt/garmin_mcp (1,424 stars, last pushed 5d ago), licensed MIT. It adds 2,382 tokens to every session, about $0.0095 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-10-13.
Other instructions, from other repositories
graftcode graftcode-python.instructions.md
Instructions for grft-dev/graftcode, covering graftcode — python backend services, when this applies (always), authoritative docs (source of truth), golden rules and service = plain python module (no web framework).
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).