Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type @ followed by the MCP server name and your instructions, e.g., "@mcp-f1 What are the current F1 standings?"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
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 |
| Check current F1 driver championship standings. Returns position, points, wins, driver name, and constructor for all drivers. |
| 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 the F1 season race calendar. Provide year (e.g., 2024). Returns all rounds with race name, circuit, location, and date. |
| Look up F1 driver profile by ID. Returns name, car number, nationality, and date of birth. |
Related MCP server: OpenF1 MCP Server
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
This server cannot be installed
Unclaimed servers have limited discoverability.
If you are the server author, to access and configure the admin panel.
Sports MCP — wraps TheSportsDB API (free tier, test key 3, no auth required)
API Ninjas MCP — wraps the multi-endpoint API Ninjas data API (api-ninjas.com)
Access and interact with anime and manga data seamlessly. Retrieve detailed information about your…
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/pipeworx-io/mcp-f1'
If you have feedback or need assistance with the MCP directory API, please join our Discord server