alertmanager-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ALERTMANAGER_URL | Yes | The URL of your Prometheus Alertmanager instance |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get-alertsD | – |
| get-alert-detailsD | – |
| create-silenceD | – |
| get-silencesD | – |
| delete-silenceD | – |
| get-alert-groupsD | – |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 6 tools
Tool names are generally distinct: create/delete/get silences, get alerts, get alert details, get alert groups. However, without descriptions, 'get-alert-details' and 'get-alerts' could cause slight confusion as to whether details are a subset.
All tools follow a consistent verb_noun pattern with kebab-case: create/delete/get + resource. No mixing of styles.
6 tools is well-scoped for an Alertmanager MCP server, covering the essential operations without being excessive.
The set covers creating/deleting silences and retrieving alerts and silences. Missing update silence or alert acknowledgment, but these are not standard Alertmanager operations, so minor gap.