compare_f1_competitors — Race Calendar F1 MCP Tool
compare_f1_competitors
(compare f1 competitors) is one of 15 tools on the
Race Calendar F1
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call compare_f1_competitors from your client
- Claude Code Race Calendar F1 compare_f1_competitors run in your project directory
- Claude Desktop Race Calendar F1 compare_f1_competitors ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Race Calendar F1 compare_f1_competitors ~/.cursor/mcp.json
- VS Code Race Calendar F1 compare_f1_competitors .vscode/mcp.json
- Zed Race Calendar F1 compare_f1_competitors ~/.config/zed/settings.json
- Windsurf Race Calendar F1 compare_f1_competitors ~/.codeium/windsurf/mcp_config.json
- Cline Race Calendar F1 compare_f1_competitors ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Race Calendar F1 compare_f1_competitors ~/.gemini/settings.json
- Grok Race Calendar F1 compare_f1_competitors .mcp.json (in your project root)
- ChatGPT Race Calendar F1 compare_f1_competitors Settings → Connectors → Advanced → Developer mode
- Claude.ai Race Calendar F1 compare_f1_competitors Settings → Connectors → Add custom connector
- LangChain Race Calendar F1 compare_f1_competitors pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http f1 https://racecalendar.app/mcpOther tools on this server
This list was read from the server itself, by connecting to it and calling tools/list on 24 September 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.