Menyediakan data real-time, historis, dan berita Formula 1 melalui 11 tool khusus untuk klien AI.
Juga dikenal sebagai praneethravuri/pitstop, pitstop-f1
- Stars
- 1
- Tools
- 11
- Unduhan, 30 hari
- 65
- Versi terbaru
- 0.5.0
- Commit terakhir
- 14 Nov 2026
- Lisensi
- MIT
Apa itu Pitstop MCP?
Menyediakan data real-time, historis, dan berita Formula 1 melalui 11 tool khusus untuk klien AI. Server ini menyediakan 11 tool, seperti get_session_data, get_telemetry_data, get_live_data.
Ringkasan dibuat dari README proyek
Tentang Pitstop MCP server
Pitstop memungkinkan Anda menganalisis telemetri Formula 1, hasil balapan, dan berita langsung dari dalam klien AI. MCP server ini mengagregasi data dari berbagai sumber otoritatif seperti FastF1, OpenF1, dan Wikidata untuk menyediakan 11 tool khusus bagi penggemar balap dan developer. Cakupannya meliputi segalanya, mulai dari live intervals dan pit stops secara real-time hingga klasemen kejuaraan historis sejak tahun 1950.
Pengguna dapat men-deploy server ini melalui hosted HTTP endpoint di Hugging Face atau menginstalnya secara lokal menggunakan stdio melalui uvx. Server ini mendukung berbagai environment termasuk Claude Desktop, Cursor, Windsurf, dan VS Code. Bagi Anda yang membutuhkan setup lokal lengkap, server ini dapat dijalankan via Docker untuk menyertakan database SQLite internal. Server ini mengelola tugas kompleks seperti pagination, retries, dan concurrency limits secara otomatis untuk memastikan pengambilan data yang andal.
Apa yang bisa Anda lakukan dengannya
- 1Analisis performa driverMinta analisis mendalam mengenai pace driver, degradasi ban, dan konsistensi stint selama Grand Prix tertentu.
- 2Monitor data balapan livePantau interval balapan real-time, pit stops, dan update team radio selama sesi balapan berlangsung.
- 3Ambil telemetri historisPeriksa telemetri mobil lap-per-lap termasuk kecepatan, throttle, dan perubahan gear untuk driver tertentu.
- 4Query fakta biografisGunakan query SPARQL untuk menemukan informasi biografis spesifik atau rekor karier driver Formula 1.
Ditulis berdasarkan README proyek. Setiap use case diperiksa terhadap kutipan dari README tersebut.
Cara menginstal Pitstop MCP
Format diverifikasi 10 Nov 2026Tambahkan ke CursorTambahkan ke GooseInstal Pitstop MCP di Claude Code
$ claude mcp add --env 'PITSTOP_TRANSPORT=<PITSTOP_TRANSPORT>' pitstop -- uvx pitstop-f1Instal Pitstop MCP di Cursor
~/.cursor/mcp.json
{
"mcpServers": {
"pitstop": {
"command": "uvx",
"args": [
"pitstop-f1"
],
"env": {
"PITSTOP_TRANSPORT": "<PITSTOP_TRANSPORT>"
}
}
}
}Instal Pitstop MCP di VS Code
.vscode/mcp.json
{
"servers": {
"pitstop": {
"type": "stdio",
"command": "uvx",
"args": [
"pitstop-f1"
],
"env": {
"PITSTOP_TRANSPORT": "<PITSTOP_TRANSPORT>"
}
}
}
}Instal Pitstop MCP di VS Code CLI
$ code --add-mcp '{"name":"pitstop","type":"stdio","command":"uvx","args":["pitstop-f1"],"env":{"PITSTOP_TRANSPORT":"<PITSTOP_TRANSPORT>"}}'Instal Pitstop MCP di Claude Desktop
claude_desktop_config.json
{
"mcpServers": {
"pitstop": {
"command": "uvx",
"args": [
"pitstop-f1"
],
"env": {
"PITSTOP_TRANSPORT": "<PITSTOP_TRANSPORT>"
}
}
}
}Instal Pitstop MCP di Codex
$ codex mcp add pitstop --env 'PITSTOP_TRANSPORT=<PITSTOP_TRANSPORT>' -- uvx pitstop-f1Instal Pitstop MCP di Codex config.toml
~/.codex/config.toml
[mcp_servers.pitstop] command = "uvx" args = ["pitstop-f1"] [mcp_servers.pitstop.env] PITSTOP_TRANSPORT = "<PITSTOP_TRANSPORT>"
Instal Pitstop MCP di Gemini CLI
$ gemini mcp add -s user -e 'PITSTOP_TRANSPORT=<PITSTOP_TRANSPORT>' pitstop uvx -- pitstop-f1Instal Pitstop MCP di Gemini settings.json
~/.gemini/settings.json
{
"mcpServers": {
"pitstop": {
"command": "uvx",
"args": [
"pitstop-f1"
],
"env": {
"PITSTOP_TRANSPORT": "<PITSTOP_TRANSPORT>"
}
}
}
}Tool Pitstop MCP 11
Terdeteksi dari READMEget_session_dataget_telemetry_dataget_live_dataget_standingsget_scheduleget_reference_dataget_f1_newsget_resultsget_race_analysisquery_wikidataquery_f1_database
| get_session_data | — | |
| get_telemetry_data | — | |
| get_live_data | — | |
| get_standings | — | |
| get_schedule | — | |
| get_reference_data | — | |
| get_f1_news | — | |
| get_results | — | |
| get_race_analysis | — | |
| query_wikidata | — | |
| query_f1_database | — |
Konfigurasi
PITSTOP_TRANSPORTWajibTransport mode; must be 'stdio' when run via an MCP client.
| Nama | Deskripsi | Tipe |
|---|---|---|
| PITSTOP_TRANSPORT | Transport mode; must be 'stdio' when run via an MCP client. | Wajib |
Pengecekan otomatis
Berjalan 12 Nov 2026Laporan lengkap →Lolos checks otomatis kami. Ini bukan audit keamanan: baca kodenya dan berikan server akses paling terbatas yang dibutuhkannya. Cara kerja checks
- Source repository terhubung dan dapat dijangkauLolos
- Lisensi open source (OSI)Lolos
- Ada commit atau release dalam satu tahun terakhirLolos
- Nama package tidak mirip dengan package populerLolos
- Remote endpoint menggunakan HTTPSTidak diperiksa
- Tools yang bersifat destruktif telah diberi labelLolos
- Tidak ada instruksi tersembunyi untuk modelLolos
- Tidak ada advisory kritis pada paket atau dependensinyaLolos
README
Lihat di GitHubPitstop — F1 MCP Server
An HTTP-first Model Context Protocol (MCP) server for Formula 1 data. Aggregates real-time, historical, and news data from multiple authoritative sources into 11 tools ready for any MCP client.
v0.5.0 | Author: Praneeth Ravuri
Install
Hosted endpoint (nothing to install)
A free public instance runs on Hugging Face Spaces:
https://praneeth1025-pitstop.hf.space/mcp
claude mcp add --transport http pitstop https://praneeth1025-pitstop.hf.space/mcp
Note: the Space sleeps after long inactivity — the first request after a quiet spell takes a cold start.
Local install
stdio, via uvx (no clone needed):
PITSTOP_TRANSPORT=stdio uvx pitstop-f1
claude mcp add pitstop -e PITSTOP_TRANSPORT=stdio -- uvx pitstop-f1
codex mcp add pitstop --env PITSTOP_TRANSPORT=stdio -- uvx pitstop-f1
gemini mcp add pitstop uvx pitstop-f1 --env PITSTOP_TRANSPORT=stdio
VS Code:
code --add-mcp '{"name":"pitstop","command":"uvx","args":["pitstop-f1"],"env":{"PITSTOP_TRANSPORT":"stdio"}}'
Claude Desktop (claude_desktop_config.json), Cursor (~/.cursor/mcp.json), and Windsurf (~/.codeium/windsurf/mcp_config.json) share the same JSON shape:
{
"mcpServers": {
"pitstop": {
"command": "uvx",
"args": ["pitstop-f1"],
"env": { "PITSTOP_TRANSPORT": "stdio" }
}
}
}
Docker (HTTP transport, runs the full server incl. the F1 database):
docker compose up
# → http://localhost:8000/mcp
Overview
Pitstop exposes F1 data as 11 MCP tools over HTTP (default) or stdio. It pulls from FastF1, Jolpica, OpenF1, Wikidata, RSS feeds, and its own seeded F1 database, handling pagination, retries, caching, and concurrency limits transparently.
Data Sources
| Source | Coverage | Type |
|---|---|---|
| FastF1 | 2018–present | Historical / timing / telemetry |
| Jolpica-F1 | 1950–present | Historical (Ergast-compatible) |
| OpenF1 | 2023–present | Real-time |
| Wikidata | All eras | SPARQL queries |
| RSS Feeds (20 sources) | Live | News |
| Pitstop F1 Database | 1950–present | Owned sqlite (seeded from F1DB, self-updated weekly from Jolpica) + per-lap times |
Database refresh: .github/workflows/db-update.yml runs weekly to pull new Jolpica results into the owned F1 database.
Tools
| Tool | Description | Key Parameters |
|---|---|---|
get_session_data |
Race/qualifying results, lap times, weather, driver details (2018–present) | year, gp, session, includes, page, page_size |
get_telemetry_data |
Lap-by-lap car telemetry (speed, throttle, brake, gears) (2018–present) | year, gp, session, drivers, lap_numbers, max_points, page, page_size |
get_live_data |
Live intervals, pit stops, team radio, stints, race control, weather, position, laps, overtakes (2023–present) | data_types, year, country, session_name, driver_number, compound, flag, category, page, page_size |
get_standings |
Driver and constructor championship standings (1950–present) | year, round, type, driver_name, team_name, page, page_size |
get_schedule |
Race calendar and session schedule | year, include_testing, round, event_name, only_remaining, page, page_size |
get_reference_data |
Circuits, drivers, constructors encyclopedia (1950–present) | reference_type, year, name, page, page_size |
get_f1_news |
F1 headlines from 20 RSS sources | source, limit, keywords, driver, team, circuit, year, date_from, date_to, page, page_size |
get_results |
Race/qualifying/sprint results, lap times, pit stops (1950–present) | year, round, result_type, driver, page |
get_race_analysis |
Pace, tire degradation, stint summaries, consistency (2018–present) | year, gp, session, drivers, analysis_type, page |
query_wikidata |
SPARQL queries to Wikidata for F1 biography, career records, history | sparql, page, page_size |
query_f1_database |
Read-only SQL over pitstop's owned F1 database (1950–present): results, standings, driver family trees, team lineage | sql, page, page_size |
Transport
HTTP (default)
uv sync
uv run pitstop
# → http://localhost:8000
MCP client config:
{
"mcpServers": {
"pitstop": {
"type": "http",
"url": "http://localhost:8000/mcp"
}
}
}
stdio (opt-in)
PITSTOP_TRANSPORT=stdio uv run pitstop
MCP client config:
{
"mcpServers": {
"pitstop": {
"command": "uv",
"args": ["run", "--directory", "/path/to/pitstop", "pitstop"],
"env": { "PITSTOP_TRANSPORT": "stdio" }
}
}
}
Health API
| Endpoint | Purpose |
|---|---|
GET /health |
Per-source status (FastF1, f1db, Jolpica, OpenF1, RSS) |
GET /live |
Liveness probe |
GET /ready |
Readiness probe |
Example /health response:
{
"version": "0.5.0",
"overall": "ok",
"sources": [
{ "name": "fastf1", "status": "ok", "latency_ms": 2, "detail": "cache writable" },
{ "name": "f1db", "status": "ok", "latency_ms": 1, "detail": "" },
{ "name": "jolpica", "status": "ok", "latency_ms": 134, "detail": "" },
{ "name": "openf1", "status": "ok", "latency_ms": 98, "detail": "" },
{ "name": "rss", "status": "ok", "latency_ms": 210, "detail": "" }
]
}
overall is "ok" / "degraded" / "down". HTTP 200 / 207 / 503.
Wikidata SPARQL
query_wikidata runs SPARQL queries against Wikidata for biographical and historical F1 facts not covered by race APIs.
Only SELECT and ASK queries are accepted (read-only). Always include LIMIT in your query.
Example — find F1 drivers with their birthdate:
SELECT ?driver ?driverLabel ?birthDate WHERE {
?driver wdt:P31 wd:Q5 ;
wdt:P641 wd:Q1968 ;
wdt:P569 ?birthDate .
SERVICE wikibase:label { bd:serviceParam wikibase:language "en" }
} ORDER BY DESC(?birthDate) LIMIT 10
Pagination
All list-returning tools accept page (1-based, default 1) and page_size (defaults vary per tool: 10–50). Responses include a pagination block:
{
"data": [...],
"pagination": {
"page": 1,
"page_size": 20,
"total_items": 47,
"total_pages": 3,
"has_next": true,
"has_prev": false
}
}
Configuration
| Variable | Default | Description |
|---|---|---|
PITSTOP_TRANSPORT |
http |
http or stdio |
PITSTOP_HOST |
0.0.0.0 |
Bind address (HTTP only) |
PITSTOP_PORT |
8000 |
Listen port (HTTP only) |
PITSTOP_ENV |
development |
development or production |
PITSTOP_LOG_LEVEL |
Depends on PITSTOP_ENV |
DEBUG if development, else INFO |
PITSTOP_LOG_FORMAT |
Depends on PITSTOP_ENV |
text if development, else json |
PITSTOP_ENABLE_CACHING |
true |
Enable HTTP response and FastF1 disk caching |
PITSTOP_CACHE_TTL_SECONDS |
300 |
HTTP response cache time-to-live (seconds) |
PITSTOP_RATE_LIMIT_ENABLED |
false |
Enable concurrent-call limiting |
PITSTOP_RATE_LIMIT_PER_HOUR |
3600 |
Max concurrent calls (derived from per-hour quota) |
FASTF1_CACHE |
cache |
FastF1 cache directory path |
Caching
Pitstop uses in-memory HTTP response caching (via Hishel) for GET requests with 200 responses. This keeps tool calls inside upstream rate limits:
- Jolpica: 4 req/s, 500/hr
- OpenF1: 3 req/s, 30/min
- Wikidata: Query complexity limits
- RSS: Per-feed redirects cached
FastF1 maintains its own disk cache in FASTF1_CACHE directory. Control caching via:
PITSTOP_ENABLE_CACHING=true(default)PITSTOP_CACHE_TTL_SECONDS=300(default)
Development
uv sync --dev
uv run pytest
uv run ruff check src/
Contributing
See CONTRIBUTING.md.
Credits & attribution
| Source | Description | License |
|---|---|---|
| F1DB | Database seeded from F1DB and subsequently modified & extended by pitstop | CC BY 4.0 |
| FastF1 | Python library for F1 timing, telemetry, and session data | MIT |
| Jolpica-F1 | Ergast-compatible F1 data API, 1950–present; also used to self-update the F1DB-seeded database weekly | — |
| OpenF1 | Free open-source API for real-time F1 data | MIT |
| Wikidata | Open knowledge graph with SPARQL query service | CC0 |
| Ergast Motor Racing API | Historical F1 data 1950–2024 (now served via Jolpica) | — |
| RSS Feeds (20 sources) | News headlines, credited collectively; see each feed's link field in get_f1_news results |
Respective publishers |
Not affiliated with Formula 1 or the FIA. Data provided by third-party sources under their respective terms.
Pertanyaan tentang Pitstop MCP
Bagaimana cara menambahkan Pitstop MCP ke Claude Code?
Jalankan claude mcp add --env 'PITSTOP_TRANSPORT=<PITSTOP_TRANSPORT>' pitstop -- uvx pitstop-f1 di terminal Anda. Tambahkan --scope user agar tersedia di semua proyek.
Bagaimana cara menambahkan Pitstop MCP ke Cursor?
Buka ~/.cursor/mcp.json dan tambahkan server di bawah mcpServers, menggunakan config Cursor yang ditunjukkan di bagian instalasi di atas.
Tool apa yang disediakan Pitstop MCP?
Server ini menyediakan 11 tool, termasuk get_session_data, get_telemetry_data, get_live_data, get_standings, get_schedule.
Bagaimana cara install Pitstop secara lokal?
Anda dapat menginstalnya via stdio menggunakan uvx dengan menjalankan PITSTOP_TRANSPORT=stdio uvx pitstop-f1.
Apakah Pitstop menyediakan data real-time?
Ya, ini mencakup live intervals, pit stops, team radio, dan data race control melalui tool get_live_data.
Bisakah saya menjalankan query SPARQL untuk sejarah F1?
Ya, tool query_wikidata memungkinkan Anda menjalankan query SELECT dan ASK SPARQL read-only terhadap Wikidata untuk fakta biografis dan historis.