formula1

The Formula1 MCP Server brings both historical Formula 1 data and live telemetry into the Model Context Protocol ecosystem. It exposes a set of tools to fetch historical results, timing data, driver and constructor standings, weather, pit stops, team radios, and more, sourced from OpenF1 (free historical data) and Ergast (legacy data). Real-time live data and MQTT streaming are supported for active sessions, though live streaming requires a paid OpenF1 account. When active, you can retrieve current car telemetry, positions, weather, and race control messages via the live tools, or fall back to REST endpoints for delayed data.

To use the server with Claude Desktop (or any MCP client), configure your mcpServers entry to point to the Node build output. The server provides tools such as getLiveCarData, getLivePositions, getLiveWeather, getHistoricRaceResults, getDriverStandings, getLapTimes, and getWeatherData, among others. Historical tools require you to first obtain a session key via getHistoricalSessions before requesting data tied to a specific race. REST endpoints are generally available for historical data, while live data requires an active session and, in some cases, paid OpenF1 access.

Prerequisites:

• Git
• Node.js (LTS version) and npm
• Basic CLI environment (bash/zsh or PowerShell)

1. Clone the repository:

git clone https://github.com/Panth1823/formula1-mcp
cd formula1-mcp

2. Install dependencies:

npm install

3. Build the project:

npm run build

4. Run the MCP server (example):

# Ensure you are in the project root and the build/index.js path exists
node build/index.js

5. Update your Claude/CLAUDE_DESKTOP config with the provided mcp_config snippet (see documentation in this repo) to enable the Formula1 MCP server within your MCP client.

Notes and tips:

• Historical data is free; live streaming and real-time data require paid OpenF1 access. REST endpoints may work during race weekends for delayed data even without a paid account.
• Live data tools: getLiveCarData, getLivePositions, getLiveWeather, getLiveRaceControl, getLiveTeamRadio, getStreamingStatus. Some data sources are MQTT-based (live) with fallback to REST.
• Before using historical tools, you may need to call getHistoricalSessions to discover session keys for specific races.
• If you encounter path or build errors, ensure the built output exists at <repo>/build/index.js and that your mcp_config points to that file.
• The MQTT streaming endpoint for live data is currently disabled in the public configuration; enable access via OpenF1 if you have a paid account and update environment/config accordingly.