Alertmanager MCP

🚀 Noisy Manager MCP Server

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

🚀 Quick Start

The Noisy Manager MCP Server acts as a crucial link between Claude AI and Prometheus Alertmanager, facilitating seamless alert management.

✨ Features

1. Alert Retrieval: Fetch and format current alerts from Alertmanager, with optional filtering capabilities.
2. Alert Details: Provide detailed information about specific alerts when referencing their fingerprints.
3. Silence Management: Offer tools to create, list, and delete notifications that suppress specific alerts.
4. Alert Grouping: Retrieve alert groups organized by Alertmanager.

🔧 Technical Details

• Built with TypeScript and MCP SDK.
• Communicates with Alertmanager's HTTP API (v2).
• Runs as a process based on standard input and output, suitable for Claude Desktop.
• Implements appropriate error handling and timeout management.
• Provides strongly typed interfaces to represent alert and silence data.

📦 Installation

Prerequisites

• Access to a running Prometheus Alertmanager instance.
• For Claude Desktop: Node.js (v18 or higher) installed on the system.

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 Examples

Using with Claude Desktop

1. Configure Claude 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": {}
       }
     }
   }
   

2. Restart Claude Desktop to load the new configuration.

3. Now, you can have Claude interact with Alertmanager using natural language:

   • "Show current alerts"
   • "Filter alerts related to CPU"
   • "Get details of this alert"
   • "Create a silence for this alert for the next 2 hours"

Available Tools

get-alerts

Retrieve a list of alerts with optional filtering.

Parameters:

• filter: (Optional) Filter query (e.g., alertname=~'.*CPU.*').
• silenced: (Optional) Include silenced alerts.
• inhibited: (Optional) Include inhibited alerts.
• active: (Optional) Include active alerts.

get-alert-details

Get detailed information about an alert by its ID.

Parameters:

• alert-id: The ID of the alert to get details for.

create-silence

Create a silence for specific matching conditions.

Parameters:

• conditions: Conditions that the silence should match.
• startsAt: The time when the silence starts (ISO datetime).
• endsAt: The time when the silence ends (ISO datetime).
• comment: (Optional) A comment for the silence.

list-silences

List all current silences.

No parameters.

delete-silence

Delete a silence by its ID.

Parameters:

• silence-id: The ID of the silence to delete.