Introduction

An MCP server that exposes the public Tour de France Race Center API as 22 tools.

The Tour de France MCP server is an HTTP Model Context Protocol server that wraps the public Tour de France Race Center API (https://racecenter.letour.fr) and exposes it to LLM clients as 22 read-only tools.

It is built with mcp-framework and runs over the Streamable HTTP transport. The upstream API is public and requires no authentication, so no API keys are needed to use this server.

What you can ask it

Once connected, a model can answer questions like:

"Who is leading the general classification after stage 12 of the 2026 Tour?"
"List every rider on Team UAE Emirates with their bib numbers."
"What's the route profile and distance of tomorrow's stage?"
"Give me the live gaps between the breakaway and the peloton right now."

Quickstart

Connect an MCP client to the public endpoint in under a minute.

Conventions

Shared parameters, pagination, compact responses and live-data behaviour.

Tool reference

All 22 tdf_* tools, grouped by domain.

Architecture

How the server and this docs site are deployed on AWS.

Highlights

Self-identifying tools. Every tool is prefixed tdf_ and every description names "Tour de France", so tools stay recognisable even when a client shows the server under an opaque id.
Compact by default. Backend bookkeeping keys are stripped and the two heavy tools (tdf_stages, tdf_riders) shrink dramatically unless you ask for the full payload.
Pagination everywhere. Every list tool accepts limit / offset.
Safe to poll gently. The server is a thin, read-only proxy over an unofficial ASO feed — no writes, no side effects.

This server talks to an unofficial feed reverse-engineered from the official race site. It can change without notice — keep request rates gentle.