Skip to main content
Glama
sanjanapeterlead

mcp-incident-triage-agent

MCP Incident Triage Agent

A deliberately small TypeScript project demonstrating two things:

  1. A custom Model Context Protocol (MCP) server that exposes validated backend-operations tools.

  2. 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: P12 SRE Ops MCP Server

Architecture

User prompt
    |
OpenAI Agents SDK
    |
MCP client over stdio
    |
Custom TypeScript MCP server
    |
In-memory service-health and log data

Why 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 .env

Add your API key to .env.

Run the tests

npm test

Run 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?"
A
license - permissive license
Not graded
quality - not tested
C
maintenance

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

  • F
    license
    A
    quality
    D
    maintenance
    Enables 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
  • F
    license
    Not graded
    quality
    B
    maintenance
    Enables SRE operations through natural language, providing tools to query SLO status, fetch runbooks, query alerts, and manage incidents with audit logging and latency tracking.
  • F
    license
    A
    quality
    D
    maintenance
    Exposes homelab and IT-ops tools to Claude, including system health monitoring, Grafana alert states, Docker container status, Loki logs, SMART disk health, and more.
    8
    1
  • F
    license
    Not graded
    quality
    B
    maintenance
    Provides 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

View all related MCP servers

Related MCP Connectors

  • Vendor status pages, TLS cert inspection, DNS propagation checks, and incident-response playbooks.

  • AI agent run monitoring with incident replay and SLA receipts.

  • Gateway between LLM agents and world data through eight tools and a bundled endpoint catalog.

View all MCP Connectors

Latest Blog Posts

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/sanjanapeterlead/mcp-incident-triage-agent'

If you have feedback or need assistance with the MCP directory API, please join our Discord server