Labsco
MCP SERVER

F1 MCP Server

by stagsz ↗

Formula 1 session data, tire degradation and pit-strategy simulation, asked for in plain language.

Sports, Fantasy & Esports Data
Summary
Read the model assumptions before you quote a number.

The driver analysis is built on a stated 88%/12% car-versus-driver split and the weather forecast on an LSTM/CNN ensemble — those are modelling choices, not measurements, and the answers inherit them. Where the server is unambiguously useful is the comparison work: fuel-corrected lap times and 25 mini-sector splits are exactly the transformations that make two stints comparable, and doing them by hand is the tedious part.

What it is

A Formula 1 analytics server. It pulls session data for a given year, round and session type, then layers analysis on top: tire degradation curves, fuel-corrected lap times, weather forecasting for strategy, and Monte Carlo simulation of pit strategies.

What you get
  • `get_session_data` for a race weekend, taking `year`, `round` and `session` — Practice 1-3, Qualifying, Sprint or Race
  • `analyze_tire_performance` returns degradation curves, grip-loss patterns and optimal stint lengths, filterable by `driver` and `compound`
  • `analyze_lap_times` applies fuel correction and breaks the lap into 25 mini-sectors
  • `simulate_race_strategy` runs Monte Carlo over `strategy_options` — the `simulations` argument defaults to 10,000
  • `predict_weather_impact` forecasts over a `forecast_hours` window, default 3
  • `analyze_driver_performance` separates driver from car and can compare against a `comparison_driver`
  • `get_real_time_telemetry` and `analyze_sector_performance` work over channels including `Speed`, `Throttle`, `Brake`, `DRS`, `Gear`, `RPM`, `TireTemp`, `BrakeTemp`, `GPS` and `EngineTemp`
  • Live-season tools — `get_current_season_info`, `get_race_schedule`, `connect_live_timing`, `get_live_timing_status`, `get_api_status`
Requirements

Node.js 18.0.0 or higher and npm. Published as f1-mcp-server version 2.0.0; the documented path is clone, `npm install`, then point your client's `command` at node and its `args` at the absolute path of `index.js`. No API key is listed. Data comes from F1 Live Timing, the OpenF1 API and the Ergast API, with simulation as the fallback; coverage runs 2018-2025 and round numbers 1-24.

Setup effort

Build from source — clone the repository and build it, then point your client at the binary