Mcp Prometheus

io.github.jeanlopezxyzPublished by GitHub account jeanlopezxyzv2.1.1Updated Oct 24, 2026

A Model Context Protocol (MCP) server for Prometheus monitoring

The publisher's own server: Prometheus MCP

Overview

AI-generated overview

A local MCP server that connects an assistant to Prometheus so it can run PromQL queries and diagnose Kubernetes/OpenShift cluster health.

What you can do
Run PromQL instant and range queries against Prometheus and compare metrics between two time periods. Inspect scrape targets, alerting and recording rules, and server version and runtime status. Get a cluster health overview and diagnose specific nodes or namespaces. Find top CPU, memory and network consumers and investigate individual pods.
When to use it
Useful when you want an assistant to answer questions about Prometheus metrics, cluster health, resource usage or pod problems in a Kubernetes or OpenShift environment without running kubectl or port-forwarding yourself.
Requirements
Runs locally via npx (Node.js) or a Go binary. Needs a reachable Prometheus endpoint, set through the PROMETHEUS_URL environment variable or the --url flag, or Kubernetes access via kubeconfig or in-cluster config for auto-connect through the K8s API service proxy. Namespace, service and port can be set with CLI flags.
Before you install
Kubernetes auto-connect uses your kubeconfig or in-cluster credentials, so the assistant can reach cluster monitoring data under your identity. The README mentions a cluster-reader RBAC role for deployments. Point it only at Prometheus instances you are authorized to query.

Installation

In SourceWeft

  1. Open Mcp Prometheus in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

Prometheus MCP Server (Go)

[License: MIT] [npm version] [Go] [GitHub release]

A Model Context Protocol (MCP) server for Prometheus integration. Native Go binary with built-in Kubernetes connectivity via client-go.

Installation

npx

bash
npx -y mcp-prometheus@latest

MCP Client Configuration

Add to your MCP client configuration (VS Code, Cursor, Windsurf, etc.):

json
{  "mcpServers": {    "prometheus": {      "command": "npx",      "args": ["-y", "mcp-prometheus@latest"],      "env": {        "PROMETHEUS_URL": "http://localhost:9090"      }    }  }}

VS Code

shell
code --add-mcp '{"name":"prometheus","command":"npx","args":["-y","mcp-prometheus@latest"],"env":{"PROMETHEUS_URL":"http://localhost:9090"}}'

Kubernetes Auto-Connect

Automatically connects to Prometheus 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/prometheus-operated:9090

json
{  "mcpServers": {    "prometheus": {      "command": "npx",      "args": ["-y", "mcp-prometheus@latest"]    }  }}

Binary

Download from GitHub Releases or build from source:

bash
make build./mcp-prometheus

Configuration

Environment Variables

VariableDescription
PROMETHEUS_URLDirect Prometheus API URL (overrides K8S auto-connect)

CLI Flags

FlagDescriptionDefault
--urlDirect Prometheus URL-
--namespaceKubernetes namespaceopenshift-monitoring
--serviceKubernetes service nameprometheus-operated
--service-portKubernetes service port9090
--service-schemeService scheme (http/https)https
--kubeconfigPath to kubeconfig fileauto-detect

Precedence: --url / PROMETHEUS_URL > K8S auto-connect

Connection strategy:

  1. Direct URL (if --url or PROMETHEUS_URL is set)
  2. K8S API proxy (auto-detect kubeconfig or in-cluster config)

Tools (11)

Basic Queries

ToolDescription
queryExecute a PromQL instant query
queryRangeExecute a PromQL range query over time
getTargetsGet scrape targets status
getRulesGet alerting and recording rules
getPrometheusStatusGet server version and runtime info

Cluster Diagnostics

ToolDescription
getClusterHealthOverviewComprehensive cluster health overview
diagnoseNodeDiagnose a specific node's health
diagnoseNamespaceDiagnose a namespace's health

Resource Analysis

ToolDescription
getTopResourceConsumersTop CPU/memory/network consumers
investigatePodDeep investigation of a specific pod
compareTimeRangesCompare metrics between two time periods

Example Prompts

"What's the current CPU usage across all nodes?""Show me the cluster health overview""Which pods are using the most memory?""Diagnose node worker-1""Are all scrape targets healthy?""Compare CPU usage now vs 24 hours ago""Investigate pod my-app in namespace production""What alerting rules are defined?"

Development

Build

bash
make build              # Build for current platformmake build-all-platforms # Cross-compile for all platforms

Container

bash
podman build -f Containerfile -t mcp-prometheus .

Kubernetes / OpenShift Deployment

Container Image

The container image is available on GitHub Container Registry:

ghcr.io/jeanlopezxyz/mcp-prometheus:latest

Helm Chart

Deploy using the included Helm chart:

bash
# Add the chart repository (or use local chart)helm upgrade --install mcp-prometheus ./charts/mcp-prometheus \  --namespace mcp-servers \  --create-namespace \  --set openshift=true
Helm Values
ParameterDescriptionDefault
image.registryContainer registryghcr.io
image.repositoryImage repositoryjeanlopezxyz/mcp-prometheus
image.versionImage taglatest
openshiftEnable OpenShift Routesfalse
service.portService port8080
prometheus.namespacePrometheus namespaceopenshift-monitoring
prometheus.servicePrometheus service nameprometheus-operated
rbac.useClusterReaderUse cluster-reader roletrue
Example with custom Prometheus
bash
helm upgrade --install mcp-prometheus ./charts/mcp-prometheus \  --namespace mcp-servers \  --set openshift=true \  --set prometheus.url=http://prometheus.monitoring:9090

License

MIT

Source: README.md at commit 4b7c47b

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v2.1.1LatestSep 16, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

Other Prometheus integrations