MCP Servers

f1-mcp

Exposes Formula 1 historical data (race results, qualifying, pit stops, and championship standings) as callable tools for LLMs via the Jolpica-F1 API.

README

f1-mcp

An MCP server exposing Formula 1 historical data (results, qualifying, pit stops, and championship standings) as tools an LLM can call directly — built on the Jolpica-F1 API.

Tools (more to be added)

Tool	Description
`get_race_results`	Race results by season + round number
`get_race_results_by_name`	Race results by season + race/circuit name (e.g. "Monaco")
`get_qualifying_results`	Qualifying results by season + round
`get_pit_stops`	Pit stop log for a race (2011 season onward)
`get_driver_standings`	Drivers' championship standings for a season
`get_constructor_standings`	Constructors' championship standings for a season

Setup

python -m venv venv && source venv/bin/activate
pip install -r requirements.txt

Running it

Standalone, with MCP Inspector (for testing tools/prompts manually):

npx @modelcontextprotocol/inspector python src/server.py

With Claude Desktop, add to claude_desktop_config.json:

{
  "mcpServers": {
    "f1-mcp": {
      "command": "python",
      "args": ["/absolute/path/to/f1-mcp/src/server.py"]
    }
  }
}

Design notes

client.py is the only file that touches raw Jolpica JSON. Every method returns a typed schemas.py model — tool functions never parse MRData.* nesting directly.
Name-based race lookup (get_race_results_by_name) resolves a loose name ("Monaco", "Monaco GP") against the season's race calendar using substring matching first, with a fuzzy fallback (difflib) for typos — since the Ergast/ Jolpica API only supports lookup by round number.
Season schedules are cached per-session to avoid refetching the calendar on every name-based lookup.

Data source

Jolpica-F1 — free, no API key required. Historical race data from 1950 onward; pit stop data from 2011 onward.

Recommended Servers

playwright-mcp

A Model Context Protocol server that enables LLMs to interact with web pages through structured accessibility snapshots without requiring vision models or screenshots.

Official

Featured

TypeScript

Magic Component Platform (MCP)

An AI-powered tool that generates modern UI components from natural language descriptions, integrating with popular IDEs to streamline UI development workflow.

Audiense Insights MCP Server

Enables interaction with Audiense Insights accounts via the Model Context Protocol, facilitating the extraction and analysis of marketing insights and audience data including demographics, behavior, and influencer engagement.

VeyraX MCP

Single MCP tool to connect all your favorite tools: Gmail, Calendar and 40 more.

Official

Featured

Local

graphlit-mcp-server

The Model Context Protocol (MCP) Server enables integration between MCP clients and the Graphlit service. Ingest anything from Slack to Gmail to podcast feeds, in addition to web crawling, into a Graphlit project - and then retrieve relevant contents from the MCP client.

Official

Featured

TypeScript

Kagi MCP Server

An MCP server that integrates Kagi search capabilities with Claude AI, enabling Claude to perform real-time web searches when answering questions that require up-to-date information.

Official

Featured

Python

Neon Database

MCP server for interacting with Neon Management API and databases

Official

Featured

E2B

Using MCP to run code via e2b.

Official

Featured

Exa Search

A Model Context Protocol (MCP) server lets AI assistants like Claude use the Exa AI Search API for web searches. This setup allows AI models to get real-time web information in a safe and controlled way.

Official

Featured

Qdrant Server

This repository is an example of how to create a MCP server for Qdrant, a vector search engine.

Official

Featured