MCP.so
ログイン

Prometheus Alertmanager MCP Server

@ntk148v

基本情報

カテゴリ

開発者ツール

ライセンス

Apache-2.0

トランスポート

stdio

作者

ntk148v

投稿者

Kien Nguyen-Tuan

Prometheus Alertmanager MCP Server について

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

Prometheus Alertmanager MCP Server の設定

以下の設定を使って、このサーバーを MCP 対応クライアントに追加してください。

{
  "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 のツール

ツール一覧はまだありません

この掲載には表示できるツール一覧がまだありません。サーバーにツールがないという意味ではありません。対応機能はプロジェクトのドキュメントをご確認ください。

ツールは README から自動的に抽出されます。メンテナーは ## Tools という見出しの下に記載することで、このタブに反映できます。

概要

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

よくある質問

1

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.

2

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.

3

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.

4

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`).

5

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.

コメント

「開発者ツール」の他のコンテンツ