Config is the same across clients — only the file and path differ.
{
"mcpServers": {
"alertmanager": {
"env": {
"ALERTMANAGER_URL": "http://localhost:9093"
},
"args": [
"-y",
"mcp-alertmanager@latest"
],
"command": "npx"
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
A Model Context Protocol (MCP) server for Prometheus Alertmanager integration. Native Go binary with built-in Kubernetes connectivity via client-go.
Run this in your terminal to verify the server starts. Then let us know if it worked — your result helps other developers.
npx -y 'mcp-alertmanager' 2>&1 | head -1 && echo "✓ Server started successfully"
After testing, let us know if it worked:
Five weighted categories — click any category to see the underlying evidence.
No known CVEs.
Checked mcp-alertmanager against OSV.dev.
Be the first to review
Have you used this server?
Share your experience — it helps other developers decide.
Sign in to write a review.
Others in devops / analytics
MCP server for using the GitLab API
MCP Server for kubernetes management commands
MCP server that enables AI agents to perform comprehensive web audits using Google Lighthouse with 13+ tools for performance, accessibility, SEO, and security analysis.
MCP server for Dynatrace Managed to access logs, events, and metrics.
MCP Security Weekly
Get CVE alerts and security updates for Alertmanager MCP Server and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
A Model Context Protocol (MCP) server for Prometheus Alertmanager integration. Native Go binary with built-in Kubernetes connectivity via client-go.
npx -y mcp-alertmanager@latest
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"
}
}
}
}
code --add-mcp '{"name":"alertmanager","command":"npx","args":["-y","mcp-alertmanager@latest"],"env":{"ALERTMANAGER_URL":"http://localhost:9093"}}'
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"]
}
}
}
Download from GitHub Releases or build from source:
make build
./mcp-alertmanager
| Variable | Description |
|---|---|
ALERTMANAGER_URL | Direct Alertmanager API URL (overrides K8S auto-connect) |
| 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:
--url or ALERTMANAGER_URL is set)| 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 |
| Tool | Description |
|---|---|
getSilences | List silences by state |
createSilence | Create a silence for an alert |
deleteSilence | Delete a silence by ID |
| Tool | Description |
|---|---|
getAlertmanagerStatus | Server status, version, cluster info |
getReceivers | List notification receivers |
| Tool | Description |
|---|---|
investigateAlert | Deep investigation of a specific alert |
getAlertHistory | Alert history and analysis guidance |
correlateAlerts | Find correlated alerts by shared labels |
"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"
``
... [View full README on GitHub](https://github.com/jeanlopezxyz/mcp-alertmanager#readme)