ProductivityMCP Registryremote15 toolsD · 33

Race Calendar F1 MCP server

Name: Race Calendar F1
Author: racecalendar.app

app.racecalendar · Updated 2mo ago

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.

Source

One-click install

VS Code VS Code Insiders Cursor

Opens your editor and pre-fills the config. Your editor will ask before adding it.

How to install Race Calendar F1 in your AI client

Setup for Claude Code, Claude Desktop, Cursor, Codex, Windsurf, Cline and VS Code — copy-paste ready.

How to install Race Calendar F1 in Claude CodeAnthropic's agentic CLI

Add the server

bash

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

2
Verify it's connected
bash
```
claude mcp list
```
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).
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 DesktopDesktop app (MCP config)

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

Add this server

json

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

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.
Restart Claude Desktop
The tools appear under the 🔌 menu once the app reloads.

How to install Race Calendar F1 in CursorAI-first code editor

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

json

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

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

How to install Race Calendar F1 in Codex CLIOpenAI coding agent

Add to ~/.codex/config.toml

toml

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

Why the wrapper?
Codex runs MCP servers as local processes, so mcp-remote bridges this HTTP endpoint to stdio.
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 WindsurfCodeium's agentic IDE

Edit ~/.codeium/windsurf/mcp_config.json

json

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

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

How to install Race Calendar F1 in ClineVS Code autonomous agent

Open Cline → MCP Servers → Configure
Adds to cline_mcp_settings.json.

Add the server

json

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

How to install Race Calendar F1 in VS CodeCopilot / MCP support

Create .vscode/mcp.json

json

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

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

What tools does Race Calendar F1 expose? (15)

Read from the live server. Click any tool for its input schema.

get_f1_season_scheduleGet the verified public Formula 1 schedule for a season, including UTC session times, freshness, results, and canonical links.
get_f1_standingsGet the public Formula 1 driver and constructor standings for a season with canonical source links.
get_f1_next_eventFind the next Formula 1 session or race weekend from a UTC timestamp, including an event already in progress.
get_f1_session_resultsGet 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_gridGet 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_weekendGet one public Formula 1 race weekend by season and exactly one friendly selector: meeting key, round, race name, or slug.
get_f1_race_classificationGet a published F1DB race, qualifying, or sprint classification by season and a friendly race selector, without requiring meeting or session keys.
get_f1_circuitGet circuit metadata and normalized track geometry for a race weekend selected by meeting key, round, race name, or slug.
get_f1_race_previewGet a structurally spoiler-safe race-weekend briefing containing schedule and venue context but no classifications, winners, podiums, or result fields.
get_f1_live_sessionGet 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_resultGet 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_resultsGet 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_historySearch the Formula 1 history index for drivers, teams, circuits, and races with bounded, cursor-based results.
get_f1_updatesGet recent public schedule, standings, and result changes after an optional timestamp or cursor.
compare_f1_competitorsCompare two Formula 1 drivers or constructors in one season using sourced standings and explicitly described calculations.

What the code can do

This is a remote server — nothing is installed or run on your machine, so there is no local code to analyze. What it can reach is described above: your requests go to the provider's host.

Before you install

Signals gathered from the source repo and package registry — not a safety verdict.

What it can reach

Third-party hosted service — Your requests and any data in them are sent to racecalendar.app.
No local execution — Nothing is installed or run on your machine.

No source repository — This registry entry does not link to a public repo, so its code cannot be reviewed before you install it.

Client compatibility

Claude Code: NativeClaude Desktop: Via mcp-remoteCursor: NativeCodex CLI: Via mcp-remoteWindsurf: NativeCline: NativeVS Code: Native

Health score

D · 33

Maintenance, adoption, transparency and packaging — not a safety audit. How this is calculated

Maintenance30%not measurable
No commit history available.
Adoption20%not measurable
No usage data available.
Transparency20%25%
1/4: ✗ public source repo, ✗ declared license, ✗ documentation, ✓ discoverable tool list.
Provenance15%0%
No source repository to trace the code back to.
Packaging15%75%
Remote endpoint; authentication requirements not declared.

Alternatives to Race Calendar F1

Maintain Race Calendar F1? Add a badge to your README

Shows its health grade, and links readers to install steps for every client.

markdown

[![Race Calendar F1 on MCP Skills Hub](https://mcp-skills-hub.vercel.app/badge/app-racecalendar-f1)](https://mcp-skills-hub.vercel.app/mcps/app-racecalendar-f1)

Catalog data refreshed Oct 28, 2026. Something wrong? Report it.