mcpField
P
Prometheus MCP Server

Prometheus MCP Server

Local
pab1it0.github.ioDeveloper Tools521Updated 1d ago
RepositoryVisit website

About Prometheus MCP Server

Prometheus MCP Server exposes Prometheus metrics and PromQL queries to AI assistants through MCP. It supports querying, metric discovery, and metadata lookup, with configurable tools and authentication options.

Key features

  1. 01Run instant PromQL queries
  2. 02Run time-range queries
  3. 03Browse metrics with filtering
  4. 04Retrieve metric metadata
  5. 05Inspect scrape targets
  6. 06Configure tools and authentication

Use cases

  1. 01Investigate a metric at a specific time
  2. 02Analyze metric trends over a time range
  3. 03Find available metrics and their metadata
  4. 04Check Prometheus scrape target status

MCP support

Acts as an MCP server, exposing Prometheus query, discovery, metadata, target, and health-check tools to MCP clients.

#devops#ai#mcp#prometheus#llm

Configuration

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

mcp.json · Universal config
{
  "mcpServers": {
    "prometheus": {
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "-e",
        "PROMETHEUS_URL",
        "-e",
        "PROMETHEUS_URL_SSL_VERIFY",
        "-e",
        "PROMETHEUS_DISABLE_LINKS",
        "-e",
        "PROMETHEUS_USERNAME",
        "-e",
        "PROMETHEUS_PASSWORD",
        "-e",
        "PROMETHEUS_TOKEN",
        "-e",
        "ORG_ID",
        "-e",
        "PROMETHEUS_CLIENT_CERT",
        "-e",
        "PROMETHEUS_CLIENT_KEY",
        "-e",
        "PROMETHEUS_MCP_SERVER_TRANSPORT",
        "-e",
        "PROMETHEUS_MCP_BIND_HOST",
        "-e",
        "PROMETHEUS_MCP_BIND_PORT",
        "-e",
        "PROMETHEUS_MCP_STATELESS_HTTP",
        "-e",
        "PROMETHEUS_CUSTOM_HEADERS",
        "ghcr.io/pab1it0/prometheus-mcp-server:1.6.2"
      ],
      "env": {
        "PROMETHEUS_URL": "<PROMETHEUS_URL>",
        "PROMETHEUS_URL_SSL_VERIFY": "<PROMETHEUS_URL_SSL_VERIFY>",
        "PROMETHEUS_DISABLE_LINKS": "<PROMETHEUS_DISABLE_LINKS>",
        "PROMETHEUS_USERNAME": "<PROMETHEUS_USERNAME>",
        "PROMETHEUS_PASSWORD": "<PROMETHEUS_PASSWORD>",
        "PROMETHEUS_TOKEN": "<PROMETHEUS_TOKEN>",
        "ORG_ID": "<ORG_ID>",
        "PROMETHEUS_CLIENT_CERT": "<PROMETHEUS_CLIENT_CERT>",
        "PROMETHEUS_CLIENT_KEY": "<PROMETHEUS_CLIENT_KEY>",
        "PROMETHEUS_MCP_SERVER_TRANSPORT": "<PROMETHEUS_MCP_SERVER_TRANSPORT>",
        "PROMETHEUS_MCP_BIND_HOST": "<PROMETHEUS_MCP_BIND_HOST>",
        "PROMETHEUS_MCP_BIND_PORT": "<PROMETHEUS_MCP_BIND_PORT>",
        "PROMETHEUS_MCP_STATELESS_HTTP": "<PROMETHEUS_MCP_STATELESS_HTTP>",
        "PROMETHEUS_CUSTOM_HEADERS": "<PROMETHEUS_CUSTOM_HEADERS>"
      }
    }
  }
}
Run commanddocker run -i --rm -e PROMETHEUS_URL -e PROMETHEUS_URL_SSL_VERIFY -e PROMETHEUS_DISABLE_LINKS -e PROMETHEUS_USERNAME -e PROMETHEUS_PASSWORD -e PROMETHEUS_TOKEN -e ORG_ID -e PROMETHEUS_CLIENT_CERT -e PROMETHEUS_CLIENT_KEY -e PROMETHEUS_MCP_SERVER_TRANSPORT -e PROMETHEUS_MCP_BIND_HOST -e PROMETHEUS_MCP_BIND_PORT -e PROMETHEUS_MCP_STATELESS_HTTP -e PROMETHEUS_CUSTOM_HEADERS ghcr.io/pab1it0/prometheus-mcp-server:1.6.2
Environment variables to set
PROMETHEUS_URLPrometheus server URL (e.g., http://localhost:9090)
PROMETHEUS_URL_SSL_VERIFYSet to False to disable SSL verification
PROMETHEUS_DISABLE_LINKSSet to True to disable Prometheus UI links in query results (saves context tokens in MCP clients)
PROMETHEUS_USERNAMEUsername for Prometheus basic authentication
PROMETHEUS_PASSWORDSecretPassword for Prometheus basic authentication
PROMETHEUS_TOKENSecretBearer token for Prometheus authentication
ORG_IDOrganization ID for multi-tenant Prometheus setups
PROMETHEUS_CLIENT_CERTPath to client certificate file for mutual TLS authentication
PROMETHEUS_CLIENT_KEYSecretPath to client private key file for mutual TLS authentication
PROMETHEUS_MCP_SERVER_TRANSPORTMCP server transport type (stdio, http, or sse)
PROMETHEUS_MCP_BIND_HOSTHost address for HTTP/SSE transport (default: 127.0.0.1)
PROMETHEUS_MCP_BIND_PORTPort number for HTTP/SSE transport (default: 8080)
PROMETHEUS_MCP_STATELESS_HTTPEnable stateless HTTP mode for multi-replica support (default: false)
PROMETHEUS_CUSTOM_HEADERSCustom headers as JSON string to include in Prometheus requests

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
ocighcr.io/pab1it0/prometheus-mcp-server:1.6.2

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

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:

{
  "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:

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:

{
  "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:

# With environment variables
docker run -i --rm \
  -e PROMETHEUS_URL="http://your-prometheus:9090" \
  ghcr.io/pab1it0/prometheus-mcp-server:latest

# With authentication
docker 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:

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:

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:

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:

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

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

uv venv
source .venv/bin/activate  # On Unix/macOS
.venv\Scripts\activate     # On Windows
uv pip install -e .
Testing

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

Run the tests with pytest:

# Install development dependencies
uv pip install -e ".[dev]"

# Run the tests
pytest

# Run with coverage report
pytest --cov=src --cov-report=term-missing

When adding new features, please also add corresponding tests.

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.