Open Formula 1 Mcp Server

Created By
Open-F1-MCP-Server8 months ago
This project implements the MCP Server for Open Formula 1 to gather F1 race, car, driver, lap and various other information. Open Formula 1 is an open-source API that provides real-time and historical Formula 1 data. The API offers a wealth of information, including lap timings, car telemetry, radio communications, and more. Whether you're looking to create interactive dashboards, dive deep into race analysis, or even develop connected objects that light up every time your favorite driver takes the lead, OpenF1 makes it all possible.
Overview

what is Open Formula 1 MCP Server?

Open Formula 1 MCP Server is an open-source API that gathers real-time and historical Formula 1 data, including race, car, driver, and lap information.

how to use Open Formula 1 MCP Server?

To use the Open Formula 1 MCP Server, clone the repository from GitHub, and run the server using the command: python /path/to/OpenF1MCPServer.py.

key features of Open Formula 1 MCP Server?

  • Real-time data on F1 races, cars, and drivers.
  • Historical data for in-depth race analysis.
  • Ability to create interactive dashboards and connected objects.

use cases of Open Formula 1 MCP Server?

  1. Analyzing lap timings and performance metrics of drivers.
  2. Developing applications that visualize race data in real-time.
  3. Creating alerts for when a favorite driver takes the lead.

FAQ from Open Formula 1 MCP Server?

  • What kind of data does the API provide?

The API provides lap timings, car telemetry, radio communications, and more.

  • Is the Open Formula 1 MCP Server free to use?

Yes! It is an open-source project and free for everyone.

  • Where can I find more information?

Detailed information about the implementation can be found on the author's personal page www.aryaakman.com under the "Projects" section.

Server Config

{
  "mcpServers": {
    "Open-F1": {
      "command": "python",
      "args": [
        "/path/to/OpenF1MCPServer.py"
      ]
    }
  }
}
Project Info
Created At
8 months ago
Updated At
8 months ago
Author Name
Open-F1-MCP-Server
Star
-
Language
-
License
-

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago