Pitwall MCP Server

F1 race engineer for Claude — 67 tools for telemetry, strategy, and 75 years of history

Remote serverstreamable-httpPython

What is the Pitwall MCP server?

F1 race engineer for Claude — 67 tools for telemetry, strategy, and 75 years of history. The pitwall mcp server wraps that behind the Model Context Protocol, so an assistant can use it through 14 defined tools rather than through you.

What it actually does

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

  • 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

Its toolset

Everything the assistant can do here goes through one of these:

  • Category — What You Get
  • 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

Adding it to your client

Being a remote server, there is no local install. You register the endpoint with your client, authorise it once, and the tools appear.

When to reach for it

Plenty of planning and project tracking servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Pitwall's toolset — Category, list_seasons, list_races and 11 more — is a fair guide to whether it matches your workflow. It is maintained by darshjoshi; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.

Caveats

  • Your data travels to the provider's service, so the usual questions apply about what you send and what they retain.
  • With 14 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch Pitwall.
  • MCP clients confirm each tool call by default. Leave that on until you have watched what the pitwall mcp server does with a few real requests.

Available tools

ToolWhat it does
CategoryWhat You Get
list_seasonsAvailable seasons (2018-present)
list_racesFull season calendar with dates
get_race_infoSession details and available data feeds
get_standingsRace classification — positions, gaps, best laps, pits
get_lap_timesLap-by-lap times, filterable by driver and lap range
get_telemetrySpeed, RPM, throttle, brake, gear, DRS for a specific lap
get_tyre_strategyCompound, stint length, new/used for every driver
get_pit_stopsAll pit stops sorted by fastest
get_race_controlFlags, penalties, safety cars, investigations
get_weatherAir/track temp, rain, humidity, wind
get_speed_trapsSpeed at 4 measurement points per driver
get_driver_comparisonHead-to-head: position, pace, strategy, pit stops
get_historical_resultsRace results from 1950 to present

How to install the Pitwall MCP server

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

Add to claude_desktop_config.json, then restart Claude Desktop.

Example prompts to try

  • Use Pitwall to Category.
  • Use Pitwall to list seasons.
  • Use Pitwall to list races.

Frequently asked questions

It connects Pitwall to MCP-compatible AI assistants such as Claude and Cursor, exposing 14 tools (Category, list_seasons, list_races, and more) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with Pitwall directly.