Formula 1 MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| f1_mcp_server_update_driversD | – |
| f1_mcp_server_driver_championship_standingsC | Get the championship standing for a specific driver in a given year. |
| f1_mcp_server_update_constructorsD | – |
| f1_mcp_server_constructor_championship_standingsB | Get the championship standing for a specific constructor in a given year. |
| f1_mcp_server_get_event_infoC | Retrieve information about a specific Formula 1 event. |
| f1_mcp_server_get_season_calendarA | Get the complete race calendar for a specific F1 season. |
| f1_mcp_server_track_visualizationC | Generate a visualization of the track with specified data. |
| f1_mcp_server_get_session_resultsC | Retrieve and format the results of a specific session. |
| f1_mcp_server_get_driver_infoC | Retrieve detailed information about a specific driver. |
| f1_mcp_server_get_constructor_infoC | Retrieve detailed information about a specific constructor. |
| f1_mcp_server_get_api_endpointsA | Retrieve a list of all available OpenF1 API endpoints. Returns: dict: A dictionary containing a single key 'endpoints' with a list of available endpoint names as strings. |
| f1_mcp_server_get_api_endpointC | Retrieve the API endpoint URL and filter metadata for a given OpenF1 endpoint. |
| f1_mcp_server_get_endpoint_infoC | Retrieve detailed information about a specific OpenF1 API endpoint. |
| f1_mcp_server_get_filter_infoC | Retrieve detailed information about a specific OpenF1 API filter. |
| f1_mcp_server_get_filter_stringC | Create a filter string for OpenF1 API requests. |
| f1_mcp_server_apply_filtersC | Apply one or more filter strings to an API endpoint URL. |
| f1_mcp_server_send_requestB | Send an HTTP GET request to the specified API endpoint and return the JSON response. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 17 tools
Core F1 retrieval tools (standings, event info, session results, driver/constructor info) are clearly distinct. However, the OpenF1 API plumbing tools (get_api_endpoints, get_api_endpoint, get_endpoint_info, get_filter_info, get_filter_string, apply_filters, send_request) overlap heavily in purpose, and update_drivers/update_constructors have no descriptions, making their boundaries unclear.
All tools share a consistent f1_mcp_server_ prefix and mostly use verb_noun or verb_resource naming (get_*, update_*). Minor deviations exist: championship_standings and track_visualization lack explicit verbs, and get_api_endpoint vs get_api_endpoints differ only by plural.
17 tools is on the heavy side for an F1 data server. While core domain tools are justified, seven generic OpenF1 API access/filter tools appear to expose implementation plumbing rather than distinct user-facing capabilities, inflating the count.
The surface covers key F1 entities (drivers, constructors, standings, events, calendars, session results) and generic OpenF1 request tools provide fallback access to unmodeled data like laps, telemetry, or pit stops. Explicit list/search tools and clear update semantics are missing, but agents can work around most gaps.