home / mcp / f1 mcp server

F1 MCP Server

Provides Formula 1 data via an MCP server with race, session, standings, and lap-time endpoints.

Installation

Add the following to your MCP client configuration file.

Configuration

{
  "mcpServers": {
    "josh-mantel-mcp-f1": {
      "command": "mcp-inspector",
      "args": [
        "uv",
        "run",
        "python",
        "-m",
        "f1_mcp_server.server"
      ]
    }
  }
}

You can run an MCP server that exposes Formula 1 data and test it interactively with the MCP Inspector. This setup lets you fetch race schedules, session results, lap times, and standings from a live API you control locally.

How to use

You will access the F1 MCP server through an MCP client or the MCP Inspector. Start the server in a local environment and then use the available tools to retrieve data such as race calendars, session results, driver standings, constructor standings, and lap times. The Inspector provides a web UI for exploring these tools and validating responses in real time.

How to install

Prerequisites you need before starting are Python 3.13 and the uv package manager.

# macOS/Linux
curl -LsSf https://astral.sh/uv/install.sh | sh

# Windows
powershell -c "irm https://astral.sh/uv/install.ps1 | iex"

Set up and run the F1 MCP server using the provided setup steps.

# Quick setup
./quick-start.sh

# Or manually
make install
# or: uv sync && uv pip install -e .

Start the server in MCP mode for MCP Inspector testing, or in HTTP mode for OAuth testing.

# MCP mode (for MCP Inspector)
make mcp

# HTTP mode (for OAuth testing)  
make http

# With MCP Inspector
make inspector

If you want to run the MCP Inspector alongside the server, use the inspector workflow.

# Using make command (recommended)
make inspector

# Or manually
mcp-inspector uv run python -m f1_mcp_server.server

Once the inspector is running, open the web interface to test and explore available tools at the default URL.

Additional content

Inspector setup and usage provide an interactive way to validate your server. The MCP Inspector supports testing the following tools against the F1 MCP server: get_race_schedule, get_session_results, get_driver_standings, get_constructor_standings, get_lap_times.

If you run into issues, verify your Node.js version for the inspector, ensure the inspector is installed globally, and check that the server starts without the inspector first to isolate connectivity problems.

Common troubleshooting steps include: - Inspecting the Node.js version (needs 16+) - Reinstalling the MCP Inspector globally - Ensuring the server starts without the inspector to rule out access problems - Resolving port conflicts by terminating processes using the inspector port (default 5173)

Available tools

get_race_schedule

Fetches the race schedule for a specific season, enabling you to browse calendars and plan tests.

get_session_results

Retrieves results for a particular session (practice, qualifying, or race) to review outcomes and timings.

get_driver_standings

Returns driver championship standings to track how drivers rank across the season.

get_constructor_standings

Returns constructor standings to compare team performances across the season.

get_lap_times

Provides detailed lap timing data for a session or driver to analyze performance.