
Connects Claude to Formula 1 historical data through the Ergast API, a well-known motorsport database covering seasons, races, drivers, constructors, and results going back to 1950. Part of the Pipeworx gateway ecosystem, which means you can either use it standalone or access it alongside 673+ other data sources through a unified interface. The ask_pipeworx feature lets you query in plain English instead of calling specific tools directly. Useful when you need to answer F1 trivia, analyze race statistics, compare driver performance across seasons, or build applications that need reliable motorsport data without managing API credentials yourself.
F1 MCP — Formula 1 data via the Ergast API
Part of Pipeworx — an MCP gateway connecting AI agents to 1476+ live data sources.
| Tool | Description |
|---|---|
get_current_standings | Check current F1 driver championship standings. Returns position, points, wins, driver name, and constructor for all drivers. |
get_race_results | Get race results for a specific F1 grand prix. Provide season year and round number (e.g., 2024, round 5). Returns finishing position, driver, constructor, status, and points. |
get_schedule | Get the F1 season race calendar. Provide year (e.g., 2024). Returns all rounds with race name, circuit, location, and date. |
get_driver | Look up F1 driver profile by ID. Returns name, car number, nationality, and date of birth. |
Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):
{
"mcpServers": {
"f1": {
"url": "https://gateway.pipeworx.io/f1/mcp"
}
}
}
tools/list at https://gateway.pipeworx.io/f1/mcp returns the tools in the table
above plus the shared Pipeworx meta-tools — ask_pipeworx,
discover_tools, search_within, remember/recall and the rest of the
gateway-wide set. So the tool count you see is larger than this table: a
single-pack endpoint currently lists roughly 30 shared tools alongside the
pack's own. The connection's initialize response states its exact scope, and
is the authoritative answer for a given day.
This is deliberate, not multiplexing by accident. The meta-tools are what let a
scoped connection answer a question this pack does not cover — via
ask_pipeworx, which routes across the whole catalog — without you adding a
second MCP server. There is currently no way to mount a pack endpoint without
them; if the extra schemas cost you more context than the routing is worth,
connect to the full gateway once rather than to several pack endpoints.
Or connect to the full Pipeworx gateway to get every pack's tools listed directly, instead of just this one's:
{
"mcpServers": {
"pipeworx": {
"url": "https://gateway.pipeworx.io/mcp"
}
}
}
Both URLs reach the same gateway and the same 1476+ data sources. The
only difference is which pack's tools are listed directly; ask_pipeworx
reaches all of them from either one.
Instead of calling tools directly, you can ask questions in plain English — this works on the pack endpoint above as well as on the full gateway:
ask_pipeworx({ question: "your question about F1 data" })
The gateway picks the right tool and fills the arguments automatically.
MIT