Formula One MCP Server
Serves as the runtime environment for the MCP server, executing the server code that interfaces with the FastF1 Python library.
Utilized as a dependency for processing Formula One data, particularly for mathematical operations related to telemetry data analysis.
Used for data manipulation and analysis of Formula One statistics, handling structured data from race results, lap times, and other performance metrics.
Leverages the FastF1 Python library to provide access to Formula One data including race calendars, event information, session results, driver statistics, lap times, telemetry, and championship standings.
Used as the programming language for the MCP server implementation, providing type safety for Formula One data processing.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Formula One MCP Server show me the 2024 race calendar"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Formula One MCP Server
This Model Context Protocol (MCP) server provides access to Formula One data and statistics using the FastF1 Python library. It allows you to access race calendars, event information, session results, driver data, lap times, telemetry, and championship standings through a clean MCP interface.
Features
Get Formula One race calendars for specific seasons
Retrieve detailed information about Grand Prix events
Get session results (Race, Qualifying, Practice)
Access driver information and statistics
Analyze driver performance with lap times and telemetry data
Compare multiple drivers' performance
Get championship standings for drivers and constructors
Related MCP server: Formula One MCP Server
Prerequisites
Node.js 18 or later
Python 3.8 or later
FastF1 library
Installation
1. Install Python dependencies
pip install fastf1 pandas numpy2. Install Node.js dependencies
cd f1-mcp-server
npm install3. Build the TypeScript code
npm run build4. Add to MCP settings
Add the following to your Cline MCP settings file (~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json):
{
"mcpServers": {
"formula1": {
"command": "node",
"args": ["/Users/rakeshgangwar/Documents/Cline/MCP/f1-mcp-server/build/index.js"],
"disabled": false,
"autoApprove": []
}
}
}Available Tools
1. get_event_schedule
Get Formula One race calendar for a specific season.
Parameters:
year(number): Season year (e.g., 2023)
2. get_event_info
Get detailed information about a specific Formula One Grand Prix.
Parameters:
year(number): Season year (e.g., 2023)identifier(string): Event name or round number (e.g., "Monaco" or "7")
3. get_session_results
Get results for a specific Formula One session.
Parameters:
year(number): Season year (e.g., 2023)event_identifier(string): Event name or round number (e.g., "Monaco" or "7")session_name(string): Session name (e.g., "Race", "Qualifying", "Sprint", "FP1", "FP2", "FP3")
4. get_driver_info
Get information about a specific Formula One driver.
Parameters:
year(number): Season year (e.g., 2023)event_identifier(string): Event name or round number (e.g., "Monaco" or "7")session_name(string): Session name (e.g., "Race", "Qualifying", "Sprint", "FP1", "FP2", "FP3")driver_identifier(string): Driver identifier (number, code, or name; e.g., "44", "HAM", "Hamilton")
5. analyze_driver_performance
Analyze a driver's performance in a Formula One session.
Parameters:
year(number): Season year (e.g., 2023)event_identifier(string): Event name or round number (e.g., "Monaco" or "7")session_name(string): Session name (e.g., "Race", "Qualifying", "Sprint", "FP1", "FP2", "FP3")driver_identifier(string): Driver identifier (number, code, or name; e.g., "44", "HAM", "Hamilton")
6. compare_drivers
Compare performance between multiple Formula One drivers.
Parameters:
year(number): Season year (e.g., 2023)event_identifier(string): Event name or round number (e.g., "Monaco" or "7")session_name(string): Session name (e.g., "Race", "Qualifying", "Sprint", "FP1", "FP2", "FP3")drivers(string): Comma-separated list of driver codes (e.g., "HAM,VER,LEC")
7. get_telemetry
Get telemetry data for a specific Formula One lap.
Parameters:
year(number): Season year (e.g., 2023)event_identifier(string): Event name or round number (e.g., "Monaco" or "7")session_name(string): Session name (e.g., "Race", "Qualifying", "Sprint", "FP1", "FP2", "FP3")driver_identifier(string): Driver identifier (number, code, or name; e.g., "44", "HAM", "Hamilton")lap_number(number, optional): Lap number (gets fastest lap if not provided)
8. get_championship_standings
Get Formula One championship standings.
Parameters:
year(number): Season year (e.g., 2023)round_num(number, optional): Round number (gets latest standings if not provided)
Example Usage
Once the server is added to your MCP settings and running, you can use these tools with Cline to access Formula One data.
Example queries:
"Show me the 2023 Formula One race calendar"
"Get the results from the 2022 Monaco Grand Prix"
"Compare Hamilton and Verstappen's performance in the 2021 British Grand Prix"
"Show me the telemetry data from Leclerc's fastest lap in the 2023 Italian Grand Prix qualifying"
"What are the current F1 championship standings?"
Data Source
This server uses the FastF1 Python library, which provides access to official Formula 1 timing data, car telemetry, and session results.
License
MIT
Available Tools
8 toolsanalyze_driver_performanceC
Analyze a driver's performance in a Formula One session
Inputs: driver_identifier (required), event_identifier (required), session_name (required), year (required).
compare_driversC
Compare performance between multiple Formula One drivers
Inputs: drivers (required), event_identifier (required), session_name (required), year (required).
get_championship_standingsC
Get Formula One championship standings
Inputs: year (required), round_num.
get_driver_infoC
Get information about a specific Formula One driver
Inputs: driver_identifier (required), event_identifier (required), session_name (required), year (required).
get_event_infoB
Get detailed information about a specific Formula One Grand Prix
Inputs: identifier (required), year (required).
get_event_scheduleA
Get Formula One race calendar for a specific season
Inputs: year (required).
get_session_resultsC
Get results for a specific Formula One session
Inputs: event_identifier (required), session_name (required), year (required).
get_telemetryC
Get telemetry data for a specific Formula One lap
Inputs: driver_identifier (required), event_identifier (required), session_name (required), year (required), +1 more.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 8 tools
Mostly distinct: get_driver_info is reference data, get_session_results is outcomes, and get_telemetry focuses on lap data. However, compare_drivers and analyze_driver_performance both deal with performance analysis and could be confused in some agent workflows.
Six tools follow a clear get_<noun> pattern, while compare_drivers and analyze_driver_performance use verb_noun instead. This is a minor deviation but the verbs are meaningful and there is no mixed casing or chaotic style.
Eight tools is a well-scoped size for an F1 data server, covering schedules, events, sessions, standings, driver information, and analysis without excessive redundancy.
The set covers core read-only F1 workflows: calendar, event info, session results, standings, driver details, telemetry, and performance analysis. It lacks constructor/team-specific tools and some historical depth, but those are not critical gaps for a typical F1 data agent.
Maintenance
Related MCP Connectors
Anonymous read-only Formula 1 tools, resources, prompts, completion, and interactive dashboard.
Read-only F1 game laps, telemetry, setups, leaderboard benchmarks, and progress.
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceProvides real-time and historical Formula 1 racing data through the Model Context Protocol, offering access to timing data, driver stats, race results, telemetry, and more.15MIT
- AlicenseAqualityDmaintenanceA Model Context Protocol server that provides comprehensive Formula One racing data, enabling access to event schedules, driver information, telemetry data, race results, and performance analytics through natural language queries.81MIT
- FlicenseNot gradedqualityDmaintenanceEnables access to Formula 1 data from the openF1.org API, including driver information, race results, lap times, telemetry, pit stops, weather conditions, and live position data across multiple seasons.-
- AlicenseNot gradedqualityDmaintenanceProvides real-time access to football (soccer) data including fixtures, standings, teams, players, transfers, and injuries through the API-Football service via the Model Context Protocol.4ISC