F1 MCP Server
This server does not currently have a deployable release on Glama. Follow the repository's setup instructions to install and configure it for your MCP client, including any required credentials and local dependencies.
ποΈ F1 MCP Server
A real-time Formula 1 analytics server built with the Model Context Protocol (MCP). Ask Claude natural language questions about F1 races, lap times, tyre strategies, pit stops, and more β powered by live data from the OpenF1 API.
"What tyre strategy did the top 3 drivers use in the 2026 Monaco Race?" "Who set the fastest lap at the 2026 Australian GP?" "Was there a safety car at the 2024 British GP?"
ποΈ Architecture

Related MCP server: f1-mcp
βοΈ How It Works
Claude Desktop acts as the MCP client. On startup, it boots the F1 MCP server as a local subprocess and communicates via stdio (standard input/output). When you ask a natural language question, Claude reads the tool definitions and docstrings, decides which tools to call (and in what order), fires the OpenF1 API requests, and synthesizes the response β all automatically.
No API key required. No authentication. Just live F1 data.
π οΈ Tools
Tool | Description |
| Find all sessions for a year/country (Race, Qualifying, Practice, Sprint) |
| List all drivers in a session with number, name, and team |
| All lap times and sector times for a specific driver |
| Fastest lap across all drivers in a session |
| Pit stop laps and durations for a session |
| Full tyre strategy β compound, stint number, lap range |
| Final finishing positions for all drivers |
| Track temp, air temp, humidity, wind, and rainfall |
| Safety cars, flags, penalties, and incidents |
π¬ Example Queries
What sessions are available for the 2026 season?
Who set the fastest lap in the 2026 Australian GP?
What tyre strategy did the top 3 use in the 2026 Monaco Race?
Did it rain during the 2024 British GP qualifying?
Were there any safety cars in the 2024 Monaco Race?
What were Hamilton's lap times in the 2026 Monaco Race?
How long were Verstappen's pit stops in the 2024 Abu Dhabi GP?πΈ Screenshots
Sessions Query

Fastest Lap β Auto Tool Chaining

Tyre Strategy β Multi-Tool Chain

π Setup
Prerequisites
Python 3.10+
uv package manager
Installation
# Clone the repo
git clone https://github.com/kevinjohnson/F1-MCP-Server.git
cd F1-MCP-Server
# Install dependencies
uv add "mcp[cli]" requests
# Register with Claude Desktop
uv run mcp install main.pyThen fully quit and reopen Claude Desktop. The F1 Assistant will appear under Connectors.
Common Issue
If the server shows as "Server not found", make sure main.py ends with:
if __name__ == "__main__":
mcp.run() # No transport argument β stdio onlyπ‘ Data Source
All data comes from OpenF1 β a free, open-source API providing real-time and historical F1 telemetry from 2023 onwards.
No API key required for historical data
Rate limit: 3 req/s, 30 req/min (free tier)
Data available from 2023 season onwards
π§ Why MCP?
Claude can't access live data or external APIs on its own. MCP (Model Context Protocol) bridges that gap β it lets you define tools as Python functions that Claude can call autonomously. The key insight: Claude reads your docstrings to decide when and how to use each tool, enabling it to chain multiple API calls together without any explicit instructions.
In this project, a single question like "What tyre strategy did the top 3 use?" triggers Claude to automatically: find the session key β get race positions β resolve driver numbers β fetch tyre stints for each driver β all from one natural language prompt.
π Project Structure
F1-MCP-Server/
βββ main.py # MCP server with all 9 tools
βββ pyproject.toml # uv project config
βββ images/ # Screenshots and architecture diagram
βββ README.mdπ Potential Extensions
Add
get_car_telemetryβ throttle, brake, DRS, gear data per lapAdd
get_overtakesβ position change events during a raceAdd
get_championship_standingsβ driver and constructor standingsCache session keys locally to reduce API calls
Add a
compare_driverstool for head-to-head lap time analysis
Built by Kevin Johnson Β· Powered by OpenF1 Β· Built with MCP
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelogβ¦
This server cannot be deployed
Maintenance
Related MCP Connectors
Anonymous read-only Formula 1 tools, resources, prompts, completion, and interactive dashboard.
AI race engineer for sim racing (Automobilista 2, Assetto Corsa, Assetto Corsa Competizione, Assetto Corsa Evo, RaceRoom). Provides telemetry analysis, braking diagnostics, and leaderboards. Connected via public demo by default. Get your free personal token at [https://flowix.com](https://flowix.com) to analyze your own laps.
Read-only F1 game laps, telemetry, setups, leaderboard benchmarks, and progress.
Related MCP Servers
- AlicenseAqualityDmaintenanceA Model Context Protocol server that provides comprehensive Formula One racing data, enabling access to event schedules, driver information, telemetry data, race results, and performance analytics through natural language queries.81MIT
- AlicenseNot gradedqualityDmaintenanceAn MCP server that provides 118+ Formula 1 analytics tools, enabling race analysis, driver comparisons, telemetry exploration, and strategy simulation through natural language.26 PyPIMIT
- AlicenseNot gradedqualityDmaintenanceEnables Formula 1 data analysis through natural language, providing tools like track dominance, lap time analysis, and team performance comparisons.Apache 2.0
- AlicenseAqualityDmaintenanceA local MCP server that gives Claude (or any MCP-compatible AI client) access to Formula 1 race data. Load any session from 2018 onwards, ask questions in natural language, and get answers backed by real telemetry, timing, and strategy data.171MIT