io.github.darshjoshi/pitwall
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@io.github.darshjoshi/pitwallWho won the 2025 Australian GP?"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Quick Start
pip install f1pitwall
claude mcp add pitwall -- f1pitwallThen ask Claude: "Who won the 2025 Australian GP?"
Want visual plots and deep analysis?
pip install "f1pitwall[full]"
git clone https://github.com/darshjoshi/pitwall.git && cd pitwall
pip install "mcp[cli]" requests # lite
pip install -r requirements-full.txt # full
claude mcp add pitwall -- python3 $(pwd)/pitwall.pyRelated MCP server: F1 MCP Server
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 live 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
Live during races — real-time positions, gaps, weather, and race control
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 flagsQuestion | Tool Used |
"Who won the Chinese GP?" |
|
"What was Verstappen's speed on lap 25?" |
|
"Compare Hamilton vs Leclerc" |
|
"What tyres did everyone use?" |
|
"Fastest pit stop at Australia 2025?" |
|
"When was the safety car?" |
|
"Was it raining during the race?" |
|
"Top speeds at Monza 2024?" |
|
"Norris's lap times in the race" |
|
"Who won the 2005 championship?" |
|
"Plot Verstappen vs Hamilton speed trace" |
|
"Show me the gear shift map at Monaco" |
|
"Who gained the most positions?" |
|
"Overtakes in the race" |
|
"Compare Verstappen lap 5 vs lap 50" |
|
"Ferrari head-to-head in qualifying" |
|
"Deleted laps in qualifying" |
|
"Gap to leader throughout the race" |
|
Features
67 tools across two modes. Pitwall auto-detects what's installed — no config changes needed.
Lite Mode (14 tools)
pip install "mcp[cli]" requests — no heavy dependencies.
Race results, lap times, telemetry, tyre strategy, pit stops, weather, race control, speed traps, driver comparison, and historical data back to 1950. Uses F1's free static archive and the Jolpica API.
Full Mode (67 tools)
pip install -r requirements-full.txt — adds FastF1.
Everything in Lite, plus:
Category | What You Get |
Visual Plots | Speed trace comparisons, gear shift maps, multi-lap telemetry overlays |
Deep Telemetry | Brake point analysis, RPM patterns, DRS usage, throttle traces |
Advanced Strategy | Stint degradation, compound comparisons, tire age performance |
Race Intelligence | Overtake detection, gap tracking, position changes, qualifying progression |
Live Data | Real-time positions, lap times, sector times, weather during active sessions |
Lite Tools (always available)
Tool | Description |
| Available seasons (2018-present) |
| Full season calendar with dates |
| Session details and available data feeds |
| Race classification — positions, gaps, best laps, pits |
| Lap-by-lap times, filterable by driver and lap range |
| Speed, RPM, throttle, brake, gear, DRS for a specific lap |
| Compound, stint length, new/used for every driver |
| All pit stops sorted by fastest |
| Flags, penalties, safety cars, investigations |
| Air/track temp, rain, humidity, wind |
| Speed at 4 measurement points per driver |
| Head-to-head: position, pace, strategy, pit stops |
| Race results from 1950 to present |
| Driver/constructor championships from 1950+ |
FastF1 Tools (requires FastF1)
Category | Tools |
Visual Plots |
|
Telemetry Analysis |
|
Lap Analysis |
|
Strategy |
|
Race Analysis |
|
Pit Stops |
|
Driver & Team |
|
Track & Safety |
|
Speed & Position |
|
History |
|
Live Data |
|
Session |
|
Setup
Claude Code:
claude mcp add pitwall -- python3 /absolute/path/to/pitwall.pyClaude Desktop — add to ~/Library/Application Support/Claude/claude_desktop_config.json:
{
"mcpServers": {
"pitwall": {
"command": "python3",
"args": ["/absolute/path/to/pitwall.py"]
}
}
}1. Find your Python path:
where pythonThis will return something like C:\Users\YourName\AppData\Local\Programs\Python\Python313\python.exe or C:\Python313\python.exe.
2. Note where you cloned Pitwall:
For example: C:\Users\YourName\Projects\pitwall\pitwall.py
Claude Code (PowerShell):
claude mcp add pitwall -- python C:\Users\YourName\Projects\pitwall\pitwall.pyClaude Desktop — add to %APPDATA%\Claude\claude_desktop_config.json:
To open this folder, press
Win + R, type%APPDATA%\Claude, and hit Enter. If theClaudefolder orclaude_desktop_config.jsondoesn't exist, create them.
{
"mcpServers": {
"pitwall": {
"command": "python",
"args": ["C:\\Users\\YourName\\Projects\\pitwall\\pitwall.py"]
}
}
}Note: Use double backslashes (
\\) in the JSON path, or forward slashes (/) — both work. The command ispython(notpython3) on Windows.
Claude Code:
claude mcp add pitwall -- python3 /absolute/path/to/pitwall.pyClaude Desktop — add to ~/.config/Claude/claude_desktop_config.json:
{
"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.
Source | Coverage | What it provides |
2018-present | Telemetry, timing, strategy, pit stops, weather, race control | |
1950-present | Historical results and championships | |
FastF1 (optional) | 2018-present | Enhanced telemetry analysis and visual plots |
F1 SignalR Core (optional) | Live only | Real-time race data during active sessions |
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 3000Live 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.
Data | Free | F1 TV |
Race positions, gaps, lap times | Yes | Yes |
Race control, flags, penalties | Yes | Yes |
Weather, track status | Yes | Yes |
Tyre compounds, stint info | Yes | Yes |
Team radio URLs | Yes | Yes |
Car telemetry (speed, RPM, throttle, brake) | No | Yes |
GPS positions (X/Y/Z coordinates) | No | Yes |
All data (including telemetry and GPS) becomes free in the static archive ~30 minutes after a session ends.
python3 auth_setup.pyThis opens a browser for F1 TV login. The token is saved locally:
<project_dir>/.f1token~/Library/Application Support/fastf1/f1auth.json(macOS)
Token expires every ~4 days. Re-run to refresh. Never uploaded anywhere.
import asyncio
from 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())For full telemetry (speed, RPM, throttle, brake, GPS):
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 PrixDriver Codes
VER = Verstappen HAM = Hamilton NOR = Norris LEC = Leclerc
ANT = Antonelli RUS = Russell PIA = Piastri BEA = Bearman
GAS = Gasly LAW = Lawson HAD = Hadjar SAI = Sainz
ALO = Alonso STR = Stroll OCO = Ocon BOT = Bottas
ALB = Albon HUL = Hulkenberg COL = Colapinto LIN = LindbladProject Files
File | Purpose |
| MCP server — 67 tools, auto-degrades to 14 without FastF1 |
| Raw SignalR Core WebSocket client for live race data |
| Zlib decompression for CarData.z / Position.z |
| Keyframe + delta state management for F1's incremental format |
| All 20 SignalR topics with auth/compression metadata |
| F1 TV token setup — browser-based OAuth flow |
Contributing
Found a bug? Want to add a tool? Contributions are welcome.
Fork the repo
Create a feature branch
Make your changes
Run the test suite:
python3 tests/pitwall_tool_validation.pyOpen 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
License
MIT
This server cannot be installed
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Latest Blog Posts
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/darshjoshi/pitwall'
If you have feedback or need assistance with the MCP directory API, please join our Discord server