About mcp-alertmanager
mcp-alertmanager is a Go MCP server for operating Prometheus Alertmanager, aimed at monitoring and platform teams. It provides alert, silence, status, and troubleshooting tools, with direct URL or Kubernetes connectivity.
Key features
- 01Filter and group alerts
- 02Create and delete silences
- 03Inspect status and receivers
- 04Investigate and correlate alerts
Use cases
- 01Review active or critical alerts
- 02Silence an alert during maintenance
- 03Trace related alerts during an incident
MCP support
Exposes 12 Alertmanager tools to MCP clients, including alert queries, silence management, status checks, and investigation. Connects through a direct API URL or the Kubernetes API service proxy.
Configuration
Local server config is the same for every client. Copy it into your client’s MCP config file.
Tools
Local servers expose tools only once running on your machine, and the maintainer has not provided a tool list.
Details
From the project READMEAlertmanager 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
| Variable | Description |
|---|---|
ALERTMANAGER_URL | Direct Alertmanager API URL (overrides K8S auto-connect) |
CLI Flags
| Flag | Description | Default |
|---|---|---|
--url | Direct Alertmanager URL | - |
--namespace | Kubernetes namespace | openshift-monitoring |
--service | Kubernetes service name | alertmanager-operated |
--service-port | Kubernetes service port | 9093 |
--service-scheme | Service scheme (http/https) | https |
--kubeconfig | Path to kubeconfig file | auto-detect |
Precedence: --url / ALERTMANAGER_URL > K8S auto-connect
Connection strategy:
- Direct URL (if
--urlorALERTMANAGER_URLis set) - K8S API proxy (auto-detect kubeconfig or in-cluster config)
Tools (12)
Alerts
| Tool | Description |
|---|---|
getAlerts | Get alerts with optional filters |
getAlertGroups | Get alerts grouped by routing labels |
getCriticalAlerts | Get critical severity alerts only |
getAlertingSummary | Summary: counts by severity, top alerts, namespaces |
Silences
| Tool | Description |
|---|---|
getSilences | List silences by state |
createSilence | Create a silence for an alert |
deleteSilence | Delete a silence by ID |
Status
| Tool | Description |
|---|---|
getAlertmanagerStatus | Server status, version, cluster info |
getReceivers | List notification receivers |
Troubleshooting
| Tool | Description |
|---|---|
investigateAlert | Deep investigation of a specific alert |
getAlertHistory | Alert history and analysis guidance |
correlateAlerts | Find 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
| Parameter | Description | Default |
|---|---|---|
image.registry | Container registry | ghcr.io |
image.repository | Image repository | jeanlopezxyz/mcp-alertmanager |
image.version | Image tag | latest |
openshift | Enable OpenShift Routes | false |
service.port | Service port | 8080 |
alertmanager.namespace | Alertmanager namespace | openshift-monitoring |
alertmanager.service | Alertmanager service name | alertmanager-operated |
rbac.useClusterReader | Use cluster-reader role | true |
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
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.