A Model Context Protocol (MCP) server that enables AI assistants to integrate with Prometheus Alertmanager
Alertmanager MCP server is a locally run integration for AI assistants that speak the Model Context Protocol. A Model Context Protocol (MCP) server that enables AI assistants to integrate with Prometheus Alertmanager.
Prometheus Alertmanager MCP is a Model Context Protocol (MCP) server for Prometheus Alertmanager. It enables AI assistants and tools to query and manage Alertmanager resources programmatically and securely.
Once Alertmanager is connected, these are the calls the assistant has available:
count — Number of alerts per page (default: 10, max: 25)offset — Number of alerts to skip (default: 0)Returns — { "data": [...], "pagination": { "total": N, "offset": M, "count": K, "has_more": bool } }Note — Alert groups have lower limits because they contain all alerts within each groupYou will need 3 environment variables: ALERTMANAGER_URL, ALERTMANAGER_USERNAME, ALERTMANAGER_PASSWORD. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.
@smithery/cli on npm is all you need. Most clients run it directly, so configuration is a few lines and a restart.
Among the monitoring and observability options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Alertmanager's toolset — count, offset, Returns and 1 more — is a fair guide to whether it matches your workflow.
SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.
| Tool | What it does |
|---|---|
| count | Number of alerts per page (default: 10, max: 25) |
| offset | Number of alerts to skip (default: 0) |
| Returns | { "data": [...], "pagination": { "total": N, "offset": M, "count": K, "has_more": bool } } |
| Note | Alert groups have lower limits because they contain all alerts within each group |
{
"mcpServers": {
"alertmanager": {
"command": "npx",
"args": ["-y", "@smithery/cli"],
"env": {
"ALERTMANAGER_URL": "your-value",
"ALERTMANAGER_USERNAME": "your-value",
"ALERTMANAGER_PASSWORD": "your-value"
}
}
}
}Add to claude_desktop_config.json, then restart Claude Desktop.
| Variable | Description | Required |
|---|---|---|
| ALERTMANAGER_URL | Endpoint or connection string the server talks to. | Yes |
| ALERTMANAGER_USERNAME | Configuration value read at startup. | Optional |
| ALERTMANAGER_PASSWORD | Configuration value read at startup. | Optional |
Give your coding agent the full DevTools toolbox: traces, network, console, heap snapshots and Lighthouse.
Dashboards, Prometheus and Loki queries, incidents and alerts — observability by conversation.
Errors with full context — stack traces, issue triage and AI-powered root-cause analysis from Sentry's server.
Auth0 Model Context Protocol (MCP) Server (Beta) — A secure and extendable implementation of an MCP server that provides AI assistants with
Query Onchain data, like ERC20 tokens, transaction history, smart contract state.
An MCP server for breaking down complex tasks into manageable pieces with structured JSON storage