explain_mission_matchup — Praetorium MCP Prompt

explain_mission_matchup is one of 2 prompts on the Praetorium MCP server. Connect the server and it appears in your client, ready to invoke.

by client

How to invoke explain_mission_matchup from your client

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

Other prompts on this server

• answer_rules_question

Praetorium also offers 2 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 29 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.