Openf1

What the Openf1 MCP server does

The Openf1 MCP server gives AI agents access to Formula 1 meeting, session, driver, and lap data. It covers Grand Prix weekends and individual Race, Qualifying, and Practice sessions, including both historical queries and live race data.

The available data includes meeting identifiers and event details, session identifiers, driver entries, and lap-level timing. Driver records include race number, name, three-letter abbreviation, team, team colour, country, and headshot. Lap records can include lap duration, sector times, speed-trap information, and whether the lap followed a pit exit.

How it works

The server exposes four tools over MCP:

• get_meetings finds Grand Prix weekends and can filter results by year or country.
• get_sessions finds sessions within the available meetings. Filters include year, country, session name, and meeting_key.
• get_drivers returns drivers entered in a selected session.
• get_laps returns lap timing and telemetry for a selected session, with optional driver-number and lap-number filters.

A typical lookup starts with get_meetings, continues with get_sessions to obtain a session_key, and then uses that key with get_drivers or get_laps. For driver and lap queries, session_key="latest" selects the most recent or ongoing session.

The remote endpoint is hosted at https://gateway.pipeworx.io/openf1/mcp. It lists the Openf1 tools along with shared Pipeworx gateway tools. Those shared tools include routing and discovery functions such as ask_pipeworx; the gateway documentation states that the exact tool scope is reported by the MCP initialize response.

Setup and configuration

You can add the remote endpoint to an MCP client with a server entry containing the URL. The documented examples name Claude Desktop, Cursor, and Windsurf as clients that can connect to it.

A local stdio installation is also available through the @pipeworx/mcp-openf1 npm package:

{
  "mcpServers": {
    "openf1": {
      "command": "npx",
      "args": ["-y", "@pipeworx/mcp-openf1"]
    }
  }
}

Running npx -y @pipeworx/mcp-openf1 starts the local process directly. The local process communicates over stdin and stdout and exposes only the four Openf1 tools, without the gateway's shared meta-tools.

For clients without MCP support, the gateway also provides HTTP tool endpoints. For example, POST https://gateway.pipeworx.io/v1/tools/get_meetings accepts a JSON body such as {"year":2024}. A GET request to the corresponding tool endpoint can be used to inspect a tool.

Tools and capabilities

The Openf1 MCP server is suited to workflows that need to identify a race weekend, resolve its sessions, inspect the drivers in a session, or analyze lap timing. Its filters help narrow results before an agent processes them, especially when working with a particular year, country, meeting, driver, or lap.

The gateway can also accept natural-language requests through ask_pipeworx, which selects a tool and fills its arguments. That routing capability belongs to the gateway connection; it is not included in the standalone stdio process.

Limitations and notes

The server focuses on the four documented Formula 1 data operations. It does not claim to provide general motorsport coverage or tools beyond those operations. Gateway connections list additional shared tools, so the tool count shown by a client may be larger than the four Openf1-specific tools. The gateway's initialize response is the authoritative source for the exact scope on a given day.

Use get_sessions before driver or lap lookups when the required session_key is not already known. The latest value is intended for the most recent or ongoing session and is not a substitute for selecting a specific historical session.