F1 Mcp

F1 MCP

What is F1 MCP about?

F1 MCP exposes Formula 1 historical and live data as MCP endpoints. It leverages the FastF1 library to fetch and cache driver stats, race outcomes, circuit specs, lap‑by‑lap information, and detailed telemetry, making the data programmatically available for downstream applications.

How to use F1 MCP?

1. Install the package:

   pip install f1-mcp
   

2. Run the server (choose one of the methods):
   • Using Hatch:

     hatch run f1_mcp_server.py
     

   • Direct Python execution:

     python src/f1_mcp/f1_mcp_server.py
     

3. Configure your MCP client (e.g., Claude Desktop) to point to the server script.

Key Features

• Driver Information – Retrieve drivers for any season, filter by name or three‑letter code.
• Race & Session Results – Access full race results or specific session outcomes (FP1‑3, Qualifying, Sprint, Race).
• Circuit Details – Get circuit layout, location, and event metadata for a given race.
• Lap Data – Pull all lap records for a driver in a session or the fastest lap of a session.
• Telemetry – Detailed per‑lap telemetry (speed, throttle, brake, gear, etc.).
• Local Caching – Automatic caching of downloaded F1 data in f1_data_cache to speed up subsequent requests.
• Timeout Guidance – Recommended large request timeout because FastF1 initialization can be lengthy.

Use Cases

• Building dashboards that display historic race statistics.
• Creating simulation or analysis tools that need precise telemetry.
• Enabling chat‑based assistants (e.g., Claude) to answer F1‑related queries.
• Automating generation of season summaries or driver performance reports.
• Supplying data for machine‑learning models that predict race outcomes.

FAQ

• Why does the first request take longer? The server downloads the required F1 files from the FastF1 data source and caches them locally. Subsequent requests hit the cache and are fast.
• Which session types are supported? FP1, FP2, FP3, Q1, Q2, Q3, Sprint, and Race.
• How do I change the cache location? By default it uses f1_data_cache in the working directory; you can set the FASTF1_CACHE_DIR environment variable before starting the server.
• Do I need an API key? No external API key is required; FastF1 fetches data from public sources.
• Can I run the server inside a Docker container? Yes, any Python‑compatible container can install the package and launch f1_mcp_server.py.

f1-mcp

A Model Context Protocol (MCP) server that provides access to Formula 1 data including race results, driver information, lap times, telemetry, and circuit details using the FastF1 library.

Installation

Installation is done using hatch.

pip install f1-mcp

Running the Server

Using hatch:

hatch run f1_mcp_server.py

Using python directly:

python src/f1_mcp/f1_mcp_server.py

Using the MCP inspector:

npx @modelcontextprotocol/inspector python src/f1_mcp/f1_mcp_server.py

Make sure to set a large timeout for requests, FastF1 takes a long time to load data upon startup.

The server will start and create a local cache directory (f1_data_cache) to store F1 data for faster subsequent requests.

Claude Desktop Configuration

Add the following configuration to your claude_desktop_config.json file:

{
  "mcpServers": {
    "f1-stats": {
      "command": "python",
      "args": ["path/to/your/f1_mcp_server.py"],
      "env": {}
    }
  }
}

Replace path/to/your/f1_mcp_server.py with the actual path to your server file.

Available Endpoints

Driver Information

• get_drivers_tool - Get F1 drivers for a season, optionally filtered by name or code query

Race Results

• get_race_results_tool - Get race results for a season, optionally filtered by specific race name
• get_session_results_tool - Get session results for a specific race and session type (FP1, FP2, FP3, Qualifying, Sprint, Race)

Circuit Information

• get_circuit_info_tool - Get circuit information and event details for a specific race

Lap Data

• get_driver_laps_tool - Get all lap data for a specific driver in a specific session
• get_fastest_lap_tool - Get the fastest lap information for a specific session

Telemetry

• get_lap_telemetry_tool - Get detailed telemetry data (speed, throttle, brake, etc.) for a specific lap

Notes

• Make sure to set a large timeout for requests, FastF1 takes a long time to load data upon startup.
• The server automatically caches F1 data locally to improve performance
• First-time requests for a season may take longer as data is downloaded and cached
• Session types include: FP1, FP2, FP3, Q1, Q2, Q3, Sprint, Race
• Driver codes are typically 3-letter abbreviations (e.g., HAM, VER, LEC)