Pitstop
Pitstop is a comprehensive Formula 1 data server providing access to historical (1950+) and detailed modern (2018+) F1 information through 25 specialized tools.
Core Capabilities:
Session Analysis - Access complete session details, results, classifications, driver lists, fastest laps, statistics, and time-series weather data for any F1 session (FP1/2/3, Qualifying, Sprint, Race)
Lap Data & Strategy - Retrieve lap-by-lap information including sector times, speeds, pit stops, track status, and perform tire strategy analysis showing compound usage, tire life, and stint information
Telemetry & Performance - Get high-frequency telemetry data (speed, throttle, brake, gear, RPM, DRS) for specific laps or compare side-by-side between two drivers for detailed performance analysis
Race Control - Retrieve official race control messages including flags, penalties, investigations, safety car deployments, and track status changes
Live Timing - Access real-time data including driver radio transcripts, pit stop timing, and interval/gap data via OpenF1 API
Championship Standings - Get driver and constructor standings from 1950 onwards, filterable by year, round, or specific driver/team
News Aggregation - Access latest F1 news from 25+ sources (official F1, FIA, Autosport, Motorsport, The Race), filterable by category (driver transfers, technical developments, regulations), source, keywords, and date ranges
Reference Data - Access driver information, team details, and circuit layouts
Flexible Filtering - Filter data by year, Grand Prix, session type, driver, team, and various other parameters
Data Sources: FastF1 (2018+), OpenF1 API (2023+), Ergast API (1950-2024), and RSS feeds from 25+ news sources. Includes production-ready features like caching, logging, health checks, and rate limiting.
Planned integration for accessing F1 news and headlines through RSS feeds
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Pitstopshow me the current driver championship standings"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
🏎️ Pitstop: The All-in-One F1 MCP Server
Pitstop is a comprehensive Model Context Protocol (MCP) server for Formula 1 data. It aggregates data from multiple authoritative sources to answer any F1-related question, from historical stats to real-time race telemetry.
🌟 Capabilities
Pitstop consolidates specialized functions into 7 powerful tools:
get_live_data: Real-time access to telemetry, pit stops, team radio, race control messages, and intervals.get_session_data: Comprehensive session analysis including results, weather, fastest laps, and driver details.get_telemetry_data: Deep dive into car performance with lap-by-lap telemetry (speed, throttle, brake, gears).get_reference_data: Static encyclopedia for drivers, teams, circuits, and tire compounds.get_standings: Current and historical championship standings.get_schedule: Full calendar awareness including testing and future races.get_f1_news: Latest headlines from 25+ trusted global sources.
🔌 Data Sources
OpenF1 API: Real-time timing & telemetry (2023-Present)
FastF1 / Ergast: Historical data & deep analysis (1950-Present)
RSS Feeds: Aggregated news from official and major media outlets.
🚀 Installation & Usage
Prerequisites
Python 3.13+
uv(recommended) orpip
1. Install via Smithery (Recommended)
To install Pitstop for Claude Desktop automatically:
npx -y @smithery/cli install pitstop --client claude2. Manual Installation
Clone the repository and install dependencies:
git clone https://github.com/praneethravuri/pitstop.git
cd pitstop
uv sync3. Running the Server
Run the MCP server directly using uv:
uv run pitstop4. Docker Deployment
To run with Docker Compose:
5. Client Configuration
To use Pitstop with MCP clients like Antigravity, Claude Desktop, or Claude Code, add the following to your configuration file (e.g., claude_desktop_config.json or mcp.json).
Option A: Docker (Recommended)
{
"mcpServers": {
"pitstop": {
"command": "docker",
"args": ["run", "-i", "--rm", "pitstop"],
"env": {
"PITSTOP_ENV": "production"
}
}
}
}Option B: Local (uv)
{
"mcpServers": {
"pitstop": {
"command": "uv",
"args": [
"run",
"--directory",
"/absolute/path/to/pitstop",
"pitstop"
],
"env": {
"PITSTOP_ENV": "production"
}
}
}
}Note: Replace
/absolute/path/to/pitstopwith the actual path to your cloned repository.
Or manually using python:
# Add src to PYTHONPATH if running manually
export PYTHONPATH=$PYTHONPATH:$(pwd)/src
python -m pitstop🛠️ Tool Usage Guide
Tool | Purpose | Example Query |
| Live race monitoring | "Check the gap between VER and HAM", "Any specialized pit stops?" |
| Post-session analysis | "Get full results for Monaco 2024", "What was the weather during Q3?" |
| Championship tracker | "Who is leading the constructor standings?", "2021 driver points" |
| Calendar & Events | "When is the next race?", "Monaco GP start times" |
| Encyclopedia | "How many corners does Spa have?", "Max Verstappen stats" |
| News Aggregator | "Latest Ferrari news", "Updates on Newey" |
| Deep Tech Analysis | "Compare telemetry for VER and LEC in Q3" |
📦 Project Structure
src/
pitstop/
__main__.py # Entry point
clients/ # API Clients (OpenF1, FastF1, RSS)
models/ # Pydantic Data Models
tools/ # Tool Implementations
live/ # Live Data Tools
general/ # Session & Telemetry
reference/ # Static Data
...📜 License
MIT License. Data provided by FastF1, OpenF1, and Ergast. Not affiliated with Formula 1 or FIA.
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Latest Blog Posts
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/praneethravuri/pitstop'
If you have feedback or need assistance with the MCP directory API, please join our Discord server