MCP Server
MCP Server
SRE Portal includes built-in Model Context Protocol (MCP) servers that let AI assistants query DNS records and alerts.
Endpoints
Four MCP servers are mounted on the same port as the web UI (8090 by default). All use Streamable HTTP transport.
| Endpoint | Description |
|---|---|
/mcp | DNS and portal tools (same as /mcp/dns; kept for backward compatibility) |
/mcp/dns | DNS and portal tools |
/mcp/alerts | Alertmanager alerts tools |
/mcp/metrics | Prometheus metrics tools |
/mcp/releases | Release tracking tools |
Base URL: http://<sreportal-host>:8090.
Available Tools
DNS / Portals (at /mcp and /mcp/dns)
| Tool | Description | Parameters |
|---|---|---|
search_fqdns | Search for FQDNs matching criteria | query, source, group, portal, namespace |
list_portals | List all available portals | (none) |
get_fqdn_details | Get detailed info about a specific FQDN | fqdn (required) |
Alerts (at /mcp/alerts)
| Tool | Description | Parameters |
|---|---|---|
list_alerts | List Alertmanager resources and their active alerts (optionally filtered by portal, search, state) | portal, search, state (optional) |
Metrics (at /mcp/metrics)
| Tool | Description | Parameters |
|---|---|---|
list_metrics | List Prometheus metrics from the operator’s metrics registry | (none) |
Releases (at /mcp/releases)
| Tool | Description | Parameters |
|---|---|---|
list_releases | List release entries for a day | day (optional, YYYY-MM-DD; defaults to the latest day with data). Response includes previous_day and next_day |
Setup
Claude Code
DNS and portals:
claude mcp add sreportal --transport http http://localhost:8090/mcpAlerts:
claude mcp add sreportal-alerts --transport http http://localhost:8090/mcp/alertsMetrics:
claude mcp add sreportal-metrics --transport http http://localhost:8090/mcp/metricsReleases:
claude mcp add sreportal-releases --transport http http://localhost:8090/mcp/releasesClaude Desktop
Add to your claude_desktop_config.json:
{
"mcpServers": {
"sreportal": {
"transport": "http",
"url": "http://localhost:8090/mcp"
},
"sreportal-alerts": {
"transport": "http",
"url": "http://localhost:8090/mcp/alerts"
},
"sreportal-metrics": {
"transport": "http",
"url": "http://localhost:8090/mcp/metrics"
},
"sreportal-releases": {
"transport": "http",
"url": "http://localhost:8090/mcp/releases"
}
}
}Cursor
Add MCP servers:
- DNS/portals: Type URL, URL:
http://localhost:8090/mcp(orhttp://localhost:8090/mcp/dns) - Alerts: Type URL, URL:
http://localhost:8090/mcp/alerts - Metrics: Type URL, URL:
http://localhost:8090/mcp/metrics - Releases: Type URL, URL:
http://localhost:8090/mcp/releases
Example Queries
Once connected to the DNS server, you can ask:
- “List all available portals”
- “Search for FQDNs containing
api” - “Get details for
api.example.com” - “Show all external-dns entries in the production portal”
- “What DNS records are in the monitoring group?”
With the alerts server:
- “List active alerts for the main portal”
- “Show firing alerts”
- “List alerts containing ‘disk’”
With the metrics server:
- “Show me all SRE Portal metrics”
- “What’s the current reconciliation rate?”
With the releases server:
- “List today’s releases”
- “Add a deployment release for v2.1.0 from CI/CD”
- “Show releases for 2026-03-19”
In-App Help
The web UI includes a Help page at /help with the same setup instructions and a live display of all MCP endpoint URLs and their tools.