playbooks
Learn Cursor Rules Windsurf Rules MCPs Modes
Log in

Formula 1 MCP server

Integrates with Formula 1 APIs to provide real-time racing data, historical results, driver information, team radio messages, weather conditions, and telemetry for building F1 statistics applications.
Back to servers
Setup instructions
Provider
Panth Shah
Release date
Apr 15, 2025
Language
TypeScript
Stats
11 stars
View on GitHub

The Formula1 MCP Server provides access to real-time and historical Formula 1 racing data through the Model Context Protocol. It offers everything from live telemetry to driver standings and weather information, making F1 data easily accessible through standardized tools.

Installation Options

Quick Install via Smithery

The easiest way to install the Formula 1 MCP Server is through Smithery:

npx -y @smithery/cli install @Panth1823/formula1-mcp --client claude

Manual Installation

If you prefer manual installation:

git clone https://github.com/Panth1823/formula1-mcp
cd formula1-mcp
npm install
npm run build

Configuration

After installation, add the server to your MCP client configuration:

{
  "mcpServers": {
    "formula1": {
      "command": "node",
      "args": ["<path-to-your-cloned-repo>/build/index.js"],
      "cwd": "<path-to-your-cloned-repo>",
      "enabled": true
    }
  }
}

Configuration file locations:

  • Windows: %APPDATA%\.cursor\mcp.json
  • MacOS: ~/.cursor/mcp.json
  • Linux: ~/.config/.cursor/mcp.json

Available Tools

Real-time Data Tools

getLiveTimingData

Get real-time timing data for the current session. Parameters: None required

getCurrentSessionStatus

Get status information about the current session. Parameters: None required

getWeatherData

Get weather data for a session. Parameters:

  • sessionKey (string, optional): Session identifier

getCarData

Get detailed car telemetry data. Parameters:

  • driverNumber (string): Driver's car number (e.g., "44", "33")
  • sessionKey (string, optional): Session identifier
  • filters (string, optional): Data filters

getPitStopData

Get pit stop information. Parameters:

  • driverNumber (string, optional): Driver's car number
  • sessionKey (string, optional): Session identifier

getTeamRadio

Get team radio communications. Parameters:

  • driverNumber (string, optional): Driver's car number
  • sessionKey (string, optional): Session identifier

getRaceControlMessages

Get race control messages. Parameters:

  • sessionKey (string, optional): Session identifier

Historical Data Tools

getDriverInfo

Get information about a specific driver. Parameters:

  • driverId (string): Driver identifier (e.g., "max_verstappen", "lewis_hamilton")

getHistoricalSessions

Find session keys for historical events. Parameters:

  • year (number, optional): Season year (e.g., 2023)
  • circuit_short_name (string, optional): Circuit name (e.g., "monza", "spa")
  • country_name (string, optional): Country name (e.g., "Italy", "Belgium")
  • session_name (string, optional): Session type (e.g., "Race", "Qualifying")

getHistoricRaceResults

Get race results for a specific historical race. Parameters:

  • year (number): Season year (e.g., 2023)
  • round (number): Race number (e.g., 1, 2, 3)

getDriverStandings

Get driver championship standings. Parameters:

  • year (number): Season year (e.g., 2023)

getConstructorStandings

Get constructor championship standings. Parameters:

  • year (number): Season year (e.g., 2023)

getLapTimes

Get lap times for a specific driver. Parameters:

  • year (number): Season year (e.g., 2023)
  • round (number): Race number (e.g., 1, 2, 3)
  • driverId (string): Driver identifier (e.g., "max_verstappen", "lewis_hamilton")

getRaceCalendar

Get the F1 race calendar. Parameters:

  • year (number): Season year (e.g., 2023)

getCircuitInfo

Get detailed circuit information. Parameters:

  • circuitId (string): Circuit identifier (e.g., "monza", "spa")

getSeasonList

Get a list of available F1 seasons. Parameters:

  • limit (number, optional): Number of seasons to return

getQualifyingResults

Get qualifying session results. Parameters:

  • year (number): Season year (e.g., 2023)
  • round (number): Race number (e.g., 1, 2, 3)

getDriverInformation

Get detailed driver information from Ergast API. Parameters:

  • driverId (string): Driver identifier (e.g., "max_verstappen", "lewis_hamilton")

getConstructorInformation

Get detailed constructor information from Ergast API. Parameters:

  • constructorId (string): Constructor identifier (e.g., "red_bull", "mercedes")

Utility Tools

clearCache

Clear the local cache for F1 data. Parameters: None required

Usage Examples

Here are some example queries you can use with the F1 MCP server:

  • "Show 2023 Monaco GP results"
  • "Get current standings"
  • "Weather at Silverstone"
  • "Hamilton's lap times"
  • "Show 2024 calendar"
  • "Verstappen's info"
  • "Japanese GP qualifying"

Debugging

For debugging issues with the MCP server, you can use the MCP Inspector.

How to install this MCP server

For Claude Code

To add this MCP server to Claude Code, run this command in your terminal:

claude mcp add-json "formula1" '{"command":"node","args":["<path-to-your-cloned-repo>/build/index.js"],"cwd":"<path-to-your-cloned-repo>","enabled":true}'

See the official Claude Code MCP documentation for more details.

For Cursor

There are two ways to add an MCP server to Cursor. The most common way is to add the server globally in the ~/.cursor/mcp.json file so that it is available in all of your projects.

If you only need the server in a single project, you can add it to the project instead by creating or adding it to the .cursor/mcp.json file.

Adding an MCP server to Cursor globally

To add a global MCP server go to Cursor Settings > Tools & Integrations and click "New MCP Server".

When you click that button the ~/.cursor/mcp.json file will be opened and you can add your server like this:

{
    "mcpServers": {
        "formula1": {
            "command": "node",
            "args": [
                "<path-to-your-cloned-repo>/build/index.js"
            ],
            "cwd": "<path-to-your-cloned-repo>",
            "enabled": true
        }
    }
}

Adding an MCP server to a project

To add an MCP server to a project you can create a new .cursor/mcp.json file or add it to the existing one. This will look exactly the same as the global MCP server example above.

How to use the MCP server

Once the server is installed, you might need to head back to Settings > MCP and click the refresh button.

The Cursor agent will then be able to see the available tools the added MCP server has available and will call them when it needs to.

You can also explicitly ask the agent to use the tool by mentioning the tool name and describing what the function does.

For Claude Desktop

To add this MCP server to Claude Desktop:

1. Find your configuration file:

  • macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
  • Windows: %APPDATA%\Claude\claude_desktop_config.json
  • Linux: ~/.config/Claude/claude_desktop_config.json

2. Add this to your configuration file:

{
    "mcpServers": {
        "formula1": {
            "command": "node",
            "args": [
                "<path-to-your-cloned-repo>/build/index.js"
            ],
            "cwd": "<path-to-your-cloned-repo>",
            "enabled": true
        }
    }
}

3. Restart Claude Desktop for the changes to take effect

Want to 10x your AI skills?

Get a free account and learn to code + market your apps using AI (with or without vibes!).

Nah, maybe later