Prometheus Alertmanager MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ALERTMANAGER_URL | Yes | The URL of your Alertmanager instance (e.g., http://your-alertmanager-url:9093) |
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
Server capabilities have not been inspected yet.
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
Each tool has a clearly distinct purpose targeting specific resources: create/delete silences, get alerts with varying granularity (details, groups, list), and get silences. There is no overlap in functionality, making tool selection straightforward for an agent.
All tools follow a consistent verb-noun pattern with hyphens (e.g., create-silence, get-alerts). The naming is uniform across all six tools, using clear verbs like 'create', 'delete', and 'get' paired with specific nouns.
Six tools are well-scoped for managing Prometheus Alertmanager alerts and silences, covering core operations. It is slightly lean but reasonable, as it includes essential CRUD-like actions for silences and multiple alert retrieval methods.
The toolset covers key areas: silences (create, delete, list) and alerts (list, groups, details). However, there are notable gaps such as no tools for creating, updating, or deleting alerts, which limits full lifecycle management in the alert domain.