1. Conduid
  2. Developer Tools
  3. Incident Triage MCP
MCP server · Developer Tools

Incident Triage MCP

by · github.com/felixkwasisarpong/incident-triage-mcp

Incident Triage MCP is a Model Context Protocol–native incident‑response tool server. It exposes structured triage tools, alerts, service health, runbook search, ticket creation, and more, to enable AI agents or LLM hosts to diagnose and respond to outages safely.

Unclaimed Apache-2.0 last commit 6 months ago devtools
InstallView source
59Fair

Scored just now · breakdown

About Incident Triage MCP

Incident Triage MCP is an MCP server published by felixkwasisarpong in the Developer Tools category: incident Triage MCP is a Model Context Protocol–native incident‑response tool server. It exposes structured triage tools, alerts, service health, runbook search, ticket creation, and more, to enable AI agents or LLM hosts to diagnose and respond to outages safely. It has been installed 0 times through Conduid.

Six months or more without a commit doesn't mean the server is broken, but check the open issues (0) before depending on it in production.

Install

Install
npx incident-triage-mcp

This server has no ConduID identity, so agent calls to it are not receipted. Pin the version you install and review the source before granting it credentials.

Ask AI

✦

Ask AI about Incident Triage MCP

Powered by Claude · Grounded in docs

I know everything about Incident Triage MCP. Ask me about installation, configuration, usage, or troubleshooting.

Security checks

  • ·README presentNot checked yet.
  • ·License declaredNot checked yet.
  • ·Tests presentNot checked yet.
  • ·Dependencies pinnedNot checked yet.
  • ·No dynamic code executionNot checked yet.
  • !Scoped permissionsDoesn't declare a permission scope. Assume it can do anything its process can.

Releases

v0.2.9v0.2.9 · 1 Mar 2026What's Changed chore(oss): add contributor governance, CI, linting, and label automation by @felixkwasisarpong in https://github.com/felixkwasisarpong/incident-triage-mcp/pull/71 Chore/oss governance scaffolding by @felixkwasisarpong in…
v0.2.8v0.2.8 · 24 Feb 2026Full Changelog**: https://github.com/felixkwasisarpong/incident-triage-mcp/compare/v0.2.7...v0.2.8
v0.2.7v0.2.7 · 24 Feb 2026Full Changelog**: https://github.com/felixkwasisarpong/incident-triage-mcp/compare/v0.2.6...v0.2.7
v0.2.6v0.2.6 · 24 Feb 2026What's Changed feat(production-foundation): adapter registry + provider flags + resilience scaffold by @felixkwasisarpong in https://github.com/felixkwasisarpong/incident-triage-mcp/pull/32 Feat/prod foundation adapter scaffold by…
v0.2.5v0.2.5 · 20 Feb 2026Full Changelog**: https://github.com/felixkwasisarpong/incident-triage-mcp/compare/v0.2.4...v0.2.5

README

Incident Triage MCP

Python MCP Transport Docker Kubernetes License

Incident Triage MCP is a Model Context Protocol (MCP) server for incident triage. It provides safe, auditable tools for evidence retrieval, deterministic summaries, ticket workflows, and notifications.

What This Project Is

  • MCP control plane for incident triage tools.
  • Compatible with local (stdio) and networked (streamable-http) MCP clients.
  • Designed for standalone mode, Docker Compose, and Kubernetes.

What This Project Is Not

  • Not a standalone LLM agent platform.
  • Not a provider credentials vault.
  • Not a replacement for your evidence pipeline; it consumes normalized evidence bundles.

Architecture Snapshot

  • MCP server stays thin and policy-focused.
  • Evidence collection runs in Airflow (optional) and writes EvidenceBundle artifacts.
  • Agents call MCP tools only.
  • Contract stability is defined under spec/.

For full details, see docs/ARCHITECTURE.md.

Core Tools

Tool Purpose Mutating
evidence_get_bundle Fetch normalized EvidenceBundle for an incident No
evidence_wait_for_bundle Poll until bundle is available No
incident_triage_summary Build deterministic triage summary from bundle No
jira_draft_ticket Build non-mutating ticket draft No
jira_create_ticket Create ticket with safety gates Yes

Mutating actions are guarded by RBAC, dry_run, confirm_token, audit logging, and idempotency.

Provider Matrix

Area Supported providers
Alerts mock, datadog, cloudwatch, prometheus, pagerduty, opsgenie
Metrics mock, datadog, cloudwatch, prometheus
Logs mock, datadog, cloudwatch, elk, none
Traces mock, datadog, cloudwatch, xray, otel, none
Ticketing (JIRA_PROVIDER) mock, cloud, servicenow
Notify (NOTIFY_PROVIDER) slack, teams

Quick Start

Local (stdio)

python -m venv .venv
source .venv/bin/activate
pip install -e .

MCP_TRANSPORT=stdio \
WORKFLOW_BACKEND=none \
EVIDENCE_BACKEND=fs \
EVIDENCE_DIR=./evidence \
incident-triage-mcp

Local agent run (single incident)

incident-triage-agent \
  --incident-id INC-123 \
  --service payments-api \
  --artifact-store fs \
  --artifact-dir ./evidence \
  --compact

Docker (streamable-http)

docker run --rm -p 3333:3333 \
  -e MCP_TRANSPORT=streamable-http \
  -e WORKFLOW_BACKEND=none \
  -e EVIDENCE_BACKEND=fs \
  ghcr.io/felixkwasisarpong/incident-triage-mcp:latest

Optional local stack (Airflow + Postgres + MinIO + MCP):

docker compose up --build

Kubernetes: One Agent Job Per Trigger

This is the recommended runtime pattern:

  1. Incoming trigger (webhook/manual) arrives.
  2. Dispatcher (or operator) creates one Kubernetes Job per incident.
  3. Job runs incident-triage-agent once and exits.
  4. Agent calls MCP tools over HTTP.
  5. MCP optionally triggers Airflow DAG (incident_evidence_v1) and consumes bundle from fs/s3.

Deploy MCP server (Helm)

helm upgrade --install incident-triage-mcp ./charts/incident-triage-mcp \
  --namespace incident-triage --create-namespace \
  --set image.repository=ghcr.io/felixkwasisarpong/incident-triage-mcp \
  --set image.tag=0.2.8 \
  --set env.MCP_TRANSPORT=streamable-http \
  --set env.MCP_HTTP_AUTH_MODE=api_key \
  --set secretEnv.MCP_HTTP_API_KEY=change-me

Trigger one incident with a single-run agent Job

kubectl -n incident-triage create job triage-inc-123 \
  --image=ghcr.io/felixkwasisarpong/incident-triage-mcp:0.2.8 \
  -- incident-triage-agent \
  --incident-id INC-123 \
  --service payments-api \
  --mcp-url http://incident-triage-mcp/mcp \
  --mcp-api-key change-me \
  --compact

Ensure single-run behavior

  • Use deterministic job names per incident (triage-inc-<incident_id>).
  • Reject duplicates at dispatcher level if job already exists.
  • Keep ticket creates idempotent with idempotency_key.
  • Configure Job lifecycle controls (backoffLimit, activeDeadlineSeconds, ttlSecondsAfterFinished).

Configuration Essentials

Variable Meaning
MCP_TRANSPORT stdio or streamable-http
WORKFLOW_BACKEND none or airflow
EVIDENCE_BACKEND none, fs, s3, airflow
EVIDENCE_DIR Local bundle directory when using fs
AIRFLOW_BASE_URL Required for Airflow trigger/read tools
MCP_HTTP_AUTH_MODE none, api_key, jwt_hs256
AUDIT_MODE stdout (recommended in k8s) or file
DEPLOYMENT_PROFILE local, staging, prod

Profile templates live in deploy/profiles/:

  • local.env.example
  • staging.env.example
  • prod.env.example

Testing

Run full tests:

pytest -q

Run contract checks only:

pytest -q tests/test_contract_evidence_bundle.py tests/test_contract_mcp_tools.py
python scripts/validate_contrib.py

Releases

Install from PyPI

pip install incident-triage-mcp==X.Y.Z

Pull container image

docker pull ghcr.io/felixkwasisarpong/incident-triage-mcp:X.Y.Z

Supported image tags:

  • X.Y.Z (exact)
  • X.Y (minor stream)
  • latest

For release workflow details, see docs/RELEASING.md.

Project Layout

incident-triage-mcp/
  src/incident_triage_mcp/      # MCP server + tools + adapters
  spec/                         # versioned contracts
  airflow/dags/                 # evidence pipeline
  charts/incident-triage-mcp/   # Helm chart
  k8s/                          # Kubernetes manifests
  contrib/                      # polyglot contribution area
  docs/                         # architecture, release, governance docs

Support And Triage

Documentation Index

Contributing

Read CONTRIBUTING.md before opening a PR.

License

MIT

README mirrored from the source repository just now. The original is authoritative.

Questions

About Incident Triage MCP

How do I install Incident Triage MCP?

Run npx incident-triage-mcp, then add the server to your MCP client's configuration. Conduid has recorded 0 installs, so the command is known to work with current clients.

Is Incident Triage MCP safe to use with an AI agent?

Its trust score is 59 out of 100 (fair). It passes 0 of 1 static security checks; the failures are listed above. It has no ConduID identity yet, so agent calls to it are not receipted.

Is Incident Triage MCP still maintained?

The last commit was 6 months ago, with 0 open issues. That's long enough that you should check whether the maintainer is responding to issues before depending on it.