Connect Garmin to Gemini
Gemini reaches garmlink over the Model Context Protocol (MCP) three ways: as a custom app in the Gemini app on the web, through the Gemini CLI for individuals, or in Gemini Enterprise for organisations. This guide covers all three.
Connect your Garmin account
On the Connection screen, sign in to Garmin Connect with your email and password (used once, never stored), complete the verification code if Garmin asks for one, and wait for the status to turn Connected. garmlink starts syncing your activities, sleep, HRV and training metrics right away.
Path A — Gemini app (web)
Google is rolling custom apps out gradually: for now they show up on personal Google accounts in the US, aged 18 and over, with Gemini in English and Keep Activity turned on. Don't see them yet? Path B works everywhere.
- 2.
Add garmlink as a custom app
On gemini.google.com, open Settings, then Connected Apps, and Custom apps. Paste the garmlink address and click Next:https://api.garmlink.ai/mcpGemini opens the garmlink sign-in page: sign in, then press Authorize.
- 3.
Call garmlink in a chat
In a conversation, type @ and pick garmlink, then ask:- “How did I sleep this week?”
- “Summarize my last five runs.”
- “Is my training load trending up or down this month?”
Path B — Gemini CLI (individual)
- 4.
Install the Gemini CLI
Install the CLI globally, then run it once so it creates its config directory:npm install -g @google/gemini-cligemini
Sign in with your Google account when it asks.
- 5.
Declare garmlink in the CLI settings
Open~/.gemini/settings.json(create it if it doesn't exist) and declare garmlink as an MCP server:{ "mcpServers": { "garmlink": { "httpUrl": "https://api.garmlink.ai/mcp", "oauth": { "enabled": true } } } }Nothing else goes in that file — no headers, no API key, no client secret. With OAuth enabled, the Gemini CLI runs the whole OAuth 2.0 flow itself.
- 6.
Run the CLI and approve access
Startgeminiin a terminal. The first time it reaches garmlink it opens a browser window: sign in, approve read-only access, and the CLI stores the tokens locally for next time.Then just ask, in plain language:
- “How did I sleep this week?”
- “Summarize my last five runs.”
- “Is my training load trending up or down this month?”
Path C — Gemini Enterprise (organisation)
- 7.
Add the MCP server in Gemini Enterprise
In Gemini Enterprise, open Connected apps → Add MCP Server. Fill in the MCP server details — a name, a description, and the garmlink URL:https://api.garmlink.ai/mcpOnly the StreamableHTTP transport is supported — legacy SSE MCP servers are rejected. garmlink is StreamableHTTP, so it qualifies.
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.
- 8.
Authenticate and set the scope
Pick OAuth as the authentication method and complete the garmlink sign-in. Then choose the scope: publish the connection to the whole organisation, or require each member to authenticate with their own garmlink account.
- There is no Custom apps option in the Gemini app. Your account doesn't have custom apps yet — Google opens them to personal accounts in the US, in English, first. Use the Gemini CLI meanwhile, or Gemini Enterprise if your organisation has it.
- The connection stops after you press Authorize. Add garmlink again in Custom apps: the second attempt usually goes through.
- The CLI can't authenticate. Make sure
~/.gemini/settings.jsoncarries no header and no token next to the OAuth block — a stale Authorization header wins over the OAuth flow and the server answers 401. - The server is unreachable. The MCP URL must be reachable over HTTPS from the machine running the CLI (or from Gemini Enterprise) — check that no proxy or firewall is blocking it.
- Data looks empty or stale. Check where the sync stands on the Connection screen.
Using another assistant? See all the setup guides. Curious what garmlink can read? Browse the tools reference. Want to see real answers first? Read twelve examples from a real account.
