Prometheus MCP Server

io.github.pab1it0Published by GitHub account pab1it0v1.6.2Updated Oct 24, 2026

MCP server providing Prometheus metrics access and PromQL query execution for AI assistants

The publisher's own server: Prometheus MCP

VerifiedSTDIODesktop onlySecurity & MonitoringData & Analytics

Overview

AI-generated overview

Connects an AI assistant to a Prometheus server so it can run PromQL instant and range queries and explore available metrics and scrape targets.

What you can do
  • Run PromQL instant and range queries against Prometheus, with configurable step intervals
  • List available metrics and fetch metadata for one or many metrics, including search by name or description
  • Inspect scrape targets with state and scrape pool filtering and pagination
  • Check server health and optionally open query results in the Prometheus UI
When to use it
Useful when you want an assistant to investigate metrics, dashboards or incidents directly in Prometheus, or to explore which metrics exist before writing queries, without copying PromQL output by hand.
Requirements
Runs as a local process, typically the published container image via Docker (a Helm chart is also offered for Kubernetes). Needs a reachable Prometheus server URL in PROMETHEUS_URL; optional basic auth via PROMETHEUS_USERNAME and PROMETHEUS_PASSWORD, bearer auth via PROMETHEUS_TOKEN, mTLS via PROMETHEUS_CLIENT_CERT and PROMETHEUS_CLIENT_KEY, and custom headers via PROMETHEUS_CUSTOM_HEADERS.
Before you install
Requires credentials for your Prometheus instance: PROMETHEUS_PASSWORD, PROMETHEUS_TOKEN and the client key path PROMETHEUS_CLIENT_KEY are secrets, so pass them through the environment rather than committing them. PROMETHEUS_URL_SSL_VERIFY can be set to False, which disables TLS certificate checks. Query results and metric metadata are sent to the AI client, and Prometheus UI links are included unless PROMETHEUS_DISABLE_LINKS is set.

Installation

In SourceWeft

  1. Open Prometheus MCP Server 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

[GitHub Container Registry] [Helm Chart] [GitHub Release] [Codecov] [Python] [License]

Give AI assistants the power to query your Prometheus metrics.

A Model Context Protocol (MCP) server that provides access to your Prometheus metrics and queries through standardized MCP interfaces, allowing AI assistants to execute PromQL queries and analyze your metrics data.

Getting Started

Prerequisites

  • Prometheus server accessible from your environment
  • MCP-compatible client (Claude Desktop, VS Code, Cursor, Windsurf, etc.)

Installation Methods

Claude Desktop

Add to your Claude Desktop configuration:

json
{  "mcpServers": {    "prometheus": {      "command": "docker",      "args": [        "run",        "-i",        "--rm",        "-e",        "PROMETHEUS_URL",        "ghcr.io/pab1it0/prometheus-mcp-server:latest"      ],      "env": {        "PROMETHEUS_URL": "<your-prometheus-url>"      }    }  }}
Claude Code

Install via the Claude Code CLI:

bash
claude mcp add prometheus --env PROMETHEUS_URL=http://your-prometheus:9090 -- docker run -i --rm -e PROMETHEUS_URL ghcr.io/pab1it0/prometheus-mcp-server:latest
VS Code / Cursor / Windsurf

Add to your MCP settings in the respective IDE:

json
{  "prometheus": {    "command": "docker",    "args": [      "run",      "-i",      "--rm",      "-e",      "PROMETHEUS_URL",      "ghcr.io/pab1it0/prometheus-mcp-server:latest"    ],    "env": {      "PROMETHEUS_URL": "<your-prometheus-url>"    }  }}
Docker Desktop

The easiest way to run the Prometheus MCP server is through Docker Desktop:

[Add to Docker Desktop]
  1. Via MCP Catalog: Visit the Prometheus MCP Server on Docker Hub and click the button above

  2. Via MCP Toolkit: Use Docker Desktop's MCP Toolkit extension to discover and install the server

  3. Configure your connection using environment variables (see Configuration Options below)

Manual Docker Setup

Run directly with Docker:

bash
# With environment variablesdocker run -i --rm \  -e PROMETHEUS_URL="http://your-prometheus:9090" \  ghcr.io/pab1it0/prometheus-mcp-server:latest
# With authenticationdocker run -i --rm \  -e PROMETHEUS_URL="http://your-prometheus:9090" \  -e PROMETHEUS_USERNAME="admin" \  -e PROMETHEUS_PASSWORD="password" \  ghcr.io/pab1it0/prometheus-mcp-server:latest
Helm Chart (Kubernetes)

Deploy to Kubernetes using the Helm chart from the OCI registry:

bash
helm install prometheus-mcp-server \  oci://ghcr.io/pab1it0/charts/prometheus-mcp-server \  --version 1.1.1 \  --set prometheus.url="http://prometheus:9090"

With authentication:

bash
helm install prometheus-mcp-server \  oci://ghcr.io/pab1it0/charts/prometheus-mcp-server \  --version 1.1.1 \  --set prometheus.url="http://prometheus:9090" \  --set auth.username="admin" \  --set auth.password="secret"

With a custom values file:

bash
helm install prometheus-mcp-server \  oci://ghcr.io/pab1it0/charts/prometheus-mcp-server \  --version 1.1.1 \  -f values.yaml

See the chart values for all available configuration options.

Configuration Options

VariableDescriptionRequired
PROMETHEUS_URLURL of your Prometheus serverYes
PROMETHEUS_URL_SSL_VERIFYSet to False to disable SSL verificationNo
PROMETHEUS_DISABLE_LINKSSet to True to disable Prometheus UI links in query results (saves context tokens)No
PROMETHEUS_REQUEST_TIMEOUTRequest timeout in seconds to prevent hanging requests (DDoS protection)No (default: 30)
PROMETHEUS_USERNAMEUsername for basic authenticationNo
PROMETHEUS_PASSWORDPassword for basic authenticationNo
PROMETHEUS_TOKENBearer token for authenticationNo
PROMETHEUS_CLIENT_CERTPath to client certificate file for mutual TLS authenticationNo
PROMETHEUS_CLIENT_KEYPath to client private key file for mutual TLS authenticationNo
REQUESTS_CA_BUNDLEPath to CA bundle file for verifying the server's TLS certificate (standard requests library env var)No
ORG_IDOrganization ID for multi-tenant setupsNo
PROMETHEUS_MCP_SERVER_TRANSPORTTransport mode (stdio, http, sse)No (default: stdio)
PROMETHEUS_MCP_BIND_HOSTHost for HTTP transportNo (default: 127.0.0.1)
PROMETHEUS_MCP_BIND_PORTPort for HTTP transportNo (default: 8080)
PROMETHEUS_MCP_STATELESS_HTTPEnable stateless HTTP mode for multi-replica supportNo (default: False)
PROMETHEUS_CUSTOM_HEADERSCustom headers as JSON stringNo
TOOL_PREFIXPrefix for all tool names (e.g., staging results in staging_execute_query). Useful for running multiple instances targeting different environments in CursorNo

Available Tools

ToolCategoryDescription
health_checkSystemHealth check endpoint for container monitoring and status verification
execute_queryQueryExecute a PromQL instant query against Prometheus
execute_range_queryQueryExecute a PromQL range query with start time, end time, and step interval
list_metricsDiscoveryList all available metrics in Prometheus with pagination and filtering support
get_metric_metadataDiscoveryGet metadata for one metric or bulk metadata with optional filtering
get_targetsDiscoveryGet scrape targets, with server-side state/scrape_pool filtering and optional pagination

The list of tools is configurable, so you can choose which tools you want to make available to the MCP client. This is useful if you don't use certain functionality or if you don't want to take up too much of the context window.

Features

  • Execute PromQL queries against Prometheus
  • Discover and explore metrics
    • List available metrics
    • Get metadata for specific metrics
    • Search metric metadata by name or description in a single call
    • View instant query results
    • View range query results with different step intervals
    • Open range query results in the Prometheus UI with the same time window and resolution
  • Authentication support
    • Basic auth from environment variables
    • Bearer token auth from environment variables
  • Docker containerization support
  • Provide interactive tools for AI assistants

Development

Contributions are welcome! Please see our Contributing Guide for detailed information on how to get started, coding standards, and the pull request process.

This project uses uv to manage dependencies. Install uv following the instructions for your platform:

bash
curl -LsSf https://astral.sh/uv/install.sh | sh

You can then create a virtual environment and install the dependencies with:

bash
uv venvsource .venv/bin/activate  # On Unix/macOS.venv\Scripts\activate     # On Windowsuv pip install -e .

Testing

The project includes a comprehensive test suite that ensures functionality and helps prevent regressions.

Run the tests with pytest:

bash
# Install development dependenciesuv pip install -e ".[dev]"
# Run the testspytest
# Run with coverage reportpytest --cov=src --cov-report=term-missing

When adding new features, please also add corresponding tests.

License

MIT


Source: README.md at commit a6bc50b

Tools

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

Version history

1
  1. v1.6.2LatestSep 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