English Français العربية

io.github.jeanlopezxyz/mcp-alertmanager

Official registry AI and agents

A Model Context Protocol (MCP) server for Prometheus Alertmanager

Source code Documentation

Install

Add this to your client's MCP configuration (Claude Desktop: claude_desktop_config.json; Cursor: .cursor/mcp.json; VS Code and others use the same "mcpServers" shape).

NPM package mcp-alertmanager
Claude Code 
claude mcp add mcp-alertmanager -- npx -y mcp-alertmanager@2.1.1
JSON configuration (Claude Desktop, Cursor, VS Code) 
{
    "mcpServers": {
        "mcp-alertmanager": {
            "command": "npx",
            "args": [
                "-y",
                "mcp-alertmanager@2.1.1"
            ]
        }
    }
}

Documentation

From the project's README on GitHub, refreshed weekly. Links open on GitHub.

Contents
  1. Alertmanager MCP Server (Go)
  2. Installation
  3. Configuration
  4. Tools (12)
  5. Example Prompts
  6. Development
  7. Kubernetes / OpenShift Deployment
  8. License

Alertmanager MCP Server (Go)

A Model Context Protocol (MCP) server for Prometheus Alertmanager integration. Native Go binary with built-in Kubernetes connectivity via client-go.

Installation

npx
npx -y mcp-alertmanager@latest
MCP Client Configuration

Add to your MCP client configuration (VS Code, Cursor, Windsurf, etc.):

{
  "mcpServers": {
    "alertmanager": {
      "command": "npx",
      "args": ["-y", "mcp-alertmanager@latest"],
      "env": {
        "ALERTMANAGER_URL": "http://localhost:9093"
      }
    }
  }
}
VS Code
code --add-mcp '{"name":"alertmanager","command":"npx","args":["-y","mcp-alertmanager@latest"],"env":{"ALERTMANAGER_URL":"http://localhost:9093"}}'
Kubernetes Auto-Connect

Automatically connects to Alertmanager running in OpenShift/Kubernetes via the K8S API service proxy. Uses native kubeconfig/in-cluster config via client-go. No kubectl or port-forwarding required.

Default: openshift-monitoring/alertmanager-operated:9093

{
  "mcpServers": {
    "alertmanager": {
      "command": "npx",
      "args": ["-y", "mcp-alertmanager@latest"]
    }
  }
}
Binary

Download from GitHub Releases or build from source:

make build
./mcp-alertmanager

Configuration

Environment Variables
VariableDescription
ALERTMANAGER_URLDirect Alertmanager API URL (overrides K8S auto-connect)
CLI Flags
FlagDescriptionDefault
--urlDirect Alertmanager URL-
--namespaceKubernetes namespaceopenshift-monitoring
--serviceKubernetes service namealertmanager-operated
--service-portKubernetes service port9093
--service-schemeService scheme (http/https)https
--kubeconfigPath to kubeconfig fileauto-detect

Precedence: --url / ALERTMANAGER_URL > K8S auto-connect

Connection strategy:

  1. Direct URL (if --url or ALERTMANAGER_URL is set)
  2. K8S API proxy (auto-detect kubeconfig or in-cluster config)

Tools (12)

Alerts
ToolDescription
getAlertsGet alerts with optional filters
getAlertGroupsGet alerts grouped by routing labels
getCriticalAlertsGet critical severity alerts only
getAlertingSummarySummary: counts by severity, top alerts, namespaces
Silences
ToolDescription
getSilencesList silences by state
createSilenceCreate a silence for an alert
deleteSilenceDelete a silence by ID
Status
ToolDescription
getAlertmanagerStatusServer status, version, cluster info
getReceiversList notification receivers
Troubleshooting
ToolDescription
investigateAlertDeep investigation of a specific alert
getAlertHistoryAlert history and analysis guidance
correlateAlertsFind correlated alerts by shared labels

Example Prompts

"What alerts are currently firing?"
"Are there any critical alerts?"
"Give me a summary of the alerting status"
"Investigate the HighMemoryUsage alert"
"Create a 2-hour silence for PodCrashLooping"
"What receivers are configured?"
"Find correlated alerts to identify the root cause"
"Show me alert history for KubeNodeNotReady"

Development

Build
make build              # Build for current platform
make build-all-platforms # Cross-compile for all platforms
Container
podman build -f Containerfile -t mcp-alertmanager .

Kubernetes / OpenShift Deployment

Container Image

The container image is available on GitHub Container Registry:

ghcr.io/jeanlopezxyz/mcp-alertmanager:latest
Helm Chart

Deploy using the included Helm chart:

# Add the chart repository (or use local chart)
helm upgrade --install mcp-alertmanager ./charts/mcp-alertmanager \
  --namespace mcp-servers \
  --create-namespace \
  --set openshift=true
Helm Values
ParameterDescriptionDefault
image.registryContainer registryghcr.io
image.repositoryImage repositoryjeanlopezxyz/mcp-alertmanager
image.versionImage taglatest
openshiftEnable OpenShift Routesfalse
service.portService port8080
alertmanager.namespaceAlertmanager namespaceopenshift-monitoring
alertmanager.serviceAlertmanager service namealertmanager-operated
rbac.useClusterReaderUse cluster-reader roletrue
Example with custom Alertmanager
helm upgrade --install mcp-alertmanager ./charts/mcp-alertmanager \
  --namespace mcp-servers \
  --set openshift=true \
  --set alertmanager.url=http://alertmanager.monitoring:9093

License

MIT

Frequently asked questions

What is io.github.jeanlopezxyz/mcp-alertmanager?

A Model Context Protocol (MCP) server for Prometheus Alertmanager

How do I install io.github.jeanlopezxyz/mcp-alertmanager?

It runs on your machine. In Claude Code: claude mcp add mcp-alertmanager -- npx -y mcp-alertmanager@2.1.1. For other clients, paste the JSON configuration from this page into their MCP settings.

Does io.github.jeanlopezxyz/mcp-alertmanager need an API key?

Its registry entry lists no required key or secret. Some features may still need an account with the service it connects to.

Is io.github.jeanlopezxyz/mcp-alertmanager open source?

Yes. Its code is on GitHub under the MIT license.

Who maintains io.github.jeanlopezxyz/mcp-alertmanager?

It is published by jeanlopezxyz. AI.tn lists it but does not maintain or endorse it.

From the official MCP Registry. Listing is not an endorsement: review a server's code and permissions before giving it access to your data.