mcpField
M
mcp-prometheus

mcp-prometheus

Local
github.com/jeanlopezxyzData & Analytics0Updated 38w ago

About mcp-prometheus

mcp-prometheus is a Go MCP server that gives clients access to Prometheus queries, status, rules, targets, and Kubernetes diagnostics. It connects directly to a configured Prometheus URL or through the Kubernetes API proxy.

Key features

  1. 01PromQL instant and range queries
  2. 02Target, rule, and server status checks
  3. 03Cluster, node, and namespace diagnostics
  4. 04CPU, memory, and network analysis
  5. 05Kubernetes API proxy connectivity

Use cases

  1. 01Inspect Prometheus metrics and scrape targets
  2. 02Review cluster or node health
  3. 03Investigate pod resource use
  4. 04Compare metrics across time ranges

MCP support

The MCP server exposes 11 Prometheus query, status, and diagnostic tools to MCP clients. It connects through a direct Prometheus URL or Kubernetes API proxy.

Configuration

Local server config is the same for every client. Copy it into your client’s MCP config file.

mcp.json · Universal config
{
"mcpServers": {
"jeanlopezxyz-mcp-prometheus": {
"command": "npx",
"args": [
"-y",
"mcp-prometheus"
]
}
}
}
Run commandnpx -y mcp-prometheus

Local servers need a runtime on your machine (e.g. Node.js 18+). Config file locations differ by client; see your client’s docs.

Packages
npmmcp-prometheus2.1.1

Tools

No tool list yet

Local servers expose tools only once running on your machine, and the maintainer has not provided a tool list.

Details

From the project 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
npx -y mcp-prometheus@latest
MCP Client Configuration

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

{
  "mcpServers": {
    "prometheus": {
      "command": "npx",
      "args": ["-y", "mcp-prometheus@latest"],
      "env": {
        "PROMETHEUS_URL": "http://localhost:9090"
      }
    }
  }
}
VS Code
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

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

Download from GitHub Releases or build from source:

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
make build              # Build for current platform
make build-all-platforms # Cross-compile for all platforms
Container
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:

# 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
helm upgrade --install mcp-prometheus ./charts/mcp-prometheus \
  --namespace mcp-servers \
  --set openshift=true \
  --set prometheus.url=http://prometheus.monitoring:9090

License

MIT

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.