3 #incident-response MCP Servers & Clients
Every MCP server and client below is tagged #incident-response — install one to give Claude, Cursor, VS Code, or any other MCP-compatible client access to incident-response tools.
All
DebugBundle
debugbundle
DebugBundle turns runtime failures, critical-path issues, and availability checks into incidents with full context, alerts, remote probes, and deterministic debug bundles for humans and AI agents.
Cirdan
adanb13
Cirdan maps and watches the live infrastructure your agent session can reach — Docker, Kubernetes, cloud, IaC, and telemetry — then exposes it over MCP. It fingerprints the environment, builds a dependency graph, detects incidents, and can run evidence-backed actions. It inherits
Shellguard
jonchun
ShellGuard is an MCP server that lets LLM agents securely SSH into remote Linux hosts with read-only shell access. Instead of copy-pasting terminal output, your AI can run safe diagnostics, inspect logs, query systems, and troubleshoot production, staging, or dev environments aut
Frequently asked questions
What is a #incident-response MCP server?
- An MCP server tagged #incident-response implements the Model Context Protocol so AI assistants like Claude, Cursor, and VS Code can access incident-response-related tools, data, or APIs.
How many #incident-response MCP servers and clients are there?
- mcp.so currently lists 3 MCP servers and clients tagged #incident-response.
How do I install a #incident-response MCP server?
- Open any server below and copy its install snippet into Claude Desktop, Cursor, VS Code, or another MCP client's configuration — remote servers need no separate download.