# Alertmanager MCP Server — 12 tools via DADL

The Alertmanager DADL turns Alertmanager's API into an MCP server that Claude, GPT or any MCP-compatible agent can consume directly. One YAML file declares all 12 tools — silence, alert, health, receiver, status, group, and more — and ToolMesh serves them at runtime. No Python boilerplate, no per-endpoint code, no separate MCP server process.

Below: the endpoint coverage matrix, a two-block ToolMesh setup, the full tool reference grouped by Alertmanager feature area.

**Source:** [Prometheus Alertmanager API v2](https://prometheus.io/docs/alerting/latest/clients/)

**Updated:** 2026-04-13

**Tags:** monitoring, alerting, crud, user-management, notifications, deployment, logging, auth:basic

## Which Alertmanager endpoints are covered?

**100%** (14 of ~14 endpoints).

**Focus:** alerts (list, create/update, groups), silences (CRUD), receivers (list), status, health/ready/reload

**Missing:** metrics and pprof debug endpoints (not useful for API consumers)

*Last reviewed: 2026-04-13*

## How do you configure the Alertmanager DADL?

1. Alertmanager has no built-in auth by default. If --web.config.file is configured with basic_auth_users:
2. 1. Open the web.config.yml used by your Alertmanager instance
3. 2. Find or add your username under basic_auth_users
4. 3. Generate a bcrypt hash of your password: htpasswd -nBC 10 '' | tr -d ':\n'
5. 4. Add the username: bcrypt_hash pair to basic_auth_users
6. 5. Reload Alertmanager config (POST /-/reload or send SIGHUP)
7. If no auth is configured, leave credentials empty or use a reverse proxy for auth

**Environment variable:** `ALERTMANAGER_URL`

[Authentication docs](https://prometheus.io/docs/alerting/latest/https/)

*Default port is 9093. Set ALERTMANAGER_URL to http(s)://host:9093. For HA setups, point to any cluster member or a load balancer.*

## How do you install the Alertmanager MCP server with ToolMesh?

Add to your `backends.yaml`:

```yaml
alertmanager.dadl
```

Set the credential:

```
ALERTMANAGER_URL=your-token-here
```

## What 12 tools does the Alertmanager DADL expose?

- **GET** `get_status` — Get Alertmanager status including version, config, uptime, and cluster state
- **GET** `get_health` — Health check — returns 200 if Alertmanager is running (liveness probe)
- **GET** `get_ready` — Readiness check — returns 200 when Alertmanager is ready to serve traffic
- **GET** `list_alerts` — List alerts with optional filters by state, receiver, and label matchers
- **POST** `post_alerts` — Create new alerts or update existing ones. Alerts are matched by label fingerprint. Set endsAt to resolve.
- **GET** `list_alert_groups` — Get alerts grouped by the routing tree configuration
- **GET** `list_silences` — List all silences, optionally filtered by label matchers
- **GET** `get_silence` — Get a single silence by its ID
- **POST** `post_silence` — Create a new silence or update an existing one. Include id to update, omit to create.
- **DELETE** `delete_silence` — Expire (delete) a silence by its ID. This immediately stops the silence from suppressing alerts.
- **GET** `list_receivers` — List all configured notification receiver names
- **POST** `reload_config` — Trigger a configuration reload (equivalent to sending SIGHUP to the process)

## Which DADLs are related to Alertmanager?

- [Checkmk](https://www.dadl.ai/d/checkmk/) — Checkmk REST API (version 1.0, Checkmk 2.4) -- live host and service status via Livestatus queries, downtimes, acknowledgements and comments, the Event Console (list, acknowledge, change state and archive events) and BI (packs, rules, aggregations and live aggregation state), plus the full Setup side: hosts, clusters, folders, service discovery, rules and rulesets, host/service/contact groups, users, roles, passwords, time periods, host tags, notification rules, site connections and change activation.

- [Mikrotik](https://www.dadl.ai/d/mikrotik/) — MikroTik RouterOS REST API -- manage interfaces, IP addresses, routing, firewall, DHCP, DNS, PPP, queues, wireless, system configuration, users, certificates, files, logs, and diagnostics on RouterOS v7.1+ devices
- [Unifi](https://www.dadl.ai/d/unifi/) — Ubiquiti UniFi Network Controller API -- manage sites, APs, switches, gateways, clients, networks, WLANs, firewall rules, DPI stats, guests, vouchers, and backups
- [Billomat](https://www.dadl.ai/d/billomat/) — Billomat REST API — German cloud invoicing & accounting: invoices, estimates, credit notes, recurring invoices, delivery notes, order confirmations, dunning reminders, clients, contacts, articles, payments, expenses, taxes
- [BookStack](https://www.dadl.ai/d/bookstack/) — BookStack wiki and documentation platform REST API -- shelves, books, chapters, pages (HTML/Markdown content), attachments, image gallery, comments, cross-entity search, exports (HTML/Markdown/PDF/ZIP), ZIP imports, users, roles, content permissions, recycle bin, audit log and tags. Hierarchy: shelves > books > chapters > pages.
- [CentralStationCRM](https://www.dadl.ai/d/centralstationcrm/) — CentralStationCRM REST API v1 — German small-business CRM: people, companies, deals in pipelines, projects, tasks, notes (protocols), calendar, tags, custom fields, attachments, activity stream and webhooks

---

**Canonical URL:** https://www.dadl.ai/d/alertmanager/
**Raw DADL:** https://github.com/DunkelCloud/dadl-registry/blob/main/alertmanager.dadl
