MCPSERV.CLUB
Darakhsh1999

Formula 1 MCP Server

MCP Server

Real-time F1 data access via a Gradio-powered MCP

Stale(55)
0stars
0views
Updated Jun 22, 2025

About

A Python-based MCP server that delivers Formula 1 statistics and live data through a Gradio web interface. It aggregates historical information from FastF1 and real‑time updates from the OpenF1 API, enabling fans, analysts, and developers to explore race data effortlessly.

Capabilities

Resources
Access data sources
Tools
Execute functions
Prompts
Pre-built templates
Sampling
AI model interactions

Demo Video

The Formula 1 MCP Server is a purpose‑built interface that exposes the rich dataset of motorsport history and live telemetry to AI assistants. By turning FastF1 and OpenF1 data into a standardized MCP endpoint, developers can ask conversational agents to pull race results, driver standings, or lap‑by‑lap performance without writing bespoke API calls. The server solves the pain point of data wrangling for F1 enthusiasts, analysts, and sports‑tech startups that want to embed real‑time racing insights into chatbots or analytics dashboards.

At its core, the server hosts a Gradio‑powered web UI that mirrors the same data layers available to humans. The UI is split into logical tabs—championship standings, event details, season calendars, track visualisations, session results, and driver/constructor profiles—each backed by FastF1’s historical parsing or the live OpenF1 API. This design allows an AI client to discover and invoke these resources through simple resource names, while the server handles authentication, caching, and data transformation. The result is a low‑latency, well‑documented API that returns JSON objects ready for natural‑language generation or further processing.

Key capabilities include:

  • Historical and live data fusion: Combine archived season statistics with up‑to‑date telemetry from the OpenF1 API, giving agents a single source of truth for both past and present races.
  • Rich visualisation tools: Generate plots of fastest laps, gear usage, and cornering forces that can be embedded in agent responses or exported for analysis.
  • Custom API access: Through the OpenF1 toolkit tab, developers can craft arbitrary queries to the public API, enabling agents to fetch niche metrics such as pit‑stop times or telemetry streams.
  • SSE transport: The MCP client uses server‑side events to stream real‑time updates, allowing agents to react instantly to live race data.

In practice, a sports journalist could ask an AI assistant for “the fastest lap of the 2024 Monaco Grand Prix” and receive a JSON payload plus a plotted graph, while a data scientist could query “average sector times for every driver in the 2023 season” and integrate the result into a predictive model. Start‑ups building race‑analysis tools can embed the MCP server in their own services, giving end users conversational access to complex F1 metrics without building custom back‑ends.

The server’s architecture—Python, Gradio, pandas, and matplotlib—means it can run locally or be hosted on any cloud platform. Its clear separation of data sources and visualisation layers makes it easy to extend: adding new tabs for telemetry, weather, or broadcast feeds would simply involve wiring additional FastF1/OpenF1 endpoints. For developers already familiar with MCP concepts, the Formula 1 MCP Server offers a ready‑made, data‑rich gateway that turns raw racing statistics into conversational knowledge.