Alertmanager MCP Server

Created By
eyazici90a year ago
MCP server for Prometheus-Alertmanager
Overview

what is Alertmanager MCP Server?

Alertmanager MCP Server is an implementation of the Model Context Protocol (MCP) server designed for use with Prometheus Alertmanager, facilitating the management of alerts.

how to use Alertmanager MCP Server?

To use the Alertmanager MCP Server, you can either build it from source using Go or run it as a Docker container. For building from source, ensure you have Go 1.24.3 or higher installed, then run make build. For Docker, execute make docker-build to create the Docker image.

key features of Alertmanager MCP Server?

  • Integration with Prometheus Alertmanager for alert management
  • Support for Model Context Protocol (MCP)
  • Easy installation via binaries or Docker

use cases of Alertmanager MCP Server?

  1. Managing alerts in a Prometheus monitoring setup.
  2. Facilitating communication between different components in a microservices architecture.
  3. Enhancing alert handling capabilities in cloud-native applications.

FAQ from Alertmanager MCP Server?

  • What is the purpose of the Alertmanager MCP Server?

The Alertmanager MCP Server is designed to manage alerts generated by Prometheus, providing a structured way to handle alert notifications.

  • How can I install the Alertmanager MCP Server?

You can install it by building from source or using Docker. Refer to the installation instructions in the documentation.

  • Is there a specific Go version required?

Yes, Go version 1.24.3 or higher is required to build from source.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
eyazici90
Star
0
Language
Go
License
-
Category
monitoring

Recommend Servers

View All
Payai X402 Tools

6 hours ago
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

a day ago