Prometheus Alertmanager MCP Server

Created By
kaznaka year ago
A Model Context Protocol (MCP) server that integrates with Prometheus Alertmanager
Overview

What is Alertmanager MCP?

Alertmanager MCP is a Model Context Protocol (MCP) server that integrates with Prometheus Alertmanager, allowing Claude AI to manage alerts through a standardized interface.

How to use Alertmanager MCP?

To use Alertmanager MCP, install it via npm and configure it with Claude for Desktop to interact with Prometheus Alertmanager using natural language commands.

Key features of Alertmanager MCP?

  • Alert Retrieval: Fetches and formats current alerts with filtering options.
  • Alert Details: Provides detailed information about specific alerts.
  • Silence Management: Create, list, and delete silences for alerts.
  • Alert Grouping: Retrieves organized alert groups from Alertmanager.

Use cases of Alertmanager MCP?

  1. Managing alerts in a cloud infrastructure.
  2. Automating alert responses through AI.
  3. Integrating alert management into incident response workflows.

FAQ from Alertmanager MCP?

  • Can Alertmanager MCP work with any version of Prometheus Alertmanager?

Yes, it is designed to work with the HTTP API of Prometheus Alertmanager.

  • Is there a cost to use Alertmanager MCP?

No, it is open-source and free to use.

  • What programming language is Alertmanager MCP built with?

It is built using TypeScript.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
kaznak
Star
0
Language
TypeScript
License
MIT license

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago