F1 race-weekend dashboard — Race Calendar F1 MCP Resource

F1 race-weekend dashboard is one of 2 resources on the Race Calendar F1 MCP server. Connect the server and your client can attach it as context.

by client

How to attach F1 race-weekend dashboard from your client

• Claude Code Race Calendar F1 Resource/F1 race-weekend dashboard run in your project directory
• Claude Desktop Race Calendar F1 Resource/F1 race-weekend dashboard ~/Library/Application Support/Claude/claude_desktop_config.json
• Cursor Race Calendar F1 Resource/F1 race-weekend dashboard ~/.cursor/mcp.json
• VS Code Race Calendar F1 Resource/F1 race-weekend dashboard .vscode/mcp.json
• Zed Race Calendar F1 Resource/F1 race-weekend dashboard ~/.config/zed/settings.json
• Windsurf Race Calendar F1 Resource/F1 race-weekend dashboard ~/.codeium/windsurf/mcp_config.json
• Cline Race Calendar F1 Resource/F1 race-weekend dashboard ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
• Gemini CLI Race Calendar F1 Resource/F1 race-weekend dashboard ~/.gemini/settings.json
• Grok Race Calendar F1 Resource/F1 race-weekend dashboard .mcp.json (in your project root)
• ChatGPT Race Calendar F1 Resource/F1 race-weekend dashboard Settings → Connectors → Advanced → Developer mode
• Claude.ai Race Calendar F1 Resource/F1 race-weekend dashboard Settings → Connectors → Add custom connector
• LangChain Race Calendar F1 Resource/F1 race-weekend dashboard pip install langchain-mcp-adapters

Other resources on this server

• f1-latest-updates

Race Calendar F1 also offers 5 prompts — things you invoke, where a resource is context you attach.

Read from the server itself, by connecting to it and calling resources/list on 24 September 2026. A listing does not declare its resources, so asking is the only way to know them, and this is what the server actually offers rather than what its listing claims. Names only are stored; connect the server for each resource's type and contents.