fastf1-mcp-server
MCP server for Formula 1 data via the FastF1 library. Ask Claude (or any MCP-compatible client) about race results, lap times, telemetry, standings, pit stops, and qualifying — with historical data back to 1950 via the Ergast API.
README
fastf1-mcp
An MCP server that exposes Formula 1 data to AI assistants via the FastF1 library. Ask Claude (or any MCP-compatible client) questions about race results, lap times, telemetry, standings, and more.
Features
- 21 tools covering standings, race results, lap times, telemetry, pit stops, and qualifying
- 4 MCP resources for schedule, driver, constructor, and circuit reference data
- 5 guided prompts for race recaps, qualifying analysis, strategy deep-dives, and weekend previews
- Async-safe LRU session cache — repeat queries are instant after the first load
- Distance-based telemetry sampling — large raw datasets compressed to ≤ 500 points
- All errors returned as structured dicts — the server never crashes on bad input
Requirements
- Python 3.12+
- uv (recommended) or pip
Installation
With uv (recommended)
git clone https://github.com/Surya96t/fastf1-mcp
cd fastf1-mcp
uv sync
With pip
pip install fastf1-mcp-server
Running the server
# via uv (development)
uv run fastf1-mcp-server
# or directly
python -m fastf1_mcp
MCP Inspector (development / debugging)
# Option A — official npx inspector
npx @modelcontextprotocol/inspector uv --directory . run fastf1-mcp-server
# Option B — fastmcp wrapper
uv run fastmcp dev inspector -m fastf1_mcp.server --with-editable .
Both open the inspector at http://localhost:6274.
Claude Desktop configuration
Add the following to ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows):
{
"mcpServers": {
"fastf1": {
"command": "uv",
"args": ["run", "fastf1-mcp-server"],
"cwd": "/absolute/path/to/fastf1-mcp",
"env": {
"FASTF1_MCP_LOG_LEVEL": "INFO",
"FASTF1_MCP_MAX_CACHED_SESSIONS": "10"
}
}
}
}
Restart Claude Desktop after saving. The server name fastf1 will appear in the tools panel.
Configuration
All settings are read from environment variables with the FASTF1_MCP_ prefix.
| Variable | Default | Description |
|---|---|---|
FASTF1_MCP_FASTF1_CACHE_PATH |
~/.fastf1_cache |
Disk cache for FastF1 session files |
FASTF1_MCP_MAX_CACHED_SESSIONS |
10 |
Max sessions held in memory (LRU) |
FASTF1_MCP_DEFAULT_TELEMETRY_SAMPLES |
200 |
Default telemetry sample points |
FASTF1_MCP_MAX_TELEMETRY_SAMPLES |
500 |
Hard cap on telemetry sample points |
FASTF1_MCP_LOG_LEVEL |
INFO |
Python logging level |
Tools
Quick Lookup (Ergast API — 1950-present)
| Tool | Description |
|---|---|
get_schedule |
Get the F1 race calendar for a season. |
get_driver_standings |
Get driver championship standings. |
get_constructor_standings |
Get constructor championship standings. |
get_driver_info |
Get driver information. |
get_race_results_historical |
Get historical race results (pre-2018 or when session data unavailable). |
get_circuit_info |
Get circuit information. |
Session Data (FastF1 Live Timing — 2018-present)
| Tool | Description |
|---|---|
get_session_results |
Get session classification/results. |
get_lap_times |
Get all lap times for a driver in a session. |
get_fastest_laps |
Get fastest laps in a session, one per driver. |
get_race_pace |
Calculate average race pace for all drivers. |
get_stint_analysis |
Analyze tire stints for a race. |
get_pit_stops |
Get all pit stops from a race. |
get_qualifying_breakdown |
Get qualifying results split by Q1/Q2/Q3. |
Telemetry (FastF1 Live Timing — 2018-present)
| Tool | Description |
|---|---|
get_lap_telemetry |
Get telemetry data for a specific lap. |
compare_telemetry |
Compare telemetry between two drivers on the same session. |
get_speed_trap_data |
Get speed trap and top-speed data for all drivers in a session. |
get_sector_times |
Get best sector times and theoretical best lap for each driver. |
Utility
| Tool | Description |
|---|---|
list_events |
List all events in a season. |
list_drivers |
List all drivers in a season, optionally filtered to a specific event. |
get_cache_status |
Check server in-memory session cache status. |
clear_cache |
Clear cached sessions from in-memory storage. |
Resources
| URI | Description |
|---|---|
f1://schedule/{year} |
Full race calendar for a season |
f1://drivers/{year} |
All drivers who competed in a season |
f1://constructors/{year} |
All constructors in a season |
f1://circuits |
All F1 circuits (all-time) |
Prompts
| Prompt | Args | What it does |
|---|---|---|
race_recap |
year, event |
Calls results + fastest laps + pit stops + stints, then narrates the race |
qualifying_analysis |
year, event |
Q breakdown + sector times + top laps analysis |
driver_comparison |
year, driver1, driver2 |
Season-level head-to-head: standings, races, qualifying |
strategy_analysis |
year, event |
Stints + pit timing + race pace — explains who won the strategy battle |
weekend_preview |
year, event |
Circuit details + recent history + championship context |
Example queries (Claude Desktop)
Who won the 2024 Monaco Grand Prix and what was the strategy?
→ use race_recap prompt or call get_session_results + get_stint_analysis
Compare Verstappen and Leclerc's telemetry in 2024 Monaco qualifying
→ compare_telemetry(2024, "Monaco", "Q", "VER", "LEC")
Who had the fastest theoretical lap in 2024 Silverstone qualifying?
→ get_sector_times(2024, "Silverstone", "Q")
Show me the 2024 constructor standings after round 10
→ get_constructor_standings(2024, after_round=10)
Development
# Install dev dependencies
uv sync --dev
# Run tests
uv run pytest
# Run tests with coverage
uv run pytest --cov=fastf1_mcp
# Lint
uv run ruff check src/
Data sources & coverage
| Source | Coverage | Used for |
|---|---|---|
| Ergast API (via FastF1) | 1950 – present | Standings, schedules, historical results, circuit info |
| FastF1 Live Timing | 2018 – present | Lap times, telemetry, qualifying, pit stops, tire data |
Note: FastF1 session data is only available from 2018 onwards. Use
get_race_results_historicalfor earlier seasons.
License
MIT
Recommended Servers
playwright-mcp
A Model Context Protocol server that enables LLMs to interact with web pages through structured accessibility snapshots without requiring vision models or screenshots.
Magic Component Platform (MCP)
An AI-powered tool that generates modern UI components from natural language descriptions, integrating with popular IDEs to streamline UI development workflow.
Audiense Insights MCP Server
Enables interaction with Audiense Insights accounts via the Model Context Protocol, facilitating the extraction and analysis of marketing insights and audience data including demographics, behavior, and influencer engagement.
VeyraX MCP
Single MCP tool to connect all your favorite tools: Gmail, Calendar and 40 more.
graphlit-mcp-server
The Model Context Protocol (MCP) Server enables integration between MCP clients and the Graphlit service. Ingest anything from Slack to Gmail to podcast feeds, in addition to web crawling, into a Graphlit project - and then retrieve relevant contents from the MCP client.
Kagi MCP Server
An MCP server that integrates Kagi search capabilities with Claude AI, enabling Claude to perform real-time web searches when answering questions that require up-to-date information.
E2B
Using MCP to run code via e2b.
Neon Database
MCP server for interacting with Neon Management API and databases
Exa Search
A Model Context Protocol (MCP) server lets AI assistants like Claude use the Exa AI Search API for web searches. This setup allows AI models to get real-time web information in a safe and controlled way.
Qdrant Server
This repository is an example of how to create a MCP server for Qdrant, a vector search engine.