The Prometheus Alertmanager MCP server enables programmatic querying and management of Alertmanager resources. With this server, you can:
- Query Alertmanager status: Retrieve the current status of an Alertmanager instance and its cluster
- Manage alerts: List alerts with filtering options, create new alerts, and retrieve alert groups
- Handle silences: Retrieve, create, update, and delete silences by ID
- Manage receivers: Get a list of all notification integration receivers
- Integration with AI assistants: Interact with Alertmanager using natural language through supported AI tools like Claude Desktop
Supports containerized deployment of the MCP server through Docker, with configuration via environment variables for connecting to Alertmanager instances.
Enables querying and managing Prometheus Alertmanager resources including status, alerts, silences, receivers, and alert groups. Supports creating new alerts, managing silences (create, update, delete), and retrieving alert information through the Alertmanager API v2.
Table of Contents
1. Introduction
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.
2. Features
- Query Alertmanager status, alerts, silences, receivers, and alert groups
- Create, update, and delete silences
- Create new alerts
- Authentication support (Basic auth via environment variables)
- Docker containerization support
3. Quickstart
3.1. Prerequisites
- Python 3.12+
- uv (for fast dependency management).
- Docker (optional, for containerized deployment).
- Ensure your Prometheus Alertmanager server is accessible from the environment where you'll run this MCP server.
3.2. Installing via Smithery
To install Prometheus Alertmanager MCP Server for Claude Desktop automatically via Smithery:
3.3. Local Run
- Clone the repository:
- Configure the environment variables for your Prometheus server, either through a .env file or system environment variables:
- Add the server configuration to your client configuration file. For example, for Claude Desktop:
- Or install it using make command:
- Restart Claude Desktop to load new configuration.
- You can now ask Claude to interact with Alertmanager using natual language:
- "Show me current alerts"
- "Filter alerts related to CPU issues"
- "Get details for this alert"
- "Create a silence for this alert for the next 2 hours"
3.4. Docker Run
- Run it with pre-built image (or you can build it yourself):
- Running with Docker in Claude Desktop:
This configuration passes the environment variables from Claude Desktop to the Docker container by using the -e
flag with just the variable name, and providing the actual values in the env
object.
4. Tools
The MCP server exposes tools for querying and managing Alertmanager, following its API v2:
- Get status:
get_status()
- List alerts:
get_alerts()
- List silences:
get_silences()
- Create silence:
post_silence(silence_dict)
- Delete silence:
delete_silence(silence_id)
- List receivers:
get_receivers()
- List alert groups:
get_alert_groups()
See src/alertmanager_mcp_server/server.py for full API details.
5. Development
Contributions are welcome! Please open an issue or submit a pull request if you have any suggestions or improvements.
This project uses uv to manage dependencies. Install uv following the instructions for your platform.
6. License
You must be authenticated.
hybrid server
The server is able to function both locally and remotely, depending on the configuration or use case.
Tools
alertmanager-mcp-server
Related MCP Servers
- AsecurityAlicenseAqualityA simple MCP server that can send notifications on mac devices.Last updated -598TypeScriptMIT License
- Python
- PythonMIT License
- PythonMIT License