Go from alert to fix with MCPs for logs, metrics, incidents and code

An SRE team gave its LLM MCPs for Loki, Prometheus, Grafana, Incident.io, GitHub and server inventory.

Difficulty
AdvancedOur rating
Time to build
Not reportedOur estimate
Monthly cost
Not reported
Revenue
Not reportedWe only show revenue the source states
Engagement
0 replies to HN commentComment in “Ask HN: Who is using MCP in production?” (198 points, 201 comments) · fetched Oct 15, 2026

What they did

At a past job, alexpotato’s team had MCPs for Loki, Prometheus, Grafana, Incident.io, GitHub and a custom server inventory.

How it went

He says the LLM could start from an alert, find its source in code and check metrics, automating a lot of alert toil.

Worth knowing

The value comes from combining sources.

Builder recipe

Our own starting point, written from the source. Adapt it to your setup.

Stack

  • MCPs for logs, metrics, incidents and code
  • An LLM agent

Steps

  1. Write down the manual process step by step.
  2. Automate the deterministic parts with plain workflow steps or scripts.
  3. Use the model only where judgment is needed, with confidence checks.
  4. Add alerts and a human fallback.

Starter prompt

Alert [name] fired. Find where it is defined in the repo, pull the related metrics and logs for the last hour, and summarize the likely cause and a safe fix.

Tags

Read the original

Related use cases

The Daily 5.

Five real AI agent use cases each morning, each with a recipe and a source. Plus a Sunday roundup. Free.