F1 Data Server

io.github.drivenrajatPublished by GitHub account drivenrajatv0.1.0Updated Nov 3, 2026

Access Formula 1 race data, telemetry, lap times, standings, and analytics powered by FastF1

VerifiedSTDIODesktop onlyLocation & LifestyleData & Analytics

Overview

AI-generated overview

Local MCP server that gives an assistant Formula 1 race data, telemetry, lap timing, strategy and standings via FastF1 and related APIs.

What you can do
  • Retrieve race, sprint and qualifying results, grids, DNF lists and historical winners
  • Compare driver telemetry: speed traces, gears, brake, throttle, RPM and DRS
  • Query lap timing, fastest laps, sector times, deleted laps and consistency
  • Analyze strategy: tire compounds, stints, pit stops and starting tires
  • Read championship standings, track records, circuit info, weather and race control messages
  • Check live session status, positions, lap times and telemetry
When to use it
Useful when you want to ask an assistant about Formula 1 results, telemetry comparisons, tire strategy or championship standings, and want the data pulled from FastF1 and public F1 APIs rather than from memory.
Requirements
Runs locally over stdio as a Python package (f1-mcp) needing Python 3.10 or higher; the README describes installing from the repository and registering it in Claude Desktop. Network access is needed to fetch FastF1, Ergast and OpenF1 data. No API keys or environment variables are declared.
Before you install
Data is fetched from third-party sources (FastF1, Ergast, OpenF1), so queries and session details go to those services. FastF1 data is cached in a local cache directory. Live data depends on those external APIs being available.

Installation

In SourceWeft

  1. Open F1 Data Server in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

F1 MCP Server

A Model Context Protocol (MCP) server that provides comprehensive Formula 1 data and analytics for Claude Desktop integration.

Features

This server exposes 36+ tools for accessing F1 data:

Race Data

  • Race results and classifications
  • Sprint race results
  • Qualifying progression (Q1, Q2, Q3)
  • Grid vs finish comparisons
  • DNF lists and retirement reasons

Telemetry & Analysis

  • Speed trace comparisons between drivers
  • Gear shift visualizations
  • Brake and throttle analysis
  • RPM and engine data
  • DRS usage patterns

Timing & Laps

  • Fastest lap data with sector times
  • Lap-by-lap timing
  • Deleted laps (track limits)
  • Lap consistency statistics
  • Personal best laps

Strategy

  • Tire compound analysis
  • Stint breakdowns
  • Pit stop data and fastest stops
  • Starting tire choices
  • Strategy comparisons

Standings & History

  • Driver championship standings
  • Constructor standings
  • Historical race winners
  • Track records

Live Data

  • Live session status
  • Real-time positions
  • Live lap times
  • Live telemetry
  • Current weather conditions

Other

  • Team radio links
  • Race control messages
  • Track status (flags, safety car)
  • Weather data
  • Circuit information

Installation

Prerequisites

  • Python 3.10 or higher
  • Claude Desktop

Setup

  1. Clone this repository:
bash
git clone https://github.com/drivenrajat/f1.gitcd f1
  1. Create a virtual environment:
bash
python -m venv venvsource venv/bin/activate  # On Windows: venv\Scripts\activate
  1. Install dependencies:
bash
pip install -e .

Configure Claude Desktop

Add this server to your Claude Desktop MCP configuration (~/Library/Application Support/Claude/claude_desktop_config.json on macOS):

json
{  "mcpServers": {    "f1": {      "command": "python",      "args": ["/path/to/f1/f1_server.py"]    }  }}

Or if using uv:

json
{  "mcpServers": {    "f1": {      "command": "uv",      "args": ["run", "--directory", "/path/to/f1", "python", "f1_server.py"]    }  }}

Usage

Once configured, you can ask Claude questions like:

  • "Show me the 2024 F1 calendar"
  • "Get the race results from Monaco 2024"
  • "Compare telemetry between Verstappen and Norris at Silverstone qualifying"
  • "What was Hamilton's tire strategy at Spa?"
  • "Show me the current driver standings"
  • "Get the fastest pit stops from the Italian GP"

Data Sources

  • FastF1: Historical telemetry, lap times, and session data
  • Ergast API: Championship standings and historical results
  • OpenF1 API: Team radio recordings

Caching

The server automatically caches FastF1 data in a cache directory to improve performance on repeated queries.

License

MIT License - see LICENSE for details.

Contributing

Contributions are welcome! Please feel free to submit a Pull Request.

Source: README.md at commit 21c226f

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.1.0LatestSep 16, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts