get_incident_details — OutageDeck MCP Tool Read-only
get_incident_details
(get incident details) is one of 14 tools on the
OutageDeck
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call get_incident_details from your client
- Claude Code OutageDeck get_incident_details run in your project directory
- Claude Desktop OutageDeck get_incident_details ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor OutageDeck get_incident_details ~/.cursor/mcp.json
- VS Code OutageDeck get_incident_details .vscode/mcp.json
- Zed OutageDeck get_incident_details ~/.config/zed/settings.json
- Windsurf OutageDeck get_incident_details ~/.codeium/windsurf/mcp_config.json
- Cline OutageDeck get_incident_details ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI OutageDeck get_incident_details ~/.gemini/settings.json
- Grok OutageDeck get_incident_details .mcp.json (in your project root)
- ChatGPT OutageDeck get_incident_details Settings → Connectors → Advanced → Developer mode
- Claude.ai OutageDeck get_incident_details Settings → Connectors → Add custom connector
- LangChain OutageDeck get_incident_details pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http outagedeck-status https://outagedeck.com/api/mcpOther tools on this server
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.