1. Conduid
  2. Blockchain
  3. Prometheus Alertmanager Integration Server
MCP server · Blockchain

Prometheus Alertmanager Integration Server

Enable natural language interaction with Prometheus Alertmanager to manage alerts and silences efficiently. Retrieve, filter, and group alerts, as well as create and delete silences through a standardized interface. Simplify alert management by bridging Claude AI with Alertmanager's API.

Unclaimed last commit a year ago blockchain
34Low

Scored 6 months ago · breakdown

About Prometheus Alertmanager Integration Server

Prometheus Alertmanager Integration Server is an MCP server published by comqx in the Blockchain category: enable natural language interaction with Prometheus Alertmanager to manage alerts and silences efficiently. Retrieve, filter, and group alerts, as well as create and delete silences through a standardized interface. Simplify alert management by bridging Claude AI with Alertmanager's API.

Six months or more without a commit doesn't mean the server is broken, but check the open issues before depending on it in production.

Install

From source
git clone https://github.com/comqx/alertmanager-mcp

This server has no ConduID identity, so agent calls to it are not receipted. Pin the version you install and review the source before granting it credentials.

Ask AI

✦

Ask AI about Prometheus Alertmanager Integration Server

Powered by Claude · Grounded in docs

I know everything about Prometheus Alertmanager Integration Server. Ask me about installation, configuration, usage, or troubleshooting.

Security checks

  • ✓README presentThe repository ships documentation.

5 checks have not been run yet.

README

Prometheus Alertmanager MCP Server

smithery badge

This project implements a Model Context Protocol (MCP) server that integrates with Prometheus Alertmanager. It serves as a bridge between Claude AI and Alertmanager, allowing Claude to interact with and manage alerts through a standardized interface.

Core Features

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

  2. Alert Details: Provides detailed information about specific alerts when referenced by their fingerprint.

  3. Silence Management: Offers tools to create, list, and delete silences that suppress notifications for specific alerts.

  4. Alert Grouping: Retrieves alert groups as organized by Alertmanager.

Technical Implementation

Installation

Installing via Smithery

To install Prometheus Alertmanager Integration Server for Claude Desktop automatically via Smithery:

npx -y @smithery/cli install @comqx/alertmanager-mcp --client claude

Prerequisites

Setup

The package is available on npm and can be used directly with npx:

npx alertmanager-mcp

For global installation:

npm install -g alertmanager-mcp
alertmanager-mcp

Usage with Claude for Desktop

  1. Configure Claude for Desktop to use the MCP server by editing the configuration file:
{
  "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": {}
    }
  }
}
  1. Restart Claude for Desktop to load the new configuration.

  2. You can now ask Claude to interact with Alertmanager using natural 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"

Available Tools

get-alerts

Retrieves a list of alerts with optional filtering.

Parameters:

  • filter: (optional) Filtering query (e.g., alertname=~'.*CPU.*')
  • silenced: (optional) Include silenced alerts
  • inhibited: (optional) Include inhibited alerts
  • active: (optional) Include active alerts (default: true)

get-alert-details

Gets detailed information about a specific alert.

Parameters:

  • fingerprint: Alert fingerprint

create-silence

Creates a silence for alerts matching specified criteria.

Parameters:

  • matchers: List of matchers for alerts
  • startsAt: (optional) Silence start time (ISO8601 format, default is current time)
  • endsAt: Silence end time (ISO8601 format)
  • createdBy: Username who created the silence
  • comment: Reason or explanation for the silence

get-silences

Retrieves a list of silences with optional filtering.

Parameters:

  • filter: (optional) Filtering query (e.g., createdBy=~'.*admin.*')

delete-silence

Deletes a silence by ID.

Parameters:

  • silenceId: ID of the silence to delete

get-alert-groups

Gets alert groups with optional filtering.

Parameters:

  • active: (optional) Include active alerts (default: true)
  • silenced: (optional) Include silenced alerts
  • inhibited: (optional) Include inhibited alerts

Extending the Server

This MCP server can be extended with additional features such as:

  • Alert trend analysis
  • Automatic response suggestions
  • Integration with incident management systems
  • Custom dashboards for specific alert types

Resources

README copy captured when this server was indexed; it may lag the repository. The original is authoritative.

Questions

About Prometheus Alertmanager Integration Server

How do I install Prometheus Alertmanager Integration Server?

No package has been published for this server, so install it from source: clone the repository and follow its README.

Is Prometheus Alertmanager Integration Server safe to use with an AI agent?

Its trust score is 34 out of 100 (low). It passes 1 of the 1 static security checks run so far. It has no ConduID identity yet, so agent calls to it are not receipted.

Is Prometheus Alertmanager Integration Server still maintained?

The last commit was a year ago. That's long enough that you should check whether the maintainer is responding to issues before depending on it.