mcpField
F
F1 Mcp Server

F1 Mcp Server

Local
github.com/Darakhsh1999Games & Entertainment1Updated 70w ago

About F1 Mcp Server

F1 Mcp Server provides Formula 1 data and statistics for fans, analysts, and developers through FastF1 and the OpenF1 API. Its Gradio interface organizes standings, events, session results, visualizations, and API queries.

Key features

  1. 01Championship standings
  2. 02Grand Prix schedules and circuit details
  3. 03Season calendars
  4. 04Fastest-lap visualizations
  5. 05Session results and statistics
  6. 06Direct OpenF1 API queries

Use cases

  1. 01Reviewing season standings
  2. 02Exploring Grand Prix schedules and circuits
  3. 03Inspecting session results
  4. 04Querying OpenF1 data

MCP support

The project exposes Formula 1 data through an MCP server defined in `app.py`. An included client and AI agent connect to it over SSE transport.

Configuration

Local server config is the same for every client. Copy it into your client’s MCP config file.

No install method listed yet

We haven’t collected a package or remote endpoint for this server. Follow the instructions in the project README.

Repository

Tools

No tool list yet

Local servers expose tools only once running on your machine, and the maintainer has not provided a tool list.

Details

From the project README

🏁 Formula 1 MCP Server 🏎️

This project defines a MCP server for Formula 1 data, providing fans, analysts, and developers with easy access to a vast range of F1 statistics and information. Built with Python and powered by the Gradio framework, it offers a user-friendly web interface to explore historical and recent F1 data from the FastF1 library and the official OpenF1 API.

Video Demo (Claude Desktop)

Demo Video

Architecture

Architectural overview of the MCP server and client. The MCP server is hosted using a Gradio back-end and can be either run locally or on a remote server.

README image
Gradio Key Features

The interface is organized into several Gradio tabs, each dedicated to a specific type of F1 data:

  • Championship Standings: View final driver and constructor championship standings for any season from 1950 to the present.
  • Event Information: Get detailed information for any Grand Prix, including schedules and circuit details.
  • Season Calendar: Display the complete race calendar for a given year.
  • Track Visualizations: Generate and view plots of the fastest race lap, visualizing speed, gear changes, and cornering G-forces.
  • Session Results: Fetch detailed results for any race session (Practice, Qualifying, or Race).
  • Driver & Constructor Info: Look up background information and statistics for drivers and teams.
  • OpenF1 API Tools: An advanced toolkit for developers to directly query the OpenF1 API, build custom requests, and view raw JSON responses.
Tech Stack
  • Backend: Python
  • Web Framework: Gradio
  • Data Sources:
    • fastf1 Python library for historical data.
    • openf1 for live and recent data via their public API.
  • Key Libraries: pandas, matplotlib

MCP Server

The MCP server is defined inside app.py.

MCP Client

The MCP client and AI agent is defined inside mcp_client.py and allows interaction with the MCP server through server side events (SSE) transport.

MCP configuration file

For MCP clients that support SSE transport (for Claude Desktop, see below), the following configuration can be used:

{
  "mcpServers": {
    "gradio": {
      "url": "https://agents-mcp-hackathon-f1-mcp-server.hf.space/gradio_api/mcp/sse"
    }
  }
}

For Claude Desktop, the following configuration can instead be used, but make sure you have Node.js installed:

{
  "mcpServers": {
    "gradio": {
      "command": "npx",
      "args": [
        "mcp-remote",
        "https://agents-mcp-hackathon-f1-mcp-server.hf.space/gradio_api/mcp/sse",
        "--transport",
        "sse-only"
      ]
    }
  }
}

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.