MCP Sport — F1 Telemetry MCP 🏎️
An MCP (Model Context Protocol) server that exposes Formula 1 data from the OpenF1 API as tools for AI assistants (Claude Desktop, Cursor, MCP Inspector, etc.).
Full coverage: 18 data tools matching the 18 documented OpenF1 endpoints — sessions, meetings, drivers, results, laps, pit stops, stints, telemetry, weather, championships and more. Two MCP App views sit on top of that data: a drivers standings board and an animated race replay. Hosts that render MCP Apps show the HTML. Cursor and Claude Desktop do not: they return the same payload as JSON.
Stack
| Layer | Technology |
|---|---|
| Language | Python 3.13+ |
| MCP framework | FastMCP 4.x |
| Validation | Pydantic v2 |
| Data | OpenF1 API (REST, free for historical data 2023+) |
| Project management | uv + pyproject.toml |
| Transport | stdio |
Installation
# Clone and install dependencies
git clone https://github.com/andrequeiroz2/mcp-sport.git mcp-sport
cd mcp-sport
uv sync
Usage
Run the server (stdio)
.venv/bin/python src/mcp_sport/server.py
MCP Inspector (web UI to test the tools)
npx @modelcontextprotocol/inspector@latest .venv/bin/python src/mcp_sport/server.py
In the Inspector UI: transport STDIO, command .venv/bin/python,
args src/mcp_sport/server.py → Connect.
Claude Desktop / Cursor
Add to the client's MCP configuration:
{
"mcpServers": {
"f1-telemetry": {
"command": "/absolute/path/mcp-sport/.venv/bin/python",
"args": ["/absolute/path/mcp-sport/src/mcp_sport/server.py"]
}
}
}
The 18 data tools work in both clients. The views do not render there.
Views (MCP Apps)
get_drivers_championship_view and get_race_replay_view return interactive
HTML. Cursor and Claude Desktop are incompatible with MCP Apps: they
ignore the UI and show the JSON payload. The MCP Inspector also treats the
result as text.
The views were validated in the official
basic-host
from modelcontextprotocol/ext-apps.
The server must be HTTP, with CORS exposing the MCP session headers.
Otherwise the browser cannot complete the Streamable HTTP handshake.
Terminal 1 — MCP server on port 8765:
uv run python -c "
import uvicorn
from starlette.middleware import Middleware
from starlette.middleware.cors import CORSMiddleware
from mcp_sport.server import mcp
app = mcp.http_app(middleware=[Middleware(
CORSMiddleware,
allow_origins=['*'],
allow_methods=['*'],
allow_headers=['*'],
expose_headers=['mcp-session-id', 'mcp-protocol-version'],
)])
uvicorn.run(app, host='127.0.0.1', port=8765)
"
Terminal 2 — basic-host (needs Node.js; npm start requires bun, so use tsx):
git clone --depth 1 https://github.com/modelcontextprotocol/ext-apps.git
cd ext-apps/examples/basic-host
npm install
npm run build
SERVERS='["http://127.0.0.1:8765/mcp"]' npx tsx serve.ts
Open http://localhost:8080 (sandbox on :8081) and call
get_drivers_championship_view or get_race_replay_view. After a change to
the view HTML, hard-refresh the page (Ctrl+Shift+R) before running the tool
again. The host caches the ui:// resource.
Available tools (18)
| Domain | Tool | Description |
|---|---|---|
| Navigation | get_sessions |
Sessions (practice, qualifying, sprint, race) |
get_meetings |
Grand Prix and testing weekends | |
| Registry | get_drivers |
Drivers by session/meeting |
| Results | get_session_results |
Final classification of a session |
get_starting_grid |
Starting grid | |
get_positions |
Position history throughout a session | |
| Race | get_laps |
Lap times, sectors and speeds |
get_pit_stops |
Pit stops | |
get_stints |
Stints and tyre compounds | |
get_intervals |
Real-time gaps (leader and car ahead) | |
get_race_control |
Flags, safety car, incidents | |
| Context | get_weather |
Track weather (per-minute samples) |
get_overtakes |
Overtakes | |
get_team_radio |
Team radio excerpts (MP3) | |
| Telemetry | get_car_data |
Speed, RPM, gear, throttle, brake, DRS (~3.7 Hz) |
get_location |
Approximate car position on the circuit (~3.7 Hz) | |
| Championships | get_drivers_championship |
Drivers standings (beta) |
get_teams_championship |
Teams standings (beta) |
Example conversation with the AI
"How many points did Norris score in the last two races?"
The AI orchestrates: get_sessions(session_type="Race") to discover recent
sessions → get_session_results(session_key=..., driver_number=4) on each one.
Project structure
src/mcp_sport/
├── server.py # Entrypoint: FastMCP instance + tool registration
├── exceptions.py # Domain exceptions
├── logging_config.py # Logging to stderr (stdout is the protocol channel)
├── clients/openf1.py # Single OpenF1 HTTP client
├── schemas/ # Pydantic: input (BaseInput) and output per endpoint
├── validators/ # Business validations per endpoint
├── services/ # Orchestration per endpoint
├── tools/ # MCP tools (thin layer) per endpoint
└── apps/ # MCP App views (Custom HTML, ui:// resource)
├── championship_view.py # Drivers standings board
└── race_replay_view.py # Animated race replay
Canonical documentation
| Document | Contents |
|---|---|
docs/Technical_Reference.md |
Stack, versions and official links (source of truth) |
docs/Architectural_Design.md |
Implementation patterns and procedure for new endpoints |
docs/Logging_Strategy.md |
Logging strategy (stderr + per-request telemetry) |
tasks/ |
History of planned and executed tasks |
Configuration
| Variable | Default | Description |
|---|---|---|
MCP_SPORT_LOG_LEVEL |
INFO |
Log level on stderr (DEBUG, INFO, WARNING, ERROR) |
Known limitations
- Historical data from 2023 onwards; real-time data requires a paid OpenF1 subscription
session_resultandstarting_gridreturn HTTP 404 until official results are published- Telemetry (
car_data,location) returns 18–24k samples per session/driver. Narrow the call with range filters such asspeed_minanddate_from/date_to - Championship endpoints are in beta on OpenF1
License
MIT. OpenF1 is an unofficial project, not associated in any way with the Formula 1 companies.
Metadata
Release files for mcp-sport 0.1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| mcp_sport-0.1.0.tar.gz | 41.6 kB | Without provenance | Details for mcp_sport-0.1.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| mcp_sport-0.1.0-py3-none-any.whl | Python 3 | none | any | Details for mcp_sport-0.1.0-py3-none-any.whl |
Total release size: 129.3 kB
Release files / mcp_sport-0.1.0.tar.gz
| Download URL | mcp_sport-0.1.0.tar.gz |
|---|---|
| Size | 41.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
32e2318a448f441c5b6cdb8eb3789321f5f67d9edbed3e8c0dc47b0e6ff09640
|
|
BLAKE2b-256 checksum How to use checksums |
5dd8401bf90f687e7012c2d8f19a339b1edcb5d46b3243ff4b49c58c8fa358d4
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
uv/0.12.17 {"installer":{"name":"uv","version":"0.12.17","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"24.04","id":"noble","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}
|
Release files / mcp_sport-0.1.0-py3-none-any.whl
| Download URL | mcp_sport-0.1.0-py3-none-any.whl |
|---|---|
| Size | 87.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
0ffc7ecdd16011b732867acb5e156c752893a31d3e816d409f7a596ea19710a0
|
|
BLAKE2b-256 checksum How to use checksums |
4d0f7c68f2a78ac7eee0901052405bc0fa4bb4e11d96696c650045b009e2b287
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
uv/0.12.17 {"installer":{"name":"uv","version":"0.12.17","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"24.04","id":"noble","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}
|
Security for mcp-sport 0.1.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.