English Français العربية

livedot MCP

Registre officiel Cartes, voyage et météo

Find someone in a live running or cycling race, clubs and coaches near you, and race-day weather.

Code source Site web Documentation

Installation

Ajoutez ceci à la configuration MCP de votre client (Claude Desktop : claude_desktop_config.json ; Cursor : .cursor/mcp.json ; VS Code et les autres utilisent la même forme « mcpServers »).

Remote (streamable-http)
Claude Code 
claude mcp add --transport http livedot-mcp 'https://livedot.me/mcp'
Configuration JSON (Claude Desktop, Cursor, VS Code) 
{
    "mcpServers": {
        "livedot-mcp": {
            "type": "http",
            "url": "https://livedot.me/mcp"
        }
    }
}

Documentation

Tirée du README du projet sur GitHub, actualisée chaque semaine. Les liens ouvrent GitHub.

Sommaire
  1. livedot MCP
  2. Try it in 30 seconds
  3. What you can ask
  4. Tools
  5. How it works
  6. For the auditor
  7. Develop
  8. Keywords
  9. Links

livedot MCP

Live races, clubs and coaches, in ChatGPT and Claude.

Ask where someone is in a live race (“Where's Megan in the Comrades?”), which running or cycling club to join near you (“Which cycling club should I join in Johannesburg?”), or for a coach near you (“Running coach near Sandton”), and get the answer with a live map and the weather in the chat.

https://livedot.me/mcp · free · asking needs no sign-in

Try it in 30 seconds

The server URL is https://livedot.me/mcp (Streamable HTTP). No key, no account, no headers.

ChatGPT

  1. Settings → Apps & Connectors → Advanced settings: turn on Developer mode.
  2. Create: name livedot, MCP server URL https://livedot.me/mcp, authentication No authentication.
  3. Ask: “Where’s the demo runner in the Comrades demo?”

Claude (web and desktop)

  1. Settings → Connectors → Add custom connector.
  2. Name livedot, URL https://livedot.me/mcp.
  3. Ask: “Fly the Comrades.”

Claude Code

claude mcp add --transport http livedot https://livedot.me/mcp

Cursor (~/.cursor/mcp.json)

{ "mcpServers": { "livedot": { "url": "https://livedot.me/mcp" } } }

Any other MCP client: point it at https://livedot.me/mcp.

What you can ask

Real answers, word for word, on sample data and the apps' demo races.

“Where’s Megan in the Comrades?” (find_person, then where_is)

I found 20+ Megans in the Comrades. Here are the 5 most likely:

  1. Megan N. (livedot.me/megan), km 58, 6:20 /km, 18 min behind goal
  2. Megan B., km 61, 5:58 /km
  3. Megan N., km 66, 5:32 /km …

Megan N. is at km 58 (mile 36) of 90 km (56 mi) in the Comrades, 18 minutes behind the goal (9:00:00). Running at 6:20 /km (10:12 /mi). Where Megan is: 31°C (88°F), calm air at 5 km/h (3 mph), rated very hard (heat stress Extreme). The road ahead (km 57–69) rates Tough: Heat stress Extreme from km 57 (WBGT up to 32°) · Weather costs about 9 min (heat and humidity, from km 57). At this pace Megan finishes around 11:43 race time. Follow live: https://livedot.me/megan

Live tracking, proudly brought to you free thanks to ProLend.

“Fly the Comrades” (fly_route)

Here's the Comrades Marathon (demo) course from the air: 90 km (56 mi), with the weather along it. Press play on the map to fly it. … Rated Tough (Heat stress High from km 12, Extreme from 30 (WBGT up to 31°)). About 20°C (68°F) at the start and 27°C (81°F) at the finish. … Fly it in 3D: https://runfast.tech/live/race/comrades-demo

“What will the weather be like for the NYC Marathon?” (event_weather)

TCS New York City Marathon 2026: Sunday 1 November 2026, start 10:20 AM. Based on 10 years of weather on this date (Copernicus ERA5, 2015–2024), not a forecast. Rated Good. About 55°F (13°C) at the start and 58°F (14°C) at the finish. Heat stress Low. Rain on about 3 days in 10. … More: https://livedot.me/guides/nyc-marathon-2026-weather/

“What’s the ProLend 2027 Durban Tour route? Give me the GPX files.” (tour_route)

ProLend 2027 Durban Tour: 6 days, 771 km (479 mi). Day 1: Johannesburg to Villiers, 164 km (102 mi), 1,185 m of climbing, start 6:00. … Day 6: Greytown to Ballito, 134 km (83 mi), 1,883 m of climbing, start 6:00. The organiser hasn't made the route files available.

More to try: “How’s the demo club doing in the Comrades?” · “How’s the Coast Classic demo going?” · “Is Thandi racing?” · “Weather for the Gravel Burn?” · “What should I pack for the Durban tour?” · “What will the wind be like on this route on Saturday at 6?” (attach a GPX) · signed in: “Make my Saturday bunch ride a weekly club ride from this route.”

Tools

ToolWhat it does
find_personFinds someone racing live by name, livedot handle (@megan, livedot.me/megan) or follow link. One clear match answers at once. Several become a picker ranked live first, then the handle's owner, name closeness and taps on the back; the assistant asks one short question and never guesses. Narrow with event, surname, bib, club, place, wave.
where_isWhere someone is now: km and mile, time against their goal, pace, finish time, the temperature and wind there with the engine's rating, the next few km of wind and heat, and Follow live.
event_statusHow a live race is going: how long it's been under way, how many are on the map, how many finished, who's in front.
club_in_raceHow a club or team is doing in a live race (“How is the UCT team doing in the Comrades?”): each of its people on the club’s public live map, with km and goal time, the map with just the club’s dots, and a tap on a face for that person’s card. “Give the team a tap on the back” sends one to each member who takes taps. Try “the demo club in the Comrades” or “Coast Riders in the Coast Classic”.
event_weatherRace-day weather along the course at the times people get there. Inside 10 days, the live forecast; beyond, 10 years of weather on the date, labelled as history.
fly_routeA flyover of the course in the chat, coloured by the weather along it, with Fly it in 3D.
tour_routeA Windline cycling tour by name or organiser: every day (from and to, distance, climbing, start time), the map and the weather. A GPX link for each day only when the organiser shares route files; otherwise it says so.
tour_notesBeta. A tour organiser's own notes for riders (what to pack, meeting points), quoted in their words.

| tap_on_the_back | A tap on the back for someone racing live (only when you ask): it buzzes on their phone, through the same tap and rules as their follow page; in the day after their finish, a congratulation. Signed in, it carries your name; if not, the first name you give. | | find_clubs | Running and cycling clubs near a place ("best running club to join in Fourways"): approved clubs and organisers on RunFast and Windline, nearest first, with their weekly sessions, Beginners welcome, Open to anyone (or Members only), pace groups, the next session with its weather, the club's own links page (Club links), and Join to the club's page. beginners: true for beginner-friendly clubs; open: true for clubs anyone can join, no membership needed. Never a person. | | find_coaches | Cycling and running coaches and training groups near a place (“personal cycling trainer in Joburg”, “running coach near Sandton”): nearest first, with what they coach (road, MTB, gravel, triathlon, beginners, racing, marathon, ultra), how (1-on-1, small group, online), the next group session with its weather, Beginners welcome, the qualifications in their own words (never shown as verified), Book / contact (their own link) and See their page (livedot.me/<slug>). Filter with specialty, format, beginners. None near: Are you a coach? Get listed free. Try “cycling coach in Fourways” for the demo coach, Coach Thandi (demo). | | find_events | Rides, runs, races and tours near a place and when ("trail runs near Cape Town in November"), soonest first, with the weather (forecast inside 10 days, typical beyond) and I'm in to the event's page. Only published public events of approved clubs and organisers. | | plan_route | The weather along your own route (a GPX file, a Ride with GPS link, or the points or encoded polyline another app's tool gave, e.g. a route or activity map from a fitness app) at the time you'll ride or run it: the forecast inside 10 days, 10 years of weather beyond. Several files are one multi-day tour, ordered as create_event orders them. The map flies over your route in the chat, coloured by the weather; for a 3D flight and a video, save it as a private ride or run. No account. |

For organisers and club admins (sign in)

Connect your Windline or RunFast account and the assistant can work on your own events, exactly as your dashboard lets you:

ToolScopeWhat it does
list_my_eventsevents.readYour events: drafts, published and private, dates, distance, finished or not, with links; and the club and organiser pages you run.
create_eventevents.writeA ride, tour or race (Windline) or run or race (RunFast) from GPX files or links. Drop in several files and it's a tour: days ordered by the numbers in the file names (else by the map), named from the towns at each end, one day after another from your start; you check the plan once, then it's made. Private (just you: My Rides with its own private link, or a private run) or shared (a draft for a group, public once you publish it). Your tour notes for riders, up to 10,000 characters.
update_eventevents.writeName, description, notes, start dates and times. Never a finished event.
add_tour_notesevents.writeA Windline tour's notes for riders (what to pack, meeting points).
publish_eventevents.publishPublishes a draft, only after you confirm. Private events stay private.
invite_membersevents.writeInvite a club's members, or a published tour's riders, by email from a CSV (any delimiter, header or none). A preview first; each person gets one livedot email with Confirm, This wasn't me and Unsubscribe; nobody joins until they confirm; never twice; a day's limit of 500 for club admins and managers, 50 for a tour's organiser, 20 for an account under a week old.
post_club_rideclubs.postA draft group ride or club run on a club or organiser page you run (always the club's, never private). If you run a club and don't say who a ride is for, the assistant asks first.

“Make a two-day tour from these GPX files, starting 6 March at 6:00.” → a draft on your dashboard, with the weather for both days.

How sign-in works. OAuth 2.1 with PKCE and dynamic client registration, following the MCP authorization spec. livedot.me is the issuer (/.well-known/oauth-protected-resource, /.well-known/oauth-authorization-server) and passes /oauth/* to the authorization server, which runs on Windline (its Firestore holds the clients and the hashed tokens, server-only). You choose Windline or RunFast, then sign in on that app's own site (windline.tech/livedot/ or runfast.tech/livedot/) with the sign-in you already use (Apple, Google or email), so nothing about your password ever reaches livedot or the assistant. Access tokens last 15 minutes and refresh tokens 30 days, rotated on every use. Disconnect any time from Account → AI assistants in Windline or RunFast: it stops at once. Read tools and plan_route never need an account. Before you allow, the sign-in page shows where you'll be sent back to ("chatgpt.com", or "an app on this computer"); only ChatGPT returning to its own site and Claude returning to its own are shown as verified, and any other app is marked as unverified with the name it gave itself. Apps must return to an https address or to this computer.

Every tool declares a human title, honest annotations (readOnlyHint, destructiveHint, idempotentHint, openWorldHint) and an outputSchema for its structuredContent (src/schemas.js).

Prompts. track_someone (Track someone in a race), race_day_weather (Race-day weather) and fly_a_course (Fly a course). Resources. The live map (ui://livedot/live-map.html) and a short guide (livedot://guide). A static server card is at /.well-known/mcp/server-card.json.

On the free paths (no sign-in) an answer ends with one line to a free Windline or RunFast account (?ref=mcp), before the sponsor line; never on a signed-in answer.

Every tool takes units: metric or imperial. Without it, the asker's region decides (ChatGPT sends it); with neither, the event's country leads and the other system follows in brackets: “km 79 (mile 49)”. All tools are read-only (readOnlyHint).

How it works

  • Live, from the apps. Positions, goals and finish times come from Windline (cycling) and RunFast (running): the same public live pages anyone can open on livedot.me.
  • One forecast engine. Weather by the Windline engine, served from livedot.me: the same engine as the apps and every livedot page, so the numbers match everywhere. Apple Weather for the next 10 days; 10 years of Copernicus ERA5 records beyond. The engine is Windline's and isn't in this repository or under its licence: scripts/build.mjs fetches it from windline.tech/engine-core.js when the server is built.
  • A map in the chat. One MCP Apps UI resource (ui://livedot/live-map.html) that Claude and ChatGPT render inline: always a light map (OpenFreeMap), never a per-tile map key. Clients without widgets get the full answer as text.

Privacy. Only people who chose to be findable, on public races; the organiser tools only ever touch the signed-in person's own events; no position when someone has stopped or is near the start or finish; names as “Megan N.”; nothing kept about who asked.

For the auditor

A position (km, mile, map dot, the weather there) is shared only when the public follow answer gives one and the person is moving (live, delayed, no signal). Paused, stopped, not started, hidden near the start or finish, private or not shared: “I can't share where they are right now.” Route files only when the organiser's own switch (routeFiles) is on. Every read is in src/reads.js.

Develop

node scripts/build.mjs                 # fetch the engine, build the widget and the event list
node test/smoke.mjs                    # every tool, on sample data and the apps' public demos
node test/fixture-api.mjs              # sample data on :8790
npx @modelcontextprotocol/inspector    # connect to your server's /mcp (Streamable HTTP)
MCP=http://localhost:8788/mcp node test/shots.mjs   # the screenshots in docs/shots, at 3x

src/server.js is the whole server (handle(request, env)); on livedot.me it runs as a Cloudflare Pages Function. src/schemas.js holds the tools' output schemas and the prompts.

Keywords

Live tracking · race tracker · marathon tracker · cycling race tracking · Comrades tracker · marathon weather · race-day weather forecast · cycling tour GPX · ChatGPT app · Claude connector · MCP server · Model Context Protocol

livedot.me · windline.tech (cycling) · runfast.tech (running) · Privacy · Terms · hello@windline.tech

Live tracking, proudly brought to you free thanks to ProLend.

MIT licensed. The Windline forecast engine is not part of this repository.

Questions fréquentes

Qu'est-ce que livedot MCP ?

Find someone in a live running or cycling race, clubs and coaches near you, and race-day weather.

Comment installer livedot MCP ?

Il fonctionne comme serveur distant. Dans Claude Code : claude mcp add --transport http livedot-mcp 'https://livedot.me/mcp'. Pour les autres clients, collez la configuration JSON de cette page dans leurs réglages MCP.

Faut-il une clé API pour livedot MCP ?

Son entrée au registre n'indique aucune clé ni secret obligatoire. Certaines fonctions peuvent tout de même demander un compte auprès du service auquel il se connecte.

livedot MCP est-il open source ?

Oui. Son code est sur GitHub sous licence MIT.

Qui maintient livedot MCP ?

Il est publié par livedotme. AI.tn le référence sans le maintenir ni le recommander.

Issu du registre MCP officiel. Être listé n'est pas une recommandation : vérifiez le code et les permissions d'un serveur avant de lui donner accès à vos données.