If your Prometheus is already configured as a Grafana datasource, you likely do not need this integration — the Grafana integration covers Prometheus queries through a single MCP server. Connect Prometheus directly only if you run Prometheus standalone without Grafana, or if your Prometheus is not reachable through your Grafana instance.
What this integration enables
- PromQL queries — agents run arbitrary PromQL against your Prometheus for metric diagnosis and verification
- Service health checks — agents evaluate
up,kube_pod_status_ready,kube_deployment_replicas_available, and similar series during incident investigation - Alert correlation — agents can query the metrics that triggered an alert to understand trend context
Prerequisites
- A running Prometheus instance reachable from your network
- The
prometheus-mcpserver running and reachable from sureops - Optional: bearer token or basic auth credentials if your Prometheus instance requires authentication
Setup
1
Stand up prometheus-mcp
Deploy
prometheus-mcp pointed at your Prometheus base URL. If you’re using the sureops demo environment, prometheus-mcp is already provisioned in-cluster — you can skip this step.For your own environment, deploy prometheus-mcp with your Prometheus URL and any required auth credentials. The sureops MCP setup guide has Helm and Docker Compose examples.2
Enter Prometheus URL and auth
In sureops, go to Settings → Integrations and click Connect next to Prometheus.Fill in:
- Prometheus URL — the base URL of your Prometheus instance (e.g.
http://prometheus.svc.cluster.local:9090) - Auth Method — one of
none,basic, orbearer. Defaults tonone. - Bearer Token — only if your Prometheus uses bearer auth
- Basic Auth Username / Password — only if your Prometheus uses basic auth
3
Enter MCP endpoint
Fill in:
- Prometheus MCP Endpoint — the URL of your running
prometheus-mcpserver - MCP Connection Token — optional bearer token if your MCP server requires its own auth