alertmanager-mcp-server
by ntk148v
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) |
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_statusB | Get current status of an Alertmanager instance and its cluster |
| get_receiversB | 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_silenceC | Delete a silence by its ID |
| get_alertsC | Get a list of alerts |
| post_alertsD | Create new alerts |
| get_alert_groupsC | 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 | |
Latest Blog Posts
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/ntk148v/alertmanager-mcp-server'
If you have feedback or need assistance with the MCP directory API, please join our Discord server