Guide · 6 min read · Last checked: 17 September 2026

What is Garmin MCP?

Garmin MCP is a small service that lets Claude — and other AI apps — read your Garmin watch. You connect once. You paste one private link. Then you ask about sleep, steps, and sport in normal language.

If you have ever exported a CSV, uploaded a zip, or copied splits into a chat, this is the version that skips that. The watch stays the source. The chat becomes the coach’s desk.

In one paragraph

Your Garmin already stores the session: how long you slept, how hard the run was, how full the Body Battery is. Garmin MCP is the door Claude uses to look at those numbers when you ask. You do not install Python. You do not edit a JSON file. You sign in, copy a link, paste it under Claude’s Connectors, and talk.

What MCP means

MCP stands for Model Context Protocol. That is the open way AI apps call outside tools. Claude, Claude Code, and Cursor all support it. You can ignore the letters. Remember the job: give Claude a safe way to ask your watch a question and get a short answer back.

A Garmin MCP server is the piece that knows Garmin’s numbers. When you say “how did I sleep,” Claude picks the sleep tool, the server fetches last night, and Claude writes the sentence. You never see the raw dump unless you ask for it.

In 2026 this pattern is everywhere in sport. COROS shipped an official MCP so athletes can ask ChatGPT and Claude about load and recovery. Coaches paste a connector instead of a spreadsheet. The idea is the same for Garmin: live data, plain questions.

What Claude can read

A good Garmin MCP is built for talk, not for dumping GPS tracks into the chat. Ours reads:

• Sleep: duration, stages, score.
• Daily: steps, calories, resting heart rate, stress.
• Sport: recent activities, laps, intervals, pace and heart rate.
• Training: status, load, threshold pace and its history, personal records.
• Recovery: Body Battery charged and drained per day.

We connected a real watch and asked about last night. Sleep score 91, a full night, last sport a run. That is the test of a Garmin MCP: your numbers, not a demo file.

What it is not

Garmin MCP is not the Garmin Connect app. It does not replace your watch face. It does not diagnose injury. It is not a Garmin product. Garmin MCP is unofficial. Garmin Ltd. did not build it. Keep that in mind the same way you keep it in mind for any third-party dashboard.

It is also not a terminal project. GitHub is full of Garmin MCP servers that you run with uvx. Those are fine if you like a shell. This site is the easy Garmin MCP: a page, a form, a link.

How to get a Garmin MCP

1. Open Connect your Garmin.
2. Enter email, password, and a code if Garmin sends one.
3. Copy the private link.
4. Paste it in Claude under Settings → Connectors.
5. Ask how you slept.

Step by step, with Claude Code and Cursor paths: Connect Garmin to Claude in 6 minutes. For what to do after it works, read What AI can do for your training in 2026.

What the private link actually is

The link is not a public website. The random part is the credential. Claude calls that URL when you ask about sleep or a run. Garmin MCP then talks to Garmin with the session token from your sign-in and returns a small answer. GPS tracks stay out of the chat unless you ask for detail. That keeps the model fast and the reply readable.

Revoke is simple in spirit: delete the connector in Claude and email us to drop the token. Treat the URL like a house key. Do not paste it into a forum “why is this broken” thread.

This is why the easy Garmin MCP exists. GitHub servers ask you to run a command on your laptop. A hosted link lets the phone Claude app work on the tram after the run. Same protocol. Less ceremony.

People search “garmin mcp” and land on READMEs. Those pages assume you already know uv, tokens, and stdio. This page assumes you know how to run. If you can open Garmin Connect, you can use a Garmin MCP. The letters are for the machines. The link is for you. After it works, you never have to think about MCP again. You only think about the next session.