OpenF1 MCP By UnClick
Wire live and historical Formula 1 session, timing, and telemetry context into Claude Code or Cursor while building dashboards, fan tools, or sports data side projects.
Overview
OpenF1 MCP is a Build-phase MCP server that lets coding agents query Formula 1 sessions, drivers, laps, pit stops, car data, radio, and weather through stdio tools.
What is this MCP server?
- Query F1 sessions, drivers, positions, laps, and pit stops through MCP tools over stdio
- Access car telemetry, team radio, and session weather from one UnClick OpenF1 server
- Ship as npm @unclick/openf1-mcp with npx runtimeHint (v0.1.0)—no separate OpenF1 API key in the catalog description
- Suited to fantasy helpers, race recap generators, and indie analytics UIs backed by an agent
- Published in the UnClick monorepo with Model Context Protocol server schema 2025-12-11
- Server version 0.1.0
- npm package @unclick/openf1-mcp with stdio transport
- Covers sessions, drivers, positions, laps, pit stops, car data, radio, and weather domains per catalog description
Community signal: 4 GitHub stars.
What problem does it solve?
Agents cannot reliably answer detailed F1 timing and telemetry questions without a dedicated, structured data bridge.
Who is it for?
Indie builders making F1 dashboards, newsletters, or agent-assisted race analysis without building a custom OpenF1 client first.
Skip if: Teams that need official F1 commercial data feeds, broadcast rights workflows, or millisecond trading systems with enterprise SLAs.
What do I get? / Deliverables
After you add @unclick/openf1-mcp to your agent, race-week research and feature scaffolding can cite live cataloged session and lap data inside the IDE.
- Registered OpenF1 MCP tools callable from agent chat
- Structured F1 session and lap answers for app and content codegen
- Repeatable npx-based local MCP wiring documented in your repo
Recommended MCP Servers
Journey fit
External sports datasets are connected during product build when agents need structured race data instead of hand-scraped pages. OpenF1 is an MCP integration layer—register it in the agent config alongside other APIs so coding sessions can query sessions, laps, and pit data on demand.
How it compares
Sports telemetry MCP integration, not a motorsport simulation game or a generic web-scraping skill.
Common Questions / FAQ
Who is OpenF1 MCP for?
Solo and indie developers who use Claude Code, Cursor, or similar agents and want OpenF1-shaped race data inside the editor.
When should I use OpenF1 MCP?
Use it during build when you are integrating F1 stats, lap charts, or weather context into an app, script, or content pipeline.
How do I add OpenF1 MCP to my agent?
Install @unclick/openf1-mcp from npm, configure an MCP stdio entry with npx as the runtime hint, and restart your agent host.