get_incident_details — Monitor Hub MCP Tool Read-only
get_incident_details
(get incident details) is one of 25 tools on the
Monitor Hub
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 Monitor Hub get_incident_details run in your project directory
- Claude Desktop Monitor Hub get_incident_details ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Monitor Hub get_incident_details ~/.cursor/mcp.json
- VS Code Monitor Hub get_incident_details .vscode/mcp.json
- Zed Monitor Hub get_incident_details ~/.config/zed/settings.json
- Windsurf Monitor Hub get_incident_details ~/.codeium/windsurf/mcp_config.json
- Cline Monitor Hub get_incident_details ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Monitor Hub get_incident_details ~/.gemini/settings.json
- Grok Monitor Hub get_incident_details .mcp.json (in your project root)
- ChatGPT Monitor Hub get_incident_details Settings → Connectors → Advanced → Developer mode
- Claude.ai Monitor Hub get_incident_details Settings → Connectors → Add custom connector
- LangChain Monitor Hub get_incident_details pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http monitorhub https://mcp.monitorhubs.com/mcpOther tools on this server
- list_monitors
- get_monitor_details
- read_monitor_status
- read_server_status
- get_server_metrics
- read_incidents
- read_uptime_statistics
- read_alerts
- list_status_pages
- search_monitors
- list_recent_outages
- list_notification_channels
- create_monitor
- update_monitor
- pause_monitor
- resume_monitor
- delete_monitor
- test_endpoint
- resolve_server_warning
- acknowledge_incident
- resolve_incident
- trigger_test_alert
- update_status_page
- get_monitor_history
This list was read from the server itself, by connecting to it and calling tools/list on 14 November 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.