Serveur MCP Pitwall
✓ VérifiéFournit à Claude la télémétrie F1 en temps réel, les données de stratégie de course et 75 ans de statistiques historiques de course.
Aussi connu sous darshjoshi/pitwall, pitwall, f1pitwall
- Étoiles
- 9
- Outils
- 14
- Téléchargements, 30 jours
- 148
- Dernière version
- 1.1.1
- Dernier commit
- 2 août 2026
- Licence
- MIT
Qu'est-ce que Pitwall MCP ?
Fournit à Claude la télémétrie F1 en temps réel, les données de stratégie de course et 75 ans de statistiques historiques de course. Il expose 14 outils, comme list_seasons, list_races, get_race_info.
Résumé généré à partir du README du projet
À propos du MCP server Pitwall
Pitwall permet de transformer Claude en un ingénieur de course virtuel pour les passionnés et les analystes de Formule 1. Ce MCP server offre un accès à la télémétrie en temps réel, aux données de stratégie de course et à une archive historique massive couvrant 75 ans de statistiques de course. Les utilisateurs peuvent interagir avec le serveur via Claude Desktop ou Claude Code, en utilisant soit un mode Lite avec 30 outils, soit un mode Full avec 79 outils incluant la génération de graphiques visuels et une analyse de télémétrie approfondie.
L'installation est simple via uvx ou pip, et aucune clé API ni aucun compte n'est requis pour l'accès aux données de base. Le mode Lite propose 16 outils de chronométrage en direct qui lisent les flux en temps réel pendant les sessions, tandis que le mode Full intègre la pile FastF1 pour fournir des comparaisons visuelles de traces de vitesse, des cartes de changement de rapport et une analyse détaillée des points de freinage. Que vous ayez besoin de comparer la dégradation des pneus ou de consulter le classement du championnat depuis 1950, Pitwall fournit des données précises pour éviter les hallucinations du modèle.
Ce que vous pouvez faire avec
- 1Analyser la télémétrie des pilotesDemandez une comparaison visuelle des traces de vitesse entre deux pilotes spécifiques lors d'un tour de course.
- 2Évaluer la stratégie de courseDemandez une analyse détaillée de la manière dont les différentes écuries ont géré leurs composés de pneus et leurs stints.
- 3Récupérer des données de course historiquesInterrogez le serveur sur les vainqueurs de championnats ou les résultats de courses datant de plusieurs décennies.
- 4Surveiller les mises à jour des sessions en directObtenez des informations en temps réel sur l'état de la piste, les safety cars ou l'ordre de passage actuel lors d'un événement en direct.
Extrait du README du projet. Chaque cas d'utilisation est vérifié par rapport à une citation du document.
Comment installer Pitwall MCP
Formats vérifiés le 10 nov. 2026Ajouter à CursorAjouter à GooseInstaller Pitwall MCP dans Claude Code
$ claude mcp add pitwall -- uvx f1pitwallInstaller Pitwall MCP dans Cursor
~/.cursor/mcp.json
{
"mcpServers": {
"pitwall": {
"command": "uvx",
"args": [
"f1pitwall"
]
}
}
}Installer Pitwall MCP dans VS Code
.vscode/mcp.json
{
"servers": {
"pitwall": {
"type": "stdio",
"command": "uvx",
"args": [
"f1pitwall"
]
}
}
}Installer Pitwall MCP dans VS Code CLI
$ code --add-mcp '{"name":"pitwall","type":"stdio","command":"uvx","args":["f1pitwall"]}'Installer Pitwall MCP dans Claude Desktop
claude_desktop_config.json
{
"mcpServers": {
"pitwall": {
"command": "uvx",
"args": [
"f1pitwall"
]
}
}
}Installer Pitwall MCP dans Codex
$ codex mcp add pitwall -- uvx f1pitwallInstaller Pitwall MCP dans Codex config.toml
~/.codex/config.toml
[mcp_servers.pitwall] command = "uvx" args = ["f1pitwall"]
Installer Pitwall MCP dans Gemini CLI
$ gemini mcp add -s user pitwall uvx -- f1pitwallInstaller Pitwall MCP dans Gemini settings.json
~/.gemini/settings.json
{
"mcpServers": {
"pitwall": {
"command": "uvx",
"args": [
"f1pitwall"
]
}
}
}Outils MCP Pitwall 14
Détectés depuis le 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 | — |
Afficher les 14 outilsAfficher moins d'outils
get_historical_resultsget_championship_standings
| get_historical_results | — | |
| get_championship_standings | — |
Vérifications automatisées
Exécuté le 14 nov. 2026Rapport complet →A passé nos vérifications automatisées. Il ne s'agit pas d'un audit de sécurité : lisez le code et donnez au serveur l'accès le plus restreint dont il a besoin. Fonctionnement des vérifications
- Dépôt source lié et accessibledarshjoshi/pitwall is public and reachablegithub.com/darshjoshi/pitwall ↗Réussi
- Le nom du package correspond au dépôt sourcef1pitwall names darshjoshi/pitwall as sourcepypi.org/project/f1pitwall/ ↗Réussi
- Provenance du build (attestation Sigstore)Sigstore attestation for f1pitwallpypi.org/project/f1pitwall/ ↗Réussi
- Licence open source (OSI)MITspdx.org/licenses/MIT.html ↗Réussi
- Commit ou version publiée au cours de l'année écouléeLast commit or release 2026-08-02github.com/darshjoshi/pitwall ↗Réussi
- OpenSSF ScorecardNon vérifié
- Nom du package non proche d'un package populaireNo popular package one edit away from f1pitwallRéussi
- Aucun avis critique dans le package ou ses dépendances41 resolved dependencies checked; no critical advisoryosv.dev ↗Réussi
- Aucune instruction cachée destinée au modèle14 tool descriptions and the README read; no override phrases, credential paths or hidden charactersRéussi
- Les outils destructifs sont étiquetésNo tool named like delete, drop or execRéussi
- Le point de terminaison distant répond à la poignée de main MCPNon vérifié
README
Voir sur 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
Questions sur Pitwall MCP
Comment ajouter Pitwall MCP à Claude Code ?
Exécutez claude mcp add pitwall -- uvx f1pitwall dans votre terminal. Ajoutez --scope user pour le rendre disponible dans tous les projets.
Comment ajouter Pitwall MCP à Cursor ?
Ouvrez ~/.cursor/mcp.json et ajoutez le serveur sous mcpServers, avec la configuration Cursor indiquée dans la section d'installation ci-dessus.
Quels outils Pitwall MCP fournit-il ?
Il expose 14 outils, dont list_seasons, list_races, get_race_info, get_standings, get_lap_times.
Pitwall nécessite-t-il une clé API ?
Non, toutes les données de base sont gratuites et aucun compte n'est requis pour les outils standard.
Quel type de données de télémétrie puis-je obtenir ?
Vous pouvez accéder à la télémétrie au tour près, incluant la vitesse, le régime moteur (RPM), l'accélérateur, le frein, la vitesse engagée et le DRS à une fréquence de 4Hz par voiture.
Quelle quantité de données historiques est disponible ?
Le serveur permet d'accéder à tous les résultats de course et championnats depuis 1950.
Y a-t-il une différence entre les modes Lite et Full ?
Le mode Lite comprend 30 outils et le chronométrage en direct sans dépendances lourdes, tandis que le mode Full comprend 79 outils avec des graphiques visuels et une analyse approfondie de la télémétrie via FastF1.