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.
@ntk148v
基本情報
A Model Context Protocol (MCP) server that enables AI assistants to integreate with Prometheus Alertmanager
以下の設定を使って、このサーバーを 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"
}
}
}
}ツール一覧はまだありません
この掲載には表示できるツール一覧がまだありません。サーバーにツールがないという意味ではありません。対応機能はプロジェクトのドキュメントをご確認ください。
ツールは README から自動的に抽出されます。メンテナーは ## Tools という見出しの下に記載することで、このタブに反映できます。
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.
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.
Python 3.12+ and uv are required. Docker is optional for containerized deployment. The Alertmanager server must be accessible from the MCP server environment.
Set the `ALERTMANAGER_USERNAME` and `ALERTMANAGER_PASSWORD` environment variables. Basic authentication is supported. These are optional; when not set, no credentials are sent.
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.
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`).
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.
Agent conductor — AGENTS.md contract parser, SKILL.md registry, CHP decision engine over MCP

SSH MCP server for AI agents: remote commands, file transfer, log search and server audits through OpenSSH.
Query your team's drift, vulnerability, and migration data from any AI assistant. Vibgrate MCP connects Cursor, Claude, ChatGPT, Windsurf, or VS Code to Vibgrate Cloud: 51 tools for DriftScores, CVEs and EOL runtimes, up
OrangePro local-first CLI + MCP server for behavior mapping, grounded test generation, and dynamic proof.

Agent-Native Terminal
コメント