alertmanager-mcp-server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MCP_HOST | No | Host/interface to bind when running http or sse transports | 0.0.0.0 |
| MCP_PORT | No | Port to listen on when running http or sse transports | 8000 |
| MCP_TRANSPORT | No | Transport mode. One of stdio, http, or sse | stdio |
| ALERTMANAGER_URL | Yes | The URL of your Prometheus Alertmanager server | |
| ALERTMANAGER_PASSWORD | No | Password for basic authentication (optional) | |
| ALERTMANAGER_USERNAME | No | Username for basic authentication (optional) |
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_statusA | Get current status of an Alertmanager instance and its cluster |
| get_receiversA | Get list of all receivers (name of notification integrations) |
| get_silencesC | Get list of all silences |
| post_silenceC | Post a new silence or update an existing one |
| get_silenceC | Get a silence by its ID |
| delete_silenceB | Delete a silence by its ID |
| get_alertsC | Get a list of alerts |
| post_alertsC | Create new alerts |
| get_alert_groupsD | Get a list of alert groups |
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 9 tools
Each tool targets a distinct resource and action (e.g., get vs post, alerts vs silences vs status). There is no overlap; get_alert_groups and get_alerts are clearly differentiated.
All tool names follow a consistent verb_noun pattern with lowercase underscores: delete_, get_, post_. No mixing of styles or irregular verbs.
With 9 tools covering common Alertmanager operations (list, get, create, delete for alerts and silences, plus status and receivers), the count is well-scoped for the domain.
Covers core alert and silence lifecycle management, status, and receivers. A minor gap: no tool to update alert fields or manage alert rules, but these are outside Alertmanager's typical CRUD.