Prometheus Alertmanager MCP Server

@ntk148v

Repository

Basic information

About Prometheus Alertmanager MCP Server

A Model Context Protocol (MCP) server that enables AI assistants to integreate with Prometheus Alertmanager

#devops #ai #mcp #prometheus #alertmanager#devopstools#mcp-server

Prometheus Alertmanager MCP Server config

Add this server to your MCP-compatible client using the configuration below.

{
  "mcpServers": {
    "alertmanager": {
      "command": "uv",
      "args": [
        "--directory",
        "<full path to alertmanager-mcp-server directory>",
        "run",
        "src/alertmanager_mcp_server/server.py"
      ],
      "env": {
        "ALERTMANAGER_URL": "http://your-alertmanager:9093s",
        "ALERTMANAGER_USERNAME": "your_username",
        "ALERTMANAGER_PASSWORD": "your_password"
      }
    }
  }
}

Prometheus Alertmanager MCP Server tools

Tool list not available yet

This listing does not currently have a tool list to display. This does not mean the server has no tools; check its documentation for supported capabilities.

We auto-extract tools from the README. The maintainer can list them under a ## Tools heading to populate this section.

Overview

What is Prometheus Alertmanager MCP?

Prometheus Alertmanager MCP is a Model Context Protocol (MCP) server that enables AI assistants to query and manage Prometheus Alertmanager resources programmatically and securely. It exposes tools for interacting with the Alertmanager API v2, including pagination and authentication support.

How to use Prometheus Alertmanager MCP?

Install via Smithery with npx -y @smithery/cli install @ntk148v/alertmanager-mcp-server --client claude, or clone the repository and run locally with uv. Docker images are also available. Configure environment variables for ALERTMANAGER_URL, optional ALERTMANAGER_USERNAME/ALERTMANAGER_PASSWORD, and optional ALERTMANAGER_TENANT. Add the server configuration to your MCP client (e.g., Claude Desktop) and use natural language commands like "Show me current alerts". Supports stdio, http, and sse transports.

Key features of Prometheus Alertmanager MCP

Query alertmanager status, alerts, silences, receivers, and alert groups
Smart pagination to prevent LLM context window overflow
Create, update, and delete silences
Create new alerts
Authentication support via basic auth environment variables
Multi-tenant support via X-Scope-OrgId header (Mimir/Cortex)

Use cases of Prometheus Alertmanager MCP

Query current alerts and filter by criteria (silenced, inhibited, active)
Create and manage silences for specific alerts
List alert groups and receivers for operational overview
Handle large numbers of alerts with paginated browsing
Integrate alerts into AI-driven incident response workflows

Frequently asked questions

What are the prerequisites to run the server?

Python 3.12+ and uv are required. Docker is optional for containerized deployment. The Alertmanager server must be accessible from the MCP server environment.

How do I configure authentication?

Set the `ALERTMANAGER_USERNAME` and `ALERTMANAGER_PASSWORD` environment variables. Basic authentication is supported. These are optional; when not set, no credentials are sent.

How does pagination work for alerts, silences, and alert groups?

By default, 10 items per page are returned. The `count` parameter controls page size (max 25 for alerts, 50 for silences, 5 for alert groups) and `offset` controls skip. The response includes `has_more` to indicate additional pages.

What transport options are available and how do I configure them?

Three transports are supported: `stdio` (default), `http` (streamable HTTP), and `sse`. Configure via command‑line flags (`--transport`, `--host`, `--port`) or environment variables (`MCP_TRANSPORT`, `MCP_HOST`, `MCP_PORT`).

How do I set up multi-tenant support?

Set the `ALERTMANAGER_TENANT` environment variable for a static tenant, or include the `X-Scope-OrgId` header in requests for per‑request tenant switching. The header takes precedence over the static configuration.

Comments

More Developer Tools MCP servers

Kaiva Bridge

Kaiva Bridge turns your API, database or documents into a managed MCP server for Claude, ChatGPT, Cursor and VS Code. Point it at an OpenAPI or Swagger spec, an API docs link, a cURL command, a Postman collection, a Grap

OrangePro

Aamir Siddiqui

OrangePro local-first CLI + MCP server for behavior mapping, grounded test generation, and dynamic proof.

Testiny MCP server

Mategra GmbH

Testiny is a test case management platform. Its remote MCP server lets AI assistants such as Claude, ChatGPT, GitHub Copilot, Cursor and other MCP clients work directly with your Testiny data. Browse and search projects,

offprompt

MCP server that lets Claude Code, Cursor or Codex ask you for API keys on a local page and write them to .env. The agent only ever sees key names.

Casefile

azimov777

One case file per task — shared by every session, agent and person that touches it. Self-hosted MCP server and live board. MIT.