acknowledge_incident — Monitor Hub MCP Tool
acknowledge_incident
(acknowledge incident) 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 acknowledge_incident from your client
- Claude Code Monitor Hub acknowledge_incident run in your project directory
- Claude Desktop Monitor Hub acknowledge_incident ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Monitor Hub acknowledge_incident ~/.cursor/mcp.json
- VS Code Monitor Hub acknowledge_incident .vscode/mcp.json
- Zed Monitor Hub acknowledge_incident ~/.config/zed/settings.json
- Windsurf Monitor Hub acknowledge_incident ~/.codeium/windsurf/mcp_config.json
- Cline Monitor Hub acknowledge_incident ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Monitor Hub acknowledge_incident ~/.gemini/settings.json
- Grok Monitor Hub acknowledge_incident .mcp.json (in your project root)
- ChatGPT Monitor Hub acknowledge_incident Settings → Connectors → Advanced → Developer mode
- Claude.ai Monitor Hub acknowledge_incident Settings → Connectors → Add custom connector
- LangChain Monitor Hub acknowledge_incident 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
- get_incident_details
- 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.