Pitwall MCP server
✓ VerifiedMemberikan Claude akses ke telemetri F1 real-time, data strategi balapan, dan statistik balap historis selama 75 tahun.
Juga dikenal sebagai darshjoshi/pitwall, pitwall, f1pitwall
- Stars
- 9
- Tools
- 14
- Unduhan, 30 hari
- 148
- Versi terbaru
- 1.1.1
- Commit terakhir
- 2 Agu 2026
- Lisensi
- MIT
Apa itu Pitwall MCP?
Pitwall adalah MCP server. Memberikan Claude akses ke telemetri F1 real-time, data strategi balapan, dan statistik balap historis selama 75 tahun. Server ini menyediakan 14 tool, seperti list_seasons, list_races, get_race_info.
Ringkasan dibuat dari README proyek
Tentang Pitwall MCP server
Pitwall memungkinkan Anda mengubah Claude menjadi virtual race engineer bagi para penggemar dan analis Formula 1. MCP server ini menyediakan akses ke telemetri real-time, data strategi balapan, dan arsip historis masif yang mencakup statistik balap selama 75 tahun. Pengguna dapat berinteraksi dengan server melalui Claude Desktop atau Claude Code, menggunakan Lite mode dengan 30 tools atau Full mode dengan 79 tools yang mencakup visual plotting tingkat lanjut dan analisis telemetri mendalam.
Setup sangat mudah menggunakan uvx atau pip, dan tidak memerlukan API keys atau akun untuk akses data inti. Lite mode menawarkan 16 tools live-timing yang membaca feed real-time selama sesi berlangsung, sementara Full mode mengintegrasikan stack FastF1 untuk menyediakan perbandingan visual speed trace, gear shift maps, dan analisis brake point yang mendetail. Baik Anda perlu membandingkan degradasi ban atau memeriksa klasemen kejuaraan dari tahun 1950, Pitwall menyajikan data presisi alih-alih halusinasi model.
Apa yang bisa Anda lakukan dengannya
- 1Analyze driver telemetryMinta perbandingan visual speed traces antara dua driver spesifik selama satu lap balapan.
- 2Evaluate race strategyMinta rincian mendalam tentang bagaimana berbagai tim mengelola tire compounds dan stint mereka.
- 3Retrieve historical racing dataTanyakan mengenai pemenang kejuaraan atau hasil balapan dari beberapa dekade lalu.
- 4Monitor live session updatesDapatkan informasi real-time mengenai status track, safety cars, atau urutan posisi saat ini selama event berlangsung.
Ditulis berdasarkan README proyek. Setiap use case diperiksa terhadap kutipan dari README tersebut.
Cara menginstal Pitwall MCP
Format diverifikasi 10 Nov 2026Tambahkan ke CursorTambahkan ke GooseInstal Pitwall MCP di Claude Code
$ claude mcp add pitwall -- uvx f1pitwallInstal Pitwall MCP di Cursor
~/.cursor/mcp.json
{
"mcpServers": {
"pitwall": {
"command": "uvx",
"args": [
"f1pitwall"
]
}
}
}Instal Pitwall MCP di VS Code
.vscode/mcp.json
{
"servers": {
"pitwall": {
"type": "stdio",
"command": "uvx",
"args": [
"f1pitwall"
]
}
}
}Instal Pitwall MCP di VS Code CLI
$ code --add-mcp '{"name":"pitwall","type":"stdio","command":"uvx","args":["f1pitwall"]}'Instal Pitwall MCP di Claude Desktop
claude_desktop_config.json
{
"mcpServers": {
"pitwall": {
"command": "uvx",
"args": [
"f1pitwall"
]
}
}
}Instal Pitwall MCP di Codex
$ codex mcp add pitwall -- uvx f1pitwallInstal Pitwall MCP di Codex config.toml
~/.codex/config.toml
[mcp_servers.pitwall] command = "uvx" args = ["f1pitwall"]
Instal Pitwall MCP di Gemini CLI
$ gemini mcp add -s user pitwall uvx -- f1pitwallInstal Pitwall MCP di Gemini settings.json
~/.gemini/settings.json
{
"mcpServers": {
"pitwall": {
"command": "uvx",
"args": [
"f1pitwall"
]
}
}
}Tool Pitwall MCP 14
Terdeteksi dari READMElist_seasonslist_racesget_race_infoget_standingsget_lap_timesget_telemetryget_tyre_strategyget_pit_stopsget_race_controlget_weatherget_speed_trapsget_driver_comparison
| list_seasons | — | |
| list_races | — | |
| get_race_info | — | |
| get_standings | — | |
| get_lap_times | — | |
| get_telemetry | — | |
| get_tyre_strategy | — | |
| get_pit_stops | — | |
| get_race_control | — | |
| get_weather | — | |
| get_speed_traps | — | |
| get_driver_comparison | — |
Tampilkan semua 14 toolTampilkan lebih sedikit tool
get_historical_resultsget_championship_standings
| get_historical_results | — | |
| get_championship_standings | — |
Pengecekan otomatis
Berjalan 14 Nov 2026Laporan lengkap →Lolos checks otomatis kami. Ini bukan audit keamanan: baca kodenya dan berikan server akses paling terbatas yang dibutuhkannya. Cara kerja checks
- Source repository terhubung dan dapat dijangkaudarshjoshi/pitwall is public and reachablegithub.com/darshjoshi/pitwall ↗Lolos
- Nama paket mencantumkan repositori ini sebagai sumbernyaf1pitwall names darshjoshi/pitwall as sourcepypi.org/project/f1pitwall/ ↗Lolos
- Provenance build (atestasi Sigstore)Sigstore attestation for f1pitwallpypi.org/project/f1pitwall/ ↗Lolos
- Lisensi open source (OSI)MITspdx.org/licenses/MIT.html ↗Lolos
- Ada commit atau release dalam satu tahun terakhirLast commit or release 2026-08-02github.com/darshjoshi/pitwall ↗Lolos
- OpenSSF ScorecardTidak diperiksa
- Nama package tidak mirip dengan package populerNo popular package one edit away from f1pitwallLolos
- Tidak ada advisory kritis pada paket atau dependensinya41 resolved dependencies checked; no critical advisoryosv.dev ↗Lolos
- Tidak ada instruksi tersembunyi untuk model14 tool descriptions and the README read; no override phrases, credential paths or hidden charactersLolos
- Tools yang bersifat destruktif telah diberi labelNo tool named like delete, drop or execLolos
- Endpoint remote merespons handshake MCPTidak diperiksa
README
Lihat di GitHubQuick 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.
Skips pandas/numpy/matplotlib/FastF1. Still includes all 16 live-timing tools.
claude mcp add pitwall -- uvx --from f1pitwall f1pitwall
pip install "f1pitwall[full]" # or just f1pitwall for lite
claude mcp add pitwall -- f1pitwall
git clone https://github.com/darshjoshi/pitwall.git && cd pitwall
pip install -r requirements.txt # lite (incl. live timing)
pip install -r requirements-full.txt # full
claude 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
| Question | Tool Used |
|---|---|
| "Who won the Chinese GP?" | get_standings |
| "What was Verstappen's speed on lap 25?" | get_telemetry |
| "Compare Hamilton vs Leclerc" | get_driver_comparison |
| "What tyres did everyone use?" | get_tyre_strategy |
| "Fastest pit stop at Australia 2025?" | get_pit_stops |
| "When was the safety car?" | get_race_control |
| "Was it raining during the race?" | get_weather |
| "Top speeds at Monza 2024?" | get_speed_traps |
| "Norris's lap times in the race" | get_lap_times |
| "Who won the 2005 championship?" | get_championship_standings |
| "Plot Verstappen vs Hamilton speed trace" | plot_telemetry_comparison |
| "Show me the gear shift map at Monaco" | plot_gear_shifts |
| "Who gained the most positions?" | compare_grid_to_finish |
| "Overtakes in the race" | detect_overtakes |
| "Compare Verstappen lap 5 vs lap 50" | plot_multi_telemetry_comparison |
| "Ferrari head-to-head in qualifying" | team_head_to_head |
| "Deleted laps in qualifying" | get_deleted_laps |
| "Gap to leader throughout the race" | get_gap_to_leader |
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:
| 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 |
Lite Tools (always available)
| Tool | Description |
|---|---|
list_seasons |
Available seasons (2018-present) |
list_races |
Full season calendar with dates |
get_race_info |
Session details and available data feeds |
get_standings |
Race classification — positions, gaps, best laps, pits |
get_lap_times |
Lap-by-lap times, filterable by driver and lap range |
get_telemetry |
Speed, RPM, throttle, brake, gear, DRS for a specific lap |
get_tyre_strategy |
Compound, stint length, new/used for every driver |
get_pit_stops |
All pit stops sorted by fastest |
get_race_control |
Flags, penalties, safety cars, investigations |
get_weather |
Air/track temp, rain, humidity, wind |
get_speed_traps |
Speed at 4 measurement points per driver |
get_driver_comparison |
Head-to-head: position, pace, strategy, pit stops |
get_historical_results |
Race results from 1950 to present |
get_championship_standings |
Driver/constructor championships from 1950+ |
Live Timing (lite — no auth, reads F1's real-time SignalR feed during a session)
| Tool | Description |
|---|---|
get_live_session_status |
Session name, flag/track status, lap count |
get_live_positions |
Live running order with gap + interval |
get_live_lap_times |
Last + best lap per driver |
get_live_sector_times |
Sector times + speed trap for one driver |
get_live_time_gaps |
Gap to leader + interval to car ahead (mode-aware) |
get_live_best_sectors |
Personal-best sectors + best lap, ranked |
get_live_speed_trap |
Speed-trap (ST) ranking across the field |
get_live_speed_comparison |
Best speed at I1/I2/FL/ST per driver |
get_live_tyres |
Compound, age (laps), stint number per driver |
get_live_stint_history |
Full compound sequence per driver |
get_live_pit_activity |
Pit count + in-pit / out-lap flags |
get_live_weather |
Air/track temp, humidity, wind, rain |
get_live_race_control |
Flags, penalties, track-limit deletions, SC/VSC |
get_live_session_clock |
Time remaining in the session |
get_live_track_status_history |
Chronological track/session status log |
get_live_mini_sectors |
Mini-sector status (green/purple/yellow) per driver |
FastF1 Tools (requires FastF1)
| Category | Tools |
|---|---|
| Visual Plots | plot_telemetry_comparison, plot_gear_shifts, plot_multi_telemetry_comparison, plot_driver_telemetry_comparison |
| Telemetry Analysis | analyze_brake_points, analyze_rpm_data, analyze_drs_usage |
| Lap Analysis | get_lap_times_fastf1, get_deleted_laps, analyze_lap_consistency, get_fastest_sectors, get_personal_best_laps, compare_sector_times |
| Strategy | get_driver_tyre_detail, get_stint_analysis, compare_tire_compounds, compare_tire_age_performance, analyze_starting_tires, compare_strategies |
| Race Analysis | get_race_results, get_sprint_results, get_session_summary, get_fastest_lap_data, detect_overtakes, compare_grid_to_finish, get_qualifying_progression |
| Pit Stops | get_pit_stop_detail, get_fastest_pit_stops |
| Driver & Team | get_driver_info, get_driver_standings, get_constructor_standings, team_head_to_head, get_team_laps, analyze_long_run_pace |
| Track & Safety | get_circuit_info, get_track_status, get_track_record, get_race_control_messages, get_penalties, get_dnf_list |
| Speed & Position | get_speed_trap_comparison, get_position_changes, get_gap_to_leader |
| History | get_race_winners_history |
| Live (auth-gated) | get_live_telemetry, get_live_gps_positions — live car telemetry + GPS, need an F1 TV token |
| Session | get_schedule, get_session_info, get_weather_data |
Setup
Claude Code:
claude mcp add pitwall -- python3 /absolute/path/to/pitwall.py
Claude 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 python
This 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.py
Claude 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.py
Claude 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 |
|---|---|---|
| F1 Static Live Timing | 2018-present | Telemetry, timing, strategy, pit stops, weather, race control |
| Jolpica-F1 | 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 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.
| 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.py
This 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 Prix
Driver 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 = Lindblad
Project Files
| File | Purpose |
|---|---|
pitwall.py |
MCP server — 79 tools, auto-degrades to 30 without FastF1 |
signalr_client.py |
Raw SignalR Core WebSocket client for live race data |
decompressor.py |
Zlib decompression for CarData.z / Position.z |
merger.py |
Keyframe + delta state management for F1's incremental format |
topics.py |
All 20 SignalR topics with auth/compression metadata |
auth_setup.py |
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.py - 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
License
MIT
Pertanyaan tentang Pitwall MCP
Bagaimana cara menambahkan Pitwall MCP ke Claude Code?
Jalankan claude mcp add pitwall -- uvx f1pitwall di terminal Anda. Tambahkan --scope user agar tersedia di semua proyek.
Bagaimana cara menambahkan Pitwall MCP ke Cursor?
Buka ~/.cursor/mcp.json dan tambahkan server di bawah mcpServers, menggunakan config Cursor yang ditunjukkan di bagian instalasi di atas.
Tool apa yang disediakan Pitwall MCP?
Server ini menyediakan 14 tool, termasuk list_seasons, list_races, get_race_info, get_standings, get_lap_times.
Apakah Pitwall memerlukan API key?
Tidak, semua data inti tersedia secara gratis dan tidak memerlukan akun untuk penggunaan tool standar.
Jenis data telemetri apa yang bisa saya dapatkan?
Anda dapat mengakses telemetri tingkat lap termasuk speed, RPM, throttle, brake, gear, dan DRS dengan frekuensi 4Hz per mobil.
Seberapa banyak data historis yang tersedia?
MCP server ini menyediakan akses ke setiap hasil balapan dan kejuaraan sejak tahun 1950.
Apa perbedaan antara mode Lite dan Full?
Lite mode mencakup 30 tools dan live timing tanpa dependency yang berat, sedangkan Full mode mencakup 79 tools dengan visual plots dan analisis telemetri mendalam menggunakan FastF1.