mcp-alertmanager
Enables interaction with Prometheus Alertmanager for querying alerts, managing silences, and investigating incidents. Supports direct API connection and Kubernetes auto-discovery.
README
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
| 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
推荐服务器
Baidu Map
百度地图核心API现已全面兼容MCP协议,是国内首家兼容MCP协议的地图服务商。
Playwright MCP Server
一个模型上下文协议服务器,它使大型语言模型能够通过结构化的可访问性快照与网页进行交互,而无需视觉模型或屏幕截图。
Magic Component Platform (MCP)
一个由人工智能驱动的工具,可以从自然语言描述生成现代化的用户界面组件,并与流行的集成开发环境(IDE)集成,从而简化用户界面开发流程。
Audiense Insights MCP Server
通过模型上下文协议启用与 Audiense Insights 账户的交互,从而促进营销洞察和受众数据的提取和分析,包括人口统计信息、行为和影响者互动。
VeyraX
一个单一的 MCP 工具,连接你所有喜爱的工具:Gmail、日历以及其他 40 多个工具。
graphlit-mcp-server
模型上下文协议 (MCP) 服务器实现了 MCP 客户端与 Graphlit 服务之间的集成。 除了网络爬取之外,还可以将任何内容(从 Slack 到 Gmail 再到播客订阅源)导入到 Graphlit 项目中,然后从 MCP 客户端检索相关内容。
Kagi MCP Server
一个 MCP 服务器,集成了 Kagi 搜索功能和 Claude AI,使 Claude 能够在回答需要最新信息的问题时执行实时网络搜索。
e2b-mcp-server
使用 MCP 通过 e2b 运行代码。
Neon MCP Server
用于与 Neon 管理 API 和数据库交互的 MCP 服务器
Exa MCP Server
模型上下文协议(MCP)服务器允许像 Claude 这样的 AI 助手使用 Exa AI 搜索 API 进行网络搜索。这种设置允许 AI 模型以安全和受控的方式获取实时的网络信息。