← All Resources

Connecting Garmin to an AI Assistant: Your Options

October 5, 2026·Simma
Simma Guidesgarminmcpclaudechatgptai assistantconnectors

Connecting Garmin to an AI Assistant: Your Options

An AI assistant can't see your Garmin data on its own. Something has to sit between the two: it signs in to Garmin for you, fetches your sessions, and hands them to Claude, ChatGPT or whichever assistant you use. That something is called a connector, or an MCP server, after the protocol the assistants use to talk to outside tools.

A year ago there were one or two of these. Now there are dozens, and they are not the same thing with different names. This page sets out the kinds that exist, five questions that separate them, and how the ones we know of answer those questions. Simma is one of them, and it is in the list on the same terms as the rest.

The three kinds

A server you run yourself. Open-source projects you install on your own computer. Your data goes from Garmin to your machine to your assistant and nowhere else. You need to be comfortable with a terminal, and it is yours to keep running.

A hosted connector. Someone else runs the server. You sign in, paste one address into your assistant, and it works on your phone as well as your laptop. Most of these pass Garmin's own numbers straight through to the assistant.

A training platform with a connector. A service that already holds and analyses your training, and has added a way for an assistant to read it. The assistant gets the platform's computed view, not only what Garmin shows.

Five questions to ask of any of them

1. How does it sign in to Garmin?

There are two ways, and they are very different.

Garmin runs an official programme for companies that want access to its users' data. A service in that programme sends you to Garmin's own page, where you choose what to share and press Agree. The service never sees your Garmin password, and you can withdraw access from your Garmin account at any time.

The other way is for the connector to sign in as you, with your Garmin email and password, and read the same pages the Garmin Connect app reads. Most open-source servers work like this, through a community library, and several hosted ones do too. Many use the password once and keep only a sign-in token afterwards. It works, and for a server on your own machine it may be all you need. It also depends on parts of Garmin that Garmin has not published and can change.

Ask which one it is. A page that says "sign in with your Garmin email and password" has told you.

2. Where does your data go, and is it kept?

Some connectors fetch a number when the assistant asks for it and keep nothing. Some keep a copy so they can answer faster or work things out across months of history. Neither is wrong. Keeping nothing means less to trust; keeping history is what makes comparisons with your own past possible. What matters is that the page says which, and what happens when you leave.

3. Does it compute anything, or pass Garmin's numbers through?

A pass-through connector gives the assistant what Garmin Connect already shows: the activity summary, sleep, Body Battery, VO2 max. The assistant then does any further arithmetic itself, in the conversation, each time you ask.

A connector that computes has done that work before the question arrives, the same way every time: training load against your own history, thresholds estimated from your own sessions, the sets inside a swim. The assistant reads a result instead of deriving one.

4. Who runs it, and what happens if they stop?

A hosted connector is a person or a company holding a key to your Garmin data. Several good ones are run by one developer in their spare time, and say so. Look for who they are, how it is paid for, and whether there is a privacy policy.

5. Can it change things, or only read?

Some connectors only read. Others can rename activities, log food, or build a workout and put it on your watch. Writing is useful and it raises the stakes of a mistake. Check which it is, and whether the assistant has to ask you first.

How the options we know of answer them

Checked on 5 October 2026. Everything below comes from each project's own public page, linked in its entry. We have not used all of them, and this field changes quickly. If an entry is wrong or out of date, tell us at coaching@getsimma.com and we will correct it.

Servers you run yourself

Taxuspt/garmin_mcp (open source)

There are many others of this kind, most built on the same library: eddmann/garmin-connect-mcp and Nicolasvegam/garmin-connect-mcp are two.

Hosted connectors

Garmin Chat Connector (an independent project, not from Garmin)

MissingMCP (run by one developer)

stats.training

athletedata

Training platforms with a connector

Tredict, AI Endurance and Training Tilt each publish a connector for their own platform. Training Tilt's is for coaches: the assistant sees what the coach's login sees, and any change is shown to the coach for approval first. intervals.icu has several community-built servers.

Simma

Choosing

If you want your data to stay on your own machine and you are at home in a terminal, a server you run yourself does that and costs nothing.

If you want to ask about last night's sleep or this morning's run from your phone, a hosted pass-through connector is the shortest path. Read how it signs in to Garmin before you give it your password.

If you want the assistant to reason from numbers that were worked out the same way every time, across months of your own history, that is what a platform with a connector is for. Simma is the one we build: start with Claude or ChatGPT, or see every tool the connector offers.

Tell us what is missing

What do you want your assistant to be able to do with your training data that none of these does yet? Three we have been asked for: read a second watch brand alongside Garmin, compare a planned week with the week that happened, and put a session on the watch from a conversation. Write to coaching@getsimma.com with the tool you want and we will build it.