Labsco
MCP SERVER

Alertmanager

by zekker6

Lists what Prometheus Alertmanager is firing right now, and creates or expires silences without opening the UI.

Observability, Monitoring & Incident Response
Summary
Silence the noisy alert while you are still talking about it.

Triage is mostly two questions: what is firing, and has someone already silenced it. Both are one call here, and writing the silence with its matchers and duration is a third.

What it is

An MCP server for Prometheus Alertmanager. It exposes alert listing and the whole silence lifecycle — create, read, list, expire — as tools.

What you get
  • Alerts listed, filtered by label matchers, state or receiver
  • Silences listed, filtered by label matchers
  • A single silence fetched by ID
  • A silence created with matchers, author, comment and duration
  • A silence expired by ID
Requirements

The URL of your Alertmanager, passed with -url. Basic auth goes in through -username and -password-file, and -header carries bearer tokens or a tenant ID. Runs over stdio by default, or SSE with -mode sse.

Setup effort

One command — mcp-alertmanager -url http://alertmanager:9093