mcp-incident-triage-agent
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., "@mcp-incident-triage-agentInvestigate the recent checkout service errors and identify the root cause."
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.
MCP Incident Triage Agent
A deliberately small TypeScript project demonstrating two things:
A custom Model Context Protocol (MCP) server that exposes validated backend-operations tools.
An AI agent that discovers and invokes those MCP tools to investigate a sample incident.
This is a portfolio project, not a production monitoring platform.
What it does
The agent can inspect local sample data through two read-only MCP tools:
get_service_health— returns service status, latency, error rate, and dependency information.search_logs— filters recent logs by service, severity, text, or trace ID.
The agent then produces an evidence-based incident summary with a likely cause and next action.
Related MCP server: AI Incident Monitoring RCA MCP Server
Architecture
User prompt
|
OpenAI Agents SDK
|
MCP client over stdio
|
Custom TypeScript MCP server
|
In-memory service-health and log dataWhy the scope is intentionally small
Included:
One CLI agent
One local MCP server
Two read-only tools
Zod input validation
Sample operational data
Unit tests
Error handling and server cleanup
Not included:
Web UI
Database
Authentication
Cloud deployment
Message queues
Vector database
Multi-agent orchestration
Those additions would make the project easier to abandon without making the résumé claim much stronger.
Requirements
Node.js 20 or newer
An OpenAI API key
Setup
npm install
cp .env.example .envAdd your API key to .env.
Run the tests
npm testRun the agent
npm run agent -- "Investigate the learning-api degradation and recommend the safest next action."Try another prompt:
npm run agent -- "Which service is unhealthy, and what log evidence supports the diagnosis?"This server cannot be installed
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Related MCP Connectors
- SuperlogOAuthsh.superlog
Open-source agent that observes and fixes your application. Query logs, traces, metrics, incidents.
Production observability for AI agents: search runs, read evaluations, acknowledge incidents.
Vendor status pages, TLS cert inspection, DNS propagation checks, and incident-response playbooks.
AI agent run monitoring with incident replay and SLA receipts.
Related MCP Servers
- FlicenseAqualityDmaintenanceEnables AI agents to query Prometheus metrics and Loki logs for intelligent alert investigation and troubleshooting. Provides service discovery, metric querying, log searching, and correlation tools to help identify root causes of issues.9-
- FlicenseNot gradedqualityBmaintenanceProvides telemetry tools for retrieving recent logs and system metrics to support root-cause analysis of infrastructure incidents. Enables autonomous incident triage with grounded verification and human-in-the-loop remediation.1-
- FlicenseNot gradedqualityBmaintenanceEnables autonomous infrastructure health management by exposing tools for retrieving system logs, querying a knowledge base, executing SQL analytics, and simulating system commands, all integrated into an AI-driven incident response workflow.-
- FlicenseNot gradedqualityCmaintenanceEnables AI agents to investigate production incidents by exposing service health, logs, and deployment data through MCP tools.10-