Alertmanager MCP Server

Prometheus Alertmanager MCP Server for Claude AI integration

Local serverstdioTypeScript

What is the Alertmanager MCP server?

Prometheus Alertmanager MCP Server for Claude AI integration. The alertmanager mcp server wraps that behind the Model Context Protocol, so an assistant can use it through 2 defined tools rather than through you.

What it actually does

  1. Alert Retrieval: Fetches and formats current alerts from Alertmanager with optional filtering capabilities.

Its toolset

Everything the assistant can do here goes through one of these:

  • Prerequisites — The Prerequisites tool exposed by this server
  • Setup — The package is available on npm and can be used directly with npx:

Configuration

You will need one environment variable: ALERTMANAGER_URL. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

Adding it to your client

Installation goes through your MCP client rather than a global install: point it at alertmanager-mcp on npm and it is fetched when the client starts. The copy-paste blocks for Claude Desktop, Claude Code and Cursor are further down this page.

When to reach for it

Plenty of monitoring and observability servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Alertmanager's toolset — Prerequisites, Setup — is a fair guide to whether it matches your workflow. It is maintained by kaznak; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.

Caveats

  • It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
  • Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
  • MCP clients confirm each tool call by default. Leave that on until you have watched what the alertmanager mcp server does with a few real requests.

Available tools

ToolWhat it does
PrerequisitesThe Prerequisites tool exposed by this server.
SetupThe package is available on npm and can be used directly with npx:

How to install the Alertmanager MCP server

{
    "mcpServers": {
      "alertmanager": {
        "command": "docker",
        "args": [
          "run",
          "--rm",
          "-i",
          "--network=host",
          "-e", "ALERTMANAGER_URL=http://your-alertmanager-url:9093",
          "ghcr.io/kaznak/alertmanager-mcp:latest"
        ],
        "env": {}
      }
    }
  }

Configuration as documented by the project. Restart the client after saving.

Configuration

VariableDescriptionRequired
ALERTMANAGER_URLEndpoint or connection string the server talks to.Yes

Example prompts to try

  • Use Alertmanager to Prerequisites.
  • Use Alertmanager to Setup.

Frequently asked questions

It connects Alertmanager to MCP-compatible AI assistants such as Claude and Cursor, exposing 2 tools (Prerequisites, Setup) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with Alertmanager directly.