# Race Calendar F1 MCP server

Anonymous read-only Formula 1 tools, resources, prompts, completion, and interactive dashboard.

## At a glance

Race Calendar F1 is an MCP server in the Productivity category. It is hosted remotely and connects over HTTP, and declares no required credentials. It exposes 15 tools, including get_f1_season_schedule, get_f1_standings and get_f1_next_event. It scores D (33/100) on the MCP Skills Hub health score as of Oct 28, 2026.

## Install

### How to install Race Calendar F1 in Claude Code

1. Add the server

```bash
claude mcp add --transport http f1 https://racecalendar.app/mcp
```

2. Verify it's connected

```bash
claude mcp list
```

3. Sharing it with your team?

   Add `--scope project` to write it to .mcp.json in the repository root, which you can commit (with the secrets left as environment variables).

4. Use it in a session

   Ask Claude to use the tools this server exposes (e.g. get_f1_season_schedule, get_f1_standings, get_f1_next_event). It discovers them automatically.

### How to install Race Calendar F1 in Claude Desktop

1. Open your MCP config

   macOS: ~/Library/Application Support/Claude/claude_desktop_config.json · Windows: %APPDATA%\Claude\claude_desktop_config.json

2. Add this server

```json
{
  "mcpServers": {
    "f1": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://racecalendar.app/mcp"
      ]
    }
  }
}
```

3. Why the wrapper?

   This is a remote (HTTP) server and Claude Desktop only launches local processes, so mcp-remote proxies the connection. It will open a browser window if the server needs OAuth.

4. Restart Claude Desktop

   The tools appear under the 🔌 menu once the app reloads.

### How to install Race Calendar F1 in Cursor

1. Create / edit .cursor/mcp.json in your project

```json
{
  "mcpServers": {
    "f1": {
      "url": "https://racecalendar.app/mcp"
    }
  }
}
```

2. Enable it

   Cursor Settings → MCP → toggle the server on. Tools become available to the Composer/Agent.

### How to install Race Calendar F1 in Codex CLI

1. Add to ~/.codex/config.toml

```toml
[mcp_servers.f1]
command = "npx"
args = ["-y", "mcp-remote", "https://racecalendar.app/mcp"]
```

2. Why the wrapper?

   Codex runs MCP servers as local processes, so mcp-remote bridges this HTTP endpoint to stdio.

3. Run Codex

   Codex loads MCP servers from config.toml on startup and exposes their tools to the agent.

### How to install Race Calendar F1 in Windsurf

1. Edit ~/.codeium/windsurf/mcp_config.json

```json
{
  "mcpServers": {
    "f1": {
      "serverUrl": "https://racecalendar.app/mcp"
    }
  }
}
```

2. Reload

   Windsurf → Cascade → refresh MCP servers. Cascade can now call the tools.

### How to install Race Calendar F1 in Cline

1. Open Cline → MCP Servers → Configure

   Adds to cline_mcp_settings.json.

2. Add the server

```json
{
  "mcpServers": {
    "f1": {
      "type": "streamableHttp",
      "url": "https://racecalendar.app/mcp"
    }
  }
}
```

### How to install Race Calendar F1 in VS Code

1. Create .vscode/mcp.json

```json
{
  "servers": {
    "f1": {
      "type": "http",
      "url": "https://racecalendar.app/mcp"
    }
  }
}
```

2. Start it

   VS Code shows a ▶ Start action above the server entry. Agent mode (Copilot Chat) can then use the tools.

## Tools

- `get_f1_season_schedule` — Get the verified public Formula 1 schedule for a season, including UTC session times, freshness, results, and canonical links.
- `get_f1_standings` — Get the public Formula 1 driver and constructor standings for a season with canonical source links.
- `get_f1_next_event` — Find the next Formula 1 session or race weekend from a UTC timestamp, including an event already in progress.
- `get_f1_session_results` — Get the published F1DB classification for one Formula 1 session by season, meeting key, and session key, with positions and available result details.
- `get_f1_starting_grid` — Get the published F1DB starting grid for one Formula 1 session by season, meeting key, and session key; use session results for the final classification.
- `get_f1_race_weekend` — Get one public Formula 1 race weekend by season and exactly one friendly selector: meeting key, round, race name, or slug.
- `get_f1_race_classification` — Get a published F1DB race, qualifying, or sprint classification by season and a friendly race selector, without requiring meeting or session keys.
- `get_f1_circuit` — Get circuit metadata and normalized track geometry for a race weekend selected by meeting key, round, race name, or slug.
- `get_f1_race_preview` — Get a structurally spoiler-safe race-weekend briefing containing schedule and venue context but no classifications, winners, podiums, or result fields.
- `get_f1_live_session` — Get the latest explicitly timestamped status for the current or selected Formula 1 session. Returns unavailable rather than implying stale data is live.
- `get_f1_historical_race_result` — Get one complete historical Formula 1 race classification by season and championship round. Use only for a single race; for two or more races, call get_f1_historical_race_results once instead.
- `get_f1_historical_race_results` — Get 2 to 8 complete historical Formula 1 race classifications in one consolidated request, with per-race sources and bounded partial failures. Use once for multi-race questions instead of repeating get_f1_historical_race_result.
- `search_f1_history` — Search the Formula 1 history index for drivers, teams, circuits, and races with bounded, cursor-based results.
- `get_f1_updates` — Get recent public schedule, standings, and result changes after an optional timestamp or cursor.
- `compare_f1_competitors` — Compare two Formula 1 drivers or constructors in one season using sourced standings and explicitly described calculations.

---

Source: https://mcp-skills-hub.vercel.app/mcps/app-racecalendar-f1 · MCP Skills Hub · data as of 2026-10-28T12:31:05Z