F1

F1

Access to Formula 1 data including race results, driver information, lap times, telemetry, and circuit details.

9
Stars
0
Forks
0
Releases

Overview

f1-mcp is a Model Context Protocol server that exposes Formula 1 data through a set of MCP endpoints backed by the FastF1 library. It supports retrieving driver information for a season, race results, session results (FP1, FP2, FP3, Q1, Q2, Q3, Sprint, Race), circuit details, lap data for individual drivers, fastest laps, and detailed telemetry for specific laps. Installation is performed with hatch, and the server can be run via hatch run or directly with Python. On startup, it builds a local cache directory named f1_data_cache to store data to improve responsiveness on subsequent requests; first requests for a season may take longer as data is downloaded and cached. Endpoints include get_drivers_tool, get_race_results_tool, get_session_results_tool, get_circuit_info_tool, get_driver_laps_tool, get_fastest_lap_tool, and get_lap_telemetry_tool. The server recommends setting large timeouts due to FastF1 startup latency, and you can inspect or debug with the MCP inspector. Claude Desktop configuration is provided to help configure clients.

Details

Owner
AbhiJ2706
Language
Python
License
MIT License
Updated
2025-12-07

Features

Driver information retrieval

Get F1 drivers for a season, optionally filtered by name or code query.

Race results retrieval

Get race results for a season, optionally filtered by a specific race name.

Session results retrieval

Get session results for a specific race and session type (FP1, FP2, FP3, Qualifying, Sprint, Race).

Circuit information retrieval

Get circuit information and event details for a specific race.

Lap data retrieval

Get all lap data for a specific driver in a specific session.

Fastest lap retrieval

Get the fastest lap information for a specific session.

Telemetry data retrieval

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

Local data caching and startup performance

Automatically caches F1 data locally (f1_data_cache) to improve performance; first requests for a season may take longer as data is downloaded and cached.

Audience

DevelopersExpose Formula 1 data via MCP endpoints for client apps and workflows.
Data scientistsQuery race results, lap data, and telemetry for analysis and research.
MCP tool integratorsTest and validate MCP data flows and tooling using the inspector and related integrations.

Tags

Formula 1F1MCPFastF1telemetryrace_resultsdriver_infolap_timescircuit_detailscacheserver