F1

The F1 MCP Server provides a comprehensive suite of Formula 1 analytics tools accessible via the MCP interface. It supports real-time telemetry processing, tire degradation modeling, weather impact analysis, and Monte Carlo-based race strategy simulations, along with live data integration for the current season. Users can invoke core analysis tools such as Session Data Analysis, Tire Performance Analysis, Lap Time Analysis, Weather Impact Prediction, Race Strategy Simulation, Driver Performance Analysis, Real-time Telemetry Processing, and Sector Performance Analysis. Additionally, 2025 live data tools offer current season information, full race calendar history, live timing connections, and API status monitoring. In Claude, configure the MCP server as a local service and then reference its endpoints through the MCP API to perform analyses, retrieve data, and generate strategy recommendations.

Once configured, you can run specific analyses by calling the tool functions described in the documentation, for example: Get session data for a given year/round and session type; run Monte Carlo simulations for different pit-stop strategies; predict weather impacts and derive tire strategies; analyze driver versus car performance. The server is designed for real-time telemetry streams and historical data, enabling both live and retrospective analytics for race weekends and training sessions. The included usage examples show how to request tire degradation insights, perform strategy simulations, and evaluate weather effects to inform tire choices and strategy planning.

Prerequisites:

• Node.js 18.0.0 or higher
• npm (comes with Node.js)
• Claude Desktop (for integrating with Claude)

Step 1: Clone and install

# Clone the repository
git clone https://github.com/stagsz/F1-MCP-Server
cd F1-mcp-server

# Install dependencies
npm install

# Run tests to verify installation
npm test

Step 2: Configure Claude Desktop (required for integration)

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

Step 3: Add MCP server configuration Add or update the following to claude_desktop_config.json (example with Node.js server):

{
  "mcpServers": {
    "f1-mcp-server": {
      "command": "node",
      "args": ["path/to/F1-mcp-server/index.js"],
      "env": {
        "NODE_ENV": "production"
      }
    }
  }
}

Replace path/to/F1-mcp-server/index.js with the absolute path to your F1-mcp-server index.js. For Windows, macOS, and Linux examples are provided in the README and should be mirrored with the actual paths.

Step 4: Restart Claude Desktop Quit and relaunch Claude Desktop to load the new MCP server configuration.

Tips and notes:

• Ensure Node.js version is exactly 18.0.0 or higher and that npm is available in your PATH.
• If Claude cannot locate the server, verify absolute paths in claude_desktop_config.json and that Claude Desktop was fully restarted after changes.
• You can enable verbose/debug logs by setting LOG_LEVEL=debug before starting npm (for development): export LOG_LEVEL=debug npm start
• Common issues include missing dependencies, incorrect index.js path, or permissions problems on Linux/macOS. If you encounter permission issues, make index.js executable (chmod +x index.js).
• The server supports real-time telemetry and historical data; ensure data sources (F1 Live Timing, OpenF1, Ergast) are accessible for live data features.
• The 300M-1B+ Monte Carlo permutations indicate heavy compute; for live testing, consider limiting simulation runs or using sample data during development.