The Formula1 MCP Server ! 🏎️💨

What is The Formula1 MCP Server ! 🏎️💨?

A TypeScript-based Formula 1 MCP server that provides real-time and historical F1 racing data via the Model Context Protocol. It supports 29 MCP tools, with free access to historical data from 2023–present (OpenF1) and 1950–present (Ergast). Live streaming requires a paid OpenF1 account.

How to use The Formula1 MCP Server ! 🏎️💨?

Clone the repository, run npm install then npm run build. No API keys or authentication are needed for historical data. Configure the server in your Claude Desktop config file (located at %APPDATA%\Claude\claude_desktop_config.json on Windows, ~/Library/Application Support/Claude/claude_desktop_config.json on MacOS, or ~/.config/Claude/claude_desktop_config.json on Linux).

Key features of The Formula1 MCP Server ! 🏎️💨

• Free historical data access with no authentication required.
• Covers sessions, drivers, weather, telemetry (2023–present via OpenF1).
• Legacy data from 1950–present via the Ergast API.
• Real-time telemetry: speed, throttle, brake, RPM, DRS, gear.
• Live streaming (MQTT) during races – requires a paid OpenF1 account.
• 29 MCP tools including session search, car data, pit stops, team radio, and race control.

Use cases of The Formula1 MCP Server ! 🏎️💨

• Inquire about current race positions and live car telemetry during a Grand Prix.
• Retrieve historical race results, driver standings, and constructor standings for any season.
• Analyze lap times, sector analysis, and pit stop strategies for past sessions.
• Access weather conditions, circuit information, and team radio recordings.
• Find session keys for historical events and then query detailed data like car telemetry or race control messages.

FAQ from The Formula1 MCP Server ! 🏎️💨

What data is available for free?

All historical data is free: sessions from 2023–present (OpenF1), races from 1950–present (Ergast), telemetry, lap times, positions, pit stops, team radio recordings, race control messages, weather data, and driver info. No authentication required.

Does real-time live streaming require payment?

Yes. MQTT WebSocket streaming for live updates during active F1 sessions requires a paid OpenF1 account. REST endpoints may still work for delayed data during race weekends (to be tested).

How do I find a specific historical session?

Use the getHistoricalSessions tool with optional parameters like year, circuit_short_name, country_name, or session_name. It returns a session_key needed as input for many other tools.

Are there known issues with certain features?

Yes. getCurrentSessionStatus may not work reliably because the official OpenF1 API lacks a standard session status endpoint. Monaco 2024 returns 0 sessions, and sprint races are not yet supported due to Ergast rate limits.

What will happen to historical data after 2024?

The Ergast API is scheduled to stop updates after the 2024 season. Alternative historical data sources for 2025+ will need to be considered.