get_sessionsLABSCO SUMMARY
Race questions answered from the timing data, not from recollection.
Ask a model who had the fastest pit stop in Singapore and you get a memory; this returns the row, with the lap number and the duration attached. Start every question by resolving the session — year, circuit, session name — because that key is what the lap, pit and overtake calls hang off.
What it is
A single-file Python server over OpenF1, the open API for real-time and historical Formula 1 data. Everything keys off a session: find the one you mean by year, country, circuit or session name, then read the drivers who took part, the lap and sector times, the pit stops and the overtakes. The upstream API is public and unauthenticated, so there is no key to obtain and nothing of yours to hand over.
What you get
- Sessions filtered by year, country, circuit, session name or type, and by start date with
>=and<=comparisons - The drivers in a session — name, number, team, country and headshot — or the current field, filtered by team or number
- Lap data for a session, a driver or a single lap, with lap time, sector times, duration and position
- Pit stops with duration and lap number, narrowed to stops under a duration you set
- Overtakes as position changes: who passed whom, on which lap, and when in the session
Requirements
Python with the mcp and httpx packages, and the server file itself — it is one script, launched by its path. Answers come from openf1.org at request time, so it needs network access, but no account and no key. The parameter set is documented as of v1.2; the lap, pit-stop and overtake calls only return anything meaningful with a session_key, which is what the session lookup produces.
Setup effort
Build from source — git clone https://github.com/AryaAkman/Open-F1-MCP-Server.git
USE CASES
01
Settling an argument about a race
Resolve the session from the year and circuit, then read the lap times and pit stops that decide it.
02
Comparing two drivers over a stint
Find who was in the session and read their lap and sector times side by side for the laps you care about.
03
Looking at how the stops played out
Pull every pit stop in the session with its lap and duration, narrowed to the ones under a threshold you set.
04
Reconstructing where positions changed
Read the overtakes as pairs — who passed whom, on which lap — filtered to one driver on either side of the move.
05
Finding out who was on track that weekend
Look up the session by country or circuit and get the entry list with numbers, teams and countries.
5 tools
Listed in project docs. Your client may show a different list.
get_driversget_lapsget_pit_stopsget_overtakesBEFORE YOU INSTALL
What to know first
Tools you get
5 tools named in the project's documentation.
Where it runs
The documented client runs the server on your machine.
INSTALLATION
Connect your client
You clone this one yourself.
Server setup
TERMINAL
git clone https://github.com/AryaAkman/Open-F1-MCP-Server.git
pip install mcp httpxMCP Clients
Claude Desktop
CLAUDE DESKTOP · JSON
{
"mcpServers": {
"Open-F1": {
"command": "python",
"args": [
"<YOUR_PATH_TO_OPEN_F1_MCP_SERVER>/OpenF1MCPServer.py"
]
}
}
}
