About F1 Data Server
F1 Data Server is an MCP server for querying Formula 1 results, timing, telemetry, strategy, standings, and session information. It is aimed at F1 analysis through clients such as Claude Desktop, combining historical and live data sources with local caching.
Key features
- 01Race and qualifying results
- 02Driver telemetry comparisons
- 03Lap times and sector data
- 04Tyre and pit-stop strategy
- 05Standings and historical records
- 06Live session and weather data
Use cases
- 01Review a Grand Prix's race results
- 02Compare driver telemetry in qualifying
- 03Inspect lap times and tyre strategy
- 04Check current standings and session status
MCP support
Exposes Formula 1 data and analytics through MCP tools for clients such as Claude Desktop. The server provides more than 36 tools.
Configuration
Local server config is the same for every client. Copy it into your client’s MCP config file.
Tools
Local servers expose tools only once running on your machine, and the maintainer has not provided a tool list.
Details
From the project READMEF1 MCP Server
A Model Context Protocol (MCP) server that provides comprehensive Formula 1 data and analytics for Claude Desktop integration.
Features
This server exposes 36+ tools for accessing F1 data:
Race Data
- Race results and classifications
- Sprint race results
- Qualifying progression (Q1, Q2, Q3)
- Grid vs finish comparisons
- DNF lists and retirement reasons
Telemetry & Analysis
- Speed trace comparisons between drivers
- Gear shift visualizations
- Brake and throttle analysis
- RPM and engine data
- DRS usage patterns
Timing & Laps
- Fastest lap data with sector times
- Lap-by-lap timing
- Deleted laps (track limits)
- Lap consistency statistics
- Personal best laps
Strategy
- Tire compound analysis
- Stint breakdowns
- Pit stop data and fastest stops
- Starting tire choices
- Strategy comparisons
Standings & History
- Driver championship standings
- Constructor standings
- Historical race winners
- Track records
Live Data
- Live session status
- Real-time positions
- Live lap times
- Live telemetry
- Current weather conditions
Other
- Team radio links
- Race control messages
- Track status (flags, safety car)
- Weather data
- Circuit information
Installation
Prerequisites
- Python 3.10 or higher
- Claude Desktop
Setup
- Clone this repository:
git clone https://github.com/drivenrajat/f1.git
cd f1
- Create a virtual environment:
python -m venv venv
source venv/bin/activate # On Windows: venv\Scripts\activate
- Install dependencies:
pip install -e .
Configure Claude Desktop
Add this server to your Claude Desktop MCP configuration (~/Library/Application Support/Claude/claude_desktop_config.json on macOS):
{
"mcpServers": {
"f1": {
"command": "python",
"args": ["/path/to/f1/f1_server.py"]
}
}
}
Or if using uv:
{
"mcpServers": {
"f1": {
"command": "uv",
"args": ["run", "--directory", "/path/to/f1", "python", "f1_server.py"]
}
}
}
Usage
Once configured, you can ask Claude questions like:
- "Show me the 2024 F1 calendar"
- "Get the race results from Monaco 2024"
- "Compare telemetry between Verstappen and Norris at Silverstone qualifying"
- "What was Hamilton's tire strategy at Spa?"
- "Show me the current driver standings"
- "Get the fastest pit stops from the Italian GP"
Data Sources
- FastF1: Historical telemetry, lap times, and session data
- Ergast API: Championship standings and historical results
- OpenF1 API: Team radio recordings
Caching
The server automatically caches FastF1 data in a cache directory to improve performance on repeated queries.
License
MIT License - see LICENSE for details.
Contributing
Contributions are welcome! Please feel free to submit a Pull Request.
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.