A
licenseNot graded
qualityD
maintenanceA multi-agent MCP server that turns LLMs into an autonomous incident-response copilot, enabling rapid investigation, correlation, and remediation of production incidents.
MIT
incident-commander-mcp
by hashirR786
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@incident-commander-mcpInvestigate the error spike in payment-service around 14:03 UTC"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
incident-commander-mcp
AI-powered incident management MCP server built for the NitroStack Hackathon.
⚠️ R12 Disclosure — Simulated Integrations
All data returned by this MCP server is entirely mocked and stored in-memory.
There are NO real connections to:
Kubernetes / container orchestration platforms
Grafana / Prometheus / any metrics backend
GitHub / GitLab / any version control system
PagerDuty / OpsGenie / any alerting system
Stripe or any payment processor
This is a demo for hackathon evaluation purposes. The realistic-looking data is seeded with a purposeful incident scenario (deploy at 14:02 → error spike at 14:03) to demonstrate agent reasoning capabilities over MCP tools, resources, and prompts.
Related MCP server: mttrly
Overview
incident-commander-mcp is a single MCP server built on the NitroStack TypeScript framework
(@nitrostack/core). It exposes tools, resources, and prompts that enable an AI agent to:
Investigate production incidents by querying deployment history, error logs, and metrics
Reason about root causes using cross-correlated data
Act (with human approval) by requesting rollbacks or creating incident tickets
Document incidents via structured postmortem prompts
Capabilities
🔧 Tools (8)
Tool | Description | Annotation |
| Recent deployments, optionally filtered by service |
|
| Error logs for a service within a time window |
|
| Latency, error rate, CPU/memory time-series |
|
| Kubernetes pod readiness and restart counts |
|
| Cross-correlates deploy + logs + metrics → hypothesis |
|
| Submits a rollback request (requires human approval) |
|
| Creates a new in-memory incident record | — |
| Appends a timeline entry to an incident | — |
📦 Resources (4)
URI | Description |
| Active incident snapshot (JSON) |
| Timeline for a specific incident |
| Last 20 deployments across all services |
| Health snapshot for one service |
💬 Prompts (3)
Prompt | Arguments | Description |
|
| Guides structured RCA with tool call sequence |
|
| Generates a blameless postmortem |
|
| Risk/benefit analysis before rollback |
Incident Scenario (Demo)
The seeded data tells a realistic story:
14:00 UTC — payment-service healthy: error_rate 0.2%, latency 45ms
14:02 UTC — payment-service v2.4.1 deployed (commit a3f8c21d)
14:03 UTC — Error spike: "Cannot read properties of undefined (reading 'stripeId')"
14:03 UTC — error_rate jumps to 28%, latency spikes to 320ms
14:04 UTC — Pods begin CrashLoopBackOff, 7 restarts
14:05 UTC — error_rate: 91%, latency: 1450ms, API Gateway circuit breaker opensAn agent reasoning over get_recent_deployments → get_service_logs → get_service_metrics →
analyze_root_cause should produce a hypothesis pointing to v2.4.1 as the culprit with ~0.90 confidence.
Quick Start
# 1. Clone / navigate to project
cd incident-commander-mcp
# 2. Install dependencies (already done by CLI)
npm install
# 3. Start development server
npm run devBuilding for Production
npm run build
npm startBuilt with NitroStack ⚡
Maintenance
–Maintainers
–Response time
–Release cycle
–Releases (12mo)
Commit activity
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Related MCP Servers
- AlicenseNot gradedqualityBmaintenanceAI-powered incident management and server monitoring via MCP.MIT
- FlicenseNot gradedqualityCmaintenanceAn AI-native incident response server that exposes diagnostic tools (system status, error logs, ticket creation) via MCP, enabling LLM agents to autonomously assess and respond to incidents.
- FlicenseAqualityCmaintenanceA production-ready MCP server that turns any MCP-compatible AI assistant into an AI-powered ServiceNow Incident Management Assistant, exposing incidents, users, CMDB records, and knowledge articles through validated tools.12
Related MCP Connectors
MCP server for AI agents to plan, verify, and deploy Cloudflare-native apps.
MCP server for AI access to Swagger by SmartBear.
MCP server for AI access to SmartBear tools, including BugSnag, Reflect, Swagger, PactFlow, QTM4J.
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/hashirR786/incident-commander-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server