Garmin MCP server
{
"mcpServers": {
"missingmcp-garmin": {
"type": "http",
"url": "https://missingmcp.com/garmin/mcp"
}
}
}{
"mcpServers": {
"missingmcp-garmin": {
"type": "http",
"url": "https://missingmcp.com/garmin/mcp"
}
}
}{
"mcpServers": {
"missingmcp-garmin": {
"type": "http",
"url": "https://missingmcp.com/garmin/mcp"
}
}
}{
"servers": {
"missingmcp-garmin": {
"type": "http",
"url": "https://missingmcp.com/garmin/mcp"
}
}
}{
"mcpServers": {
"missingmcp-garmin": {
"type": "http",
"url": "https://missingmcp.com/garmin/mcp"
}
}
}file .mcp.json (in your project root)file claude_desktop_config.jsonfile ~/.cursor/mcp.jsonfile .vscode/mcp.jsonfile ~/.codeium/windsurf/mcp_config.jsonversion 1.0.0
What it does
A multi-user OAuth gateway that exposes Garmin Connect and WHOOP fitness data through MCP, allowing users to connect their accounts securely from any Claude client without managing tokens locally.
- Query your Garmin activities, sleep data, and training metrics directly in Claude conversations.
- Access WHOOP recovery, strain, sleep, and workout data through Claude with encrypted token storage.
- Analyze HRV and fitness trends by combining multiple data sources in a single Claude session.
Before you enable it
An MCP server runs with whatever access you give it. Start with a development account rather than production, and check which tools the server exposes before you let an agent call them unattended.