Pitwall — F1 Data for Claude

Pitwall

Turn Claude into your F1 race engineer.
Real telemetry. Real strategy data. 75 years of history.

[PyPI] [Downloads] [License: MIT] [Python 3.10+] [MCP Compatible] [GitHub Stars]

[Verstappen vs Norris — Abu Dhabi 2024 Qualifying Speed Trace]

Quick Start

Claude Code — one command, all 79 tools:

claude mcp add pitwall -- uvx --from "f1pitwall[full]" f1pitwall

Then ask Claude: "Who won the 2025 Australian GP?"

Needs uv (curl -LsSf https://astral.sh/uv/install.sh | sh). No pip, no virtualenv, no "which python3" — and you always get the latest release.

First launch downloads the FastF1 stack (~540 MB) and takes about 25 seconds. Every launch after that is under a second. If the very first start times out, just restart Claude Code — the download is already cached.

Want the plugin instead, so you get the f1 skill along with the server? See Install as a Claude Code plugin.

claude mcp add pitwall -- uvx --from f1pitwall f1pitwall

pip install "f1pitwall[full]"        # or just f1pitwall for liteclaude mcp add pitwall -- f1pitwall

git clone https://github.com/darshjoshi/pitwall.git && cd pitwallpip install -r requirements.txt        # lite (incl. live timing)pip install -r requirements-full.txt   # fullclaude mcp add pitwall -- python3 $(pwd)/pitwall.py

Install as a Claude Code plugin

The plugin ships the MCP server and the f1 skill together — the skill teaches Claude which of the 79 tools to reach for and how to explain F1 to someone who's never watched a race.

/plugin marketplace add darshjoshi/pitwall/plugin install pitwall@pitwall

Claude Desktop

Add to claude_desktop_config.json (Settings → Developer → Edit Config):

{  "mcpServers": {    "pitwall": {      "command": "uvx",      "args": ["--from", "f1pitwall[full]", "f1pitwall"]    }  }}

Why Pitwall?

Claude knows F1 from training data — but it can't look up last week's race. It can't show you Verstappen's throttle trace through Turn 1. It doesn't know who pitted first or when the safety car came out.

Pitwall connects Claude to real F1 data:

• Real data, not hallucinations — actual timing feeds from formula1.com
• Lap-level telemetry — speed, RPM, throttle, brake, gear, DRS at 4Hz per car
• Visual plots — speed trace comparisons, gear shift maps returned as images
• 75 years of history — every race result and championship since 1950
• Fresh after every session — full telemetry and timing published ~30 min after each session ends, back to 2018
• Zero API keys — all core data is free, no account needed

What You Can Ask

"Who won the 2025 Australian GP?"           → Race results and classification"Verstappen's speed on lap 25 at Monaco"    → Lap telemetry at 4Hz"Plot Hamilton vs Norris speed trace"       → Visual speed comparison chart"Compare Ferrari's tyre strategy"           → Stint-by-stint breakdown"Who won the 1994 championship?"            → 75 years of history"When was the safety car at Silverstone?"   → Race control messages and flags

Features

79 tools across two modes. Pitwall auto-detects what's installed — no config changes needed.

Lite Mode (30 tools)

pip install f1pitwall — light deps only (mcp, requests, plus websockets/aiohttp for live timing); no pandas/numpy/FastF1.

Race results, lap times, telemetry, tyre strategy, pit stops, weather, race control, speed traps, driver comparison, and historical data back to 1950. Plus 16 live-timing tools (running order, gaps, lap/sector times, tyres, weather, race control, speed traps, mini-sectors, …) that read F1's real-time SignalR feed during a session — no auth needed. (Live car telemetry + GPS are auth-gated and live in Full mode.) Uses F1's free static archive and the Jolpica API.

Full Mode (79 tools)

pip install -r requirements-full.txt — adds FastF1.

Everything in Lite, plus:

Setup

claude mcp add pitwall -- python3 /absolute/path/to/pitwall.py

{  "mcpServers": {    "pitwall": {      "command": "python3",      "args": ["/absolute/path/to/pitwall.py"]    }  }}

where python

claude mcp add pitwall -- python C:\Users\YourName\Projects\pitwall\pitwall.py

{  "mcpServers": {    "pitwall": {      "command": "python",      "args": ["C:\\Users\\YourName\\Projects\\pitwall\\pitwall.py"]    }  }}

claude mcp add pitwall -- python3 /absolute/path/to/pitwall.py

{  "mcpServers": {    "pitwall": {      "command": "python3",      "args": ["/absolute/path/to/pitwall.py"]    }  }}

Restart Claude Code or Claude Desktop after setup. Works with any MCP-compatible client.

Optional: Beginner-Friendly Skill (Claude Desktop)

Upload SKILL.md as a skill in Claude Desktop (Settings → Skills → Upload). Claude will explain F1 jargon inline — DRS, undercut, compound, safety car, etc.

Data Sources

All core data is free and requires no API keys.

How It Works

Pitwall reads from F1's publicly available static timing archive — the same data that powers the official F1 app. After each session ends (~30 minutes), F1 publishes 33 data feeds per session including full car telemetry (speed, RPM, throttle, brake, gear, DRS at ~4Hz per car), GPS positions, tyre data, pit stops, and race control messages.

The telemetry tool (get_telemetry) correlates the timing stream with the car data stream to extract telemetry for a specific driver on a specific lap — something no other F1 MCP server does.

Architecture

Claude ──MCP──> Pitwall ──HTTP──> livetiming.formula1.com/static/ (free)                       ──HTTP──> api.jolpi.ca/ergast/f1/ (free)                       ──lib──>  FastF1 (optional, local)                       ──WS───> SignalR Core (optional, live races)

Running the Server

python3 pitwall.py              # MCP stdio (Claude Code / Claude Desktop)python3 pitwall.py --http       # MCP HTTP (remote / self-hosted)python3 pitwall.py --http --port 3000

Live Race Data

Pitwall includes a raw SignalR Core WebSocket client for real-time data during active F1 sessions. Most data is free — car telemetry and GPS require an F1 TV Pro or Premium subscription.

Note: The get_live_* MCP tools read this client's live SignalR feed directly. 16 timing tools (running order, gaps, lap/sector times, tyres, weather, race control, speed traps, mini-sectors, …) work in the lite install with no auth; live car telemetry and GPS (get_live_telemetry, get_live_gps_positions) need an F1 TV token and ship in the full install. Post-session data — telemetry, timing, strategy — also remains available through the main tools after each session ends.

python3 auth_setup.py

import asynciofrom signalr_client import F1LiveClient
async def main():    # Free mode — timing, weather, race control (no auth needed)    client = F1LiveClient(no_auth=True)
    @client.on("TimingData")    def on_timing(data, timestamp):        for num, info in data.get("Lines", {}).items():            print(f"P{info.get('Position','?')} #{num} Gap: {info.get('GapToLeader','')}")
    @client.on("RaceControlMessages")    def on_rc(data, timestamp):        for msg in data.get("Messages", {}).values():            print(f"[{msg.get('Flag', '')}] {msg.get('Message', '')}")
    await client.connect()
asyncio.run(main())

from auth_setup import load_token
client = F1LiveClient(no_auth=False, auth_token=load_token())
@client.on("CarData.z")def on_telemetry(data, timestamp):    # Speed, RPM, throttle, brake, gear, DRS at ~4Hz per car    ...
@client.on("Position.z")def on_position(data, timestamp):    # GPS X/Y/Z coordinates at ~4Hz per car    ...

Reference

Race Names

Race names are fuzzy-matched. All of these work:

"china", "chinese", "shanghai"           → Chinese Grand Prix"australia", "melbourne", "aus"          → Australian Grand Prix"monaco", "monte carlo"                  → Monaco Grand Prix"silverstone", "great britain", "british" → British Grand Prix

Driver Codes

VER = Verstappen    HAM = Hamilton    NOR = Norris     LEC = LeclercANT = Antonelli     RUS = Russell     PIA = Piastri    BEA = BearmanGAS = Gasly         LAW = Lawson      HAD = Hadjar     SAI = SainzALO = Alonso        STR = Stroll      OCO = Ocon       BOT = BottasALB = Albon         HUL = Hulkenberg  COL = Colapinto  LIN = Lindblad

Project Files

Contributing

Found a bug? Want to add a tool? Contributions are welcome.

1. Fork the repo
2. Create a feature branch
3. Make your changes
4. Run the test suite: python3 tests/pitwall_tool_validation.py
5. Open a pull request

Credits

• FastF1 by @theOehrly — the gold standard F1 Python library
• Jolpica-F1 — the Ergast API successor
• drivenrajat/f1 — inspiration for FastF1 tool patterns

Built by

Darsh Joshi — AI Engineer

[LinkedIn] [GitHub] [Email]

License

MIT