A Model Context Protocol (MCP) server for Prometheus Alertmanager
npx -y mcp-alertmanagerAdd this server entry to the mcpServers object in your Claude Desktop config, then restart the app.
{
"mcpServers": {
"io-github-jeanlopezxyz-mcp-alertmanager": {
"command": "npx",
"args": [
"-y",
"mcp-alertmanager"
]
}
}
}~/Library/Application Support/Claude/claude_desktop_config.json%APPDATA%\Claude\claude_desktop_config.jsonNo remote HTTP endpoint is advertised. Use the package or stdio setup shown in Install.
mcp-alertmanager is an MCP server for A Model Context Protocol (MCP) server for Prometheus Alertmanager. It supports STDIO transport.
Use the generated config in Install. This server runs with npx -y mcp-alertmanager; add any required environment variables before starting your client.
Choose the Claude Desktop tab in Install and copy the config for npx -y mcp-alertmanager. Add required environment variables before starting Claude Desktop.
Choose the Claude Code tab in Install and copy the config for npx -y mcp-alertmanager. Add required environment variables before starting Claude Code.
Choose the Codex tab in Install and copy the config for npx -y mcp-alertmanager. Add required environment variables before starting Codex.
Choose the Cursor or VS Code tab in Install and copy the config for npx -y mcp-alertmanager. Add required environment variables before starting Cursor or VS Code.
mcp-alertmanager uses STDIO transport. Use the package or command config in Install.
mcp-alertmanager inventory is listed when the MCP endpoint exposes tools, resources, or prompts. Some servers require auth first.
mcp-alertmanager does not advertise a verified auth requirement. If discovery fails, it may still need provider login, an API key, a bearer token, or a session header.
| Package | Registry | Version | Inputs |
|---|---|---|---|
mcp-alertmanagerstdio | npm | 2.1.1 | None advertised |