get_f1_race_weekend — Race Calendar F1 MCP Tool Read-only
get_f1_race_weekend
(get f1 race weekend) 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 get_f1_race_weekend from your client
- Claude Code Race Calendar F1 get_f1_race_weekend run in your project directory
- Claude Desktop Race Calendar F1 get_f1_race_weekend ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Race Calendar F1 get_f1_race_weekend ~/.cursor/mcp.json
- VS Code Race Calendar F1 get_f1_race_weekend .vscode/mcp.json
- Zed Race Calendar F1 get_f1_race_weekend ~/.config/zed/settings.json
- Windsurf Race Calendar F1 get_f1_race_weekend ~/.codeium/windsurf/mcp_config.json
- Cline Race Calendar F1 get_f1_race_weekend ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Race Calendar F1 get_f1_race_weekend ~/.gemini/settings.json
- Grok Race Calendar F1 get_f1_race_weekend .mcp.json (in your project root)
- ChatGPT Race Calendar F1 get_f1_race_weekend Settings → Connectors → Advanced → Developer mode
- Claude.ai Race Calendar F1 get_f1_race_weekend Settings → Connectors → Add custom connector
- LangChain Race Calendar F1 get_f1_race_weekend pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http f1 https://racecalendar.app/mcp
Other tools on this server
- get_f1_season_schedule
- get_f1_standings
- get_f1_next_event
- get_f1_session_results
- get_f1_starting_grid
- get_f1_race_classification
- get_f1_circuit
- get_f1_race_preview
- get_f1_live_session
- get_f1_historical_race_result
- get_f1_historical_race_results
- search_f1_history
- get_f1_updates
- compare_f1_competitors
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.