cover_my_stack — OutageDeck MCP Prompt

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

by client

How to invoke cover_my_stack from your client

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

Other prompts on this server

• triage_outage

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.