# Garmin MCP server

> Retrieve activities, health metrics, and training history.

- Provider: Garmin
- Category: Data (https://mcpheaven.com/catalog/category/data)
- Status: Planned
- Slug: `garmin`
- Verified: 2026-11-10
- JSON: https://mcpheaven.com/api/v1/capabilities/garmin
- HTML: https://mcpheaven.com/catalog/garmin

## Why it is in the catalog

Fitness and device data access is currently community MCP territory.

## Questions

### Is there an official Garmin MCP server?

Fitness and device data access is currently community MCP territory. mcpheaven lists Garmin so agents can find it by task and reach it through one MCP endpoint.

### What can an AI agent do with Garmin?

Retrieve activities, health metrics, and training history. Agents find it by describing the task, for example with the search_capabilities tool.

### How do I connect Garmin to Claude, Codex or Cursor?

Add mcpheaven once as an MCP server (https://mcpheaven.com/mcp) with an API key, then ask your agent for the task. It calls get_capability with the slug "garmin" for details.

### Is the Garmin integration available?

The Garmin integration is planned. Agents can already discover it through mcpheaven's search, and it will become callable once the integration ships.

## Connect

MCP endpoint: `https://mcpheaven.com/mcp` (Streamable HTTP, JSON-RPC). Without a key: public catalog, 120 calls per hour per address. With a key (`Authorization: Bearer mch_…`, free at https://mcpheaven.com/signup): plan quota and private capabilities.

```bash
claude mcp add --transport http mcpheaven https://mcpheaven.com/mcp --header "Authorization: Bearer mch_…"
```

```json
{ "mcpServers": { "mcpheaven": { "url": "https://mcpheaven.com/mcp", "headers": { "Authorization": "Bearer mch_…" } } } }
```

REST: `GET https://mcpheaven.com/api/v1/capabilities?q=<task>` · OpenAPI: https://mcpheaven.com/openapi.json · Server card: https://mcpheaven.com/.well-known/mcp.json