Pitwall
UnclaimedTurn Claude into your F1 race engineer — 79 MCP tools for telemetry, strategy, and 75 years of race history
Set up this server
01 / Choose your client
02 / Before you connect
Authentication is not specified. Check the project instructions before connecting.
Project instructions03 / Add the configuration
claude mcp add --transport stdio 'pitwall' -- 'uvx' '--from' 'f1pitwall[full]' 'f1pitwall'04 / Check it in your client
Open your client’s MCP settings and confirm the server connects and lists its tools. A copied configuration does not confirm a working connection.
More in Developer Tools
Browse the full directoryUnclaimed listing
Is this your MCP server?
This listing was auto-indexed from the public record. Claim it to edit the page, set compatibility and unlock growth tools. Takes under two minutes.
Claim this serverSecurity profile
Claimed and verified servers get a weekly static scan that shows what the code can reach: external services, environment variables, shell commands, agent configuration folders, plus any dependencies with known advisories. Claim this listing to get one. How the security profile works
30 of 30 tools
Documented tools (30)
From project documentation. A server handshake does not verify each tool’s description or behavior.
get_championship_standings
Driver/constructor championships from 1950+
get_driver_comparison
Head-to-head: position, pace, strategy, pit stops
get_historical_results
Race results from 1950 to present
get_lap_times
Lap-by-lap times, filterable by driver and lap range
get_live_best_sectors
Personal-best sectors + best lap, ranked
get_live_lap_times
Last + best lap per driver
get_live_mini_sectors
Mini-sector status (green/purple/yellow) per driver
get_live_pit_activity
Pit count + in-pit / out-lap flags
get_live_positions
Live running order with gap + interval
get_live_race_control
Flags, penalties, track-limit deletions, SC/VSC
get_live_sector_times
Sector times + speed trap for one driver
get_live_session_clock
Time remaining in the session
get_live_session_status
Session name, flag/track status, lap count
get_live_speed_comparison
Best speed at I1/I2/FL/ST per driver
get_live_speed_trap
Speed-trap (ST) ranking across the field
get_live_stint_history
Full compound sequence per driver
get_live_time_gaps
Gap to leader + interval to car ahead (mode-aware)
get_live_track_status_history
Chronological track/session status log
get_live_tyres
Compound, age (laps), stint number per driver
get_live_weather
Air/track temp, humidity, wind, rain
get_pit_stops
All pit stops sorted by fastest
get_race_control
Flags, penalties, safety cars, investigations
get_race_info
Session details and available data feeds
get_speed_traps
Speed at 4 measurement points per driver
get_standings
Race classification — positions, gaps, best laps, pits
get_telemetry
Speed, RPM, throttle, brake, gear, DRS for a specific lap
get_tyre_strategy
Compound, stint length, new/used for every driver
get_weather
Air/track temp, rain, humidity, wind
list_races
Full season calendar with dates
list_seasons
Available seasons (2018-present)
Tool change history
FAQ
Questions about Pitwall MCP Server
- How do I connect Pitwall MCP Server to Claude?
- Run `claude mcp add pitwall -- uvx --from f1pitwall[full] f1pitwall` in Claude Code, or add the same command and arguments under mcpServers in Cursor's mcp.json or Claude Desktop's claude_desktop_config.json, then restart the client. The blocks above are ready to paste.
- Is Pitwall MCP Server free?
- The listed licence is MIT. Check the upstream terms for permitted use and commercial requirements; a public repository does not by itself mean the software is free or open source. Connected APIs and hosted services may have separate charges.
- What can Pitwall MCP Server do?
- Pitwall MCP Server documents 30 tools to the agent, including get_championship_standings, get_driver_comparison, get_historical_results. The descriptions above come from project documentation. A live handshake does not test individual tool behavior.