dev.cotlet/garmin

Garmin Connect MCP Server and API by Cotlet

Is the Garmin Connect MCP Server and API by Cotlet MCP server down? No. It is up and needs auth (HTTP 401), probed 2026-11-13.

Garmin Connect fitness and health tracking MCP server: list activities, download FIT file.

needs auth probed 2026-11-14 · unchanged since 2026-11-13 · HTTP 401 · Bearer

The server needs auth, so these tool definitions were read from the publisher's open-source package pypi:garmin-cotlet-mcp, started in a container with placeholder values and the network off, on 2026-11-14. Tool definitions do not depend on the token, so this is what an authorized user loads, unless the server hides tools by plan or role.

Streamable HTTP error: Error POSTing to endpoint: {"error":"unauthorized","message":"Sign in to Cotlet to use this MCP server."}

Endpoint

https://cotlet.dev/mcp/v1/garmin/connect (streamable-http)

Host

cotlet.dev

Of a 1M window

<0.1 % of a 1M context window

Getting access

OAuth with dynamic client registration. A client such as Claude Code, Cursor or npx mcpcost auth https://cotlet.dev/mcp/v1/garmin/connect registers itself and opens the consent page; the publisher has nothing to set up for you. The publisher's guide to getting access.
Authorization server cotlet.dev, PKCE S256, grants authorization_code, refresh_token.
Scopes mcp.
Read from the server's public OAuth metadata, without a token. Method.

Repository

https://github.com/cotlet-connect/garmin-mcp

Website

https://cotlet.dev/integrations/garmin-api-mcp-server

Registry

active, updated 2026-11-10 · registry entry

Compare this server with others.