list_alertsLABSCO 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
Follow the published steps
USE CASES
01
Seeing what is firing right now
List alerts narrowed by label matcher, state or receiver.
02
Silencing a known-noisy alert during a deploy
Create the silence with matchers, your name, a reason and a duration.
03
Checking whether someone already silenced it
List existing silences filtered by the same label matchers.
04
Bringing an alert back early
Expire the silence by ID once the work is finished.
05
Reading the reason behind a silence you did not create
Fetch it by ID and read its author, comment and window.
5 tools
Listed in project docs. Your client may show a different list.
list_silencesget_silencecreate_silencedelete_silenceBEFORE YOU INSTALL
What to know first
Tools you get
5 tools named in the project's documentation.
Requires
mcp-alertmanager on PATH
Where it runs
The documented client runs the server on your machine.
INSTALLATION
Connect your client
Server setup
Download the archive for your platform from https://github.com/zekker6/mcp-alertmanager/releases/latest — for example mcp-alertmanager_Darwin_arm64.tar.gz on an Apple-silicon Mac or mcp-alertmanager_Linux_x86_64.tar.gz on Linux.
Unpack it and move the mcp-alertmanager binary into a folder on your PATH.
MCP Clients
Claude Desktop
CLAUDE DESKTOP · JSON
{
"mcpServers": {
"alertmanager": {
"command": "mcp-alertmanager",
"args": [
"-url",
"http://alertmanager:9093"
]
}
}
}
