Connect garmlink to your AI assistant

garmlink speaks the Model Context Protocol, so any assistant or code tool that can add a remote MCP server reads your Garmin history directly. Same address everywhere — only the place you paste it changes.

Every guide below asks for the same address — this one:

https://api.garmlink.ai/mcp

Icon (optional)

PNG, 256×256, ≤ 10 KB. The garmlink icon carries its own background, so it stays readable whether the assistant's interface is light or dark.

The garmlink connector icon
On a light interface
The garmlink connector icon
On a dark interface
Download the icon

Pick your assistant

Chat assistants

Code editors and agents

Another MCP client?

Other clients that can add a remote MCP server with a browser sign-in — Zed, Goose or Raycast, for example — connect the same way: add the address above as an HTTP server, leave any key empty, and sign in with your garmlink account when the browser opens.

Thinking of running a Garmin MCP server yourself? Hosted or self-hosted: the comparison.

Want to see what garmlink can read before connecting anything? Everything is listed in the MCP docs.