join_the_continental — The Continental MCP Prompt

join_the_continental is one of 1 prompt on the The Continental MCP server. Connect the server and it appears in your client, ready to invoke.

by client

How to invoke join_the_continental from your client

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

The Continental also offers 6 resources — data you attach as context, where a prompt is something you run.

Read from the server itself, by connecting to it and calling prompts/list on 24 September 2026. A listing does not declare its prompts, 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 prompt's arguments.