Use FlaMap with your AI assistant

FlaMap has an MCP server. It lets an AI assistant you already use (Claude, ChatGPT, Cursor and others) read your own rides, climb efforts, routes and profile, so you can ask about them in plain words. Nothing is shared automatically: your assistant sees your data only after you connect it yourself, and only when you ask it something.

Server URL   https://api.flamap.app/mcp
Transport    Streamable HTTP
Sign-in      OAuth 2.1 (you sign in to FlaMap and approve the connection)
Access       read-only, your own data only

Who can use it

Any FlaMap account. It is free and there is nothing to turn on in FlaMap.

Your AI client may have its own requirements:

Connect

Pick your assistant. Each page has the steps, a check that it worked, and how to disconnect.

• Claude (web, desktop and mobile)
• Claude Code
• ChatGPT
• Cursor
• VS Code
• Gemini CLI

Every client ends the same way. A browser page opens on flamap.app. You sign in to FlaMap (with Google or an 8-digit code FlaMap emails you), and you see which app is asking, what it will be able to read, and where your data goes. To approve, you first tick a box giving your explicit consent to share your health-related data (heart rate, HRV, weight) and detailed activity data (ride metrics such as power, speed and elevation over time) with that assistant, including outside the EU. Your GPS tracks, the exact route of your rides and where they start and end are never shared. Then you go back to your assistant. You can deny instead without ticking anything. Every connection is approved through the box: connections made before 26 September 2026 were revoked and must be approved again. The privacy page has the full consent text.

What to ask

Start with anything you would ask a coach who can see your training log. Some examples:

Analysis

• "How has my eFTP changed this year, and why?"
• "Am I riding more than at this time last year?"
• "Did I fade in the second half of Saturday's ride?"

Climbs

• "What is my best time up Coll de Montcau, and how does this year compare?"
• "Find a climb near Manresa for 8-minute intervals."
• "Which of my saved climbs have I never ridden?"

Routes

• "How much of my Gravel Sunday route is unpaved?"
• "Here is a GPX file. How hard is it for me, and which climbs does it cross?"
• "Which of my planned routes has the most climbing per kilometre?"

Data questions

• "What is my average power on climbs steeper than 6%, by month?"
• "How many rides over 100 km did I do each year?"
• "Which weekday do I ride the most kilometres on?"

Some clients also offer four ready-made prompts from FlaMap: season review, why did my FTP change, climb for intervals, and ride analysis. See the tool reference.

What your assistant can and cannot see

It can read:

• Your rides: date, sport, name, description, distance, time, elevation, power, heart rate, cadence, calories, the eFTP that applied that day, laps, pauses, HRV, and the town and country where the ride started.
• Your ride streams (power, heart rate, cadence, speed, elevation, distance, temperature), reduced to 500 points per ride unless your assistant asks for more (2000 at most). No GPS positions.
• Your efforts on catalogued climbs, your saved climbs, and the public climb catalogue.
• Your planned routes: distance, climbing, expected time, surface and the climbs on them.
• Your profile: FTP, weight, age in whole years, units, timezone and default sport.
• Through the query tool only: the rest of your profile as you filled it in (username, gender, height, language, location name) and the devices recorded with each ride.

It never gets the start or end point or the map line of a ride, any position within 500 m of where a ride starts or ends, or your date of birth. The privacy page has the exact rules.

It cannot:

• Change anything. Every tool is read-only. FlaMap also refuses any write from a connected app, even if the app tried.

• See other riders. Every request is limited to your account in the database itself.

• See your linked accounts. Tokens for services you connected to FlaMap are never readable.

• See your share links, or the GPS track and navigation waypoints of your planned routes.

• See your email address or password.

The full list of tools, with parameters and limits, is in the tool reference. How we handle your data is in the privacy page.

Limits

These keep the service fast for everyone. When your assistant hits one, it gets a short message and can try again a moment later.

Ride streams are the expensive part. A long ride with many channels fills a lot of your assistant's context. Ask about one ride at a time when you want second-by-second detail.

A word on AI answers

Your assistant writes the answer, not FlaMap. It can misread a number, mix up two rides or state a guess as a fact. Check anything that matters against the ride in FlaMap. It is not medical advice, and it is not a coach who knows how you feel.

What your assistant does with your data after it reads it is set by the assistant's provider (Anthropic, OpenAI, Google, Cursor, GitHub), which is responsible for it from then on. Most of them are in the United States, so your data may leave the EU. Read their policy on chat history, retention and training. The privacy page explains the transfer.

Troubleshooting

"The FlaMap session has expired. Ask the rider to reconnect this connector." Your sign-in ran out or was revoked. Reconnect from your client (each connect page says how). You will sign in to FlaMap again.

Approve is greyed out. Tick the consent box above the buttons. FlaMap cannot connect an assistant without your explicit consent to share health-related and activity data. If you would rather not share them, select Deny: nothing is shared.

The sign-in email does not arrive. Check spam. You can ask for a new code after 60 seconds. The code is valid for one hour. Use the same email as your FlaMap account: the page does not create new accounts.

Claude Free will not let you add FlaMap. The Free plan allows one custom connector. Remove the other one under Customize → Connectors, or use a paid plan. This is a Claude limit, not a FlaMap one.

ChatGPT: there is no way to add a server. You need Developer mode, on ChatGPT for the web. See Connect ChatGPT.

Your assistant does not use FlaMap. Make sure the connector is turned on for this chat, then name it: "Using FlaMap, what did I ride last week?"

"rate limit: 60 calls per minute; wait a moment". Your assistant asked for too much at once. Wait a minute, or ask a narrower question.

"Query rejected: …". The SQL was not a single SELECT, or it took longer than 5 seconds. Ask your assistant to narrow the date range or aggregate first.

The ride has no streams. Some rides have no second-by-second recording. The summary tools still work for them.

Changelog

• 2026-10-01: get_climbs returns the climbs you ask for (it returned none before).
• 2026-09-30: each assistant connection signs in to its own database role; the SQL tool no longer sees your date of birth, ride start and end points or route waypoints; connecting asks for explicit consent; sign in with Google or an emailed code; manage connections at flamap.app/settings/ai-assistants.
• 2026-09-25: first release: 15 read-only tools, 2 resources, 4 prompts.

Support

Write to support@flamap.app and mention "AI assistant". Tell us which client you use and the time it went wrong. Do not send us your sign-in code or any token.