Prometheus MCP Server
MCP server that enables AI assistants to query and analyze Prometheus metrics through PromQL, with support for metric discovery and authentication.
README
Prometheus MCP Server
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
<details> <summary><b>Claude Desktop</b></summary>
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>"
}
}
}
}
</details>
<details> <summary><b>Claude Code</b></summary>
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
</details>
<details> <summary><b>VS Code / Cursor / Windsurf</b></summary>
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>"
}
}
}
</details>
<details> <summary><b>Docker Desktop</b></summary>
The easiest way to run the Prometheus MCP server is through Docker Desktop:
<a href="https://hub.docker.com/open-desktop?url=https://open.docker.com/dashboard/mcp/servers/id/prometheus/config?enable=true"> <img src="https://img.shields.io/badge/+%20Add%20to-Docker%20Desktop-2496ED?style=for-the-badge&logo=docker&logoColor=white" alt="Add to Docker Desktop" /> </a>
-
Via MCP Catalog: Visit the Prometheus MCP Server on Docker Hub and click the button above
-
Via MCP Toolkit: Use Docker Desktop's MCP Toolkit extension to discover and install the server
-
Configure your connection using environment variables (see Configuration Options below)
</details>
<details> <summary><b>Manual Docker Setup</b></summary>
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
</details>
<details> <summary><b>Helm Chart (Kubernetes)</b></summary>
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.0.0 \
--set prometheus.url="http://prometheus:9090"
With authentication:
helm install prometheus-mcp-server \
oci://ghcr.io/pab1it0/charts/prometheus-mcp-server \
--version 1.0.0 \
--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.0.0 \
-f values.yaml
See the chart values for all available configuration options. </details>
Configuration Options
| Variable | Description | Required |
|---|---|---|
PROMETHEUS_URL |
URL of your Prometheus server | Yes |
PROMETHEUS_URL_SSL_VERIFY |
Set to False to disable SSL verification | No |
PROMETHEUS_DISABLE_LINKS |
Set to True to disable Prometheus UI links in query results (saves context tokens) | No |
PROMETHEUS_REQUEST_TIMEOUT |
Request timeout in seconds to prevent hanging requests (DDoS protection) | No (default: 30) |
PROMETHEUS_USERNAME |
Username for basic authentication | No |
PROMETHEUS_PASSWORD |
Password for basic authentication | No |
PROMETHEUS_TOKEN |
Bearer token for authentication | No |
PROMETHEUS_CLIENT_CERT |
Path to client certificate file for mutual TLS authentication | No |
PROMETHEUS_CLIENT_KEY |
Path to client private key file for mutual TLS authentication | No |
REQUESTS_CA_BUNDLE |
Path to CA bundle file for verifying the server's TLS certificate (standard requests library env var) |
No |
ORG_ID |
Organization ID for multi-tenant setups | No |
PROMETHEUS_MCP_SERVER_TRANSPORT |
Transport mode (stdio, http, sse) | No (default: stdio) |
PROMETHEUS_MCP_BIND_HOST |
Host for HTTP transport | No (default: 127.0.0.1) |
PROMETHEUS_MCP_BIND_PORT |
Port for HTTP transport | No (default: 8080) |
PROMETHEUS_MCP_STATELESS_HTTP |
Enable stateless HTTP mode for multi-replica support | No (default: False) |
PROMETHEUS_CUSTOM_HEADERS |
Custom headers as JSON string | No |
TOOL_PREFIX |
Prefix for all tool names (e.g., staging results in staging_execute_query). Useful for running multiple instances targeting different environments in Cursor |
No |
Available Tools
| Tool | Category | Description |
|---|---|---|
health_check |
System | Health check endpoint for container monitoring and status verification |
execute_query |
Query | Execute a PromQL instant query against Prometheus |
execute_range_query |
Query | Execute a PromQL range query with start time, end time, and step interval |
list_metrics |
Discovery | List all available metrics in Prometheus with pagination and filtering support |
get_metric_metadata |
Discovery | Get metadata for one metric or bulk metadata with optional filtering |
get_targets |
Discovery | Get information about all scrape targets |
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
- 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
Recommended Servers
playwright-mcp
A Model Context Protocol server that enables LLMs to interact with web pages through structured accessibility snapshots without requiring vision models or screenshots.
Magic Component Platform (MCP)
An AI-powered tool that generates modern UI components from natural language descriptions, integrating with popular IDEs to streamline UI development workflow.
Audiense Insights MCP Server
Enables interaction with Audiense Insights accounts via the Model Context Protocol, facilitating the extraction and analysis of marketing insights and audience data including demographics, behavior, and influencer engagement.
VeyraX MCP
Single MCP tool to connect all your favorite tools: Gmail, Calendar and 40 more.
graphlit-mcp-server
The Model Context Protocol (MCP) Server enables integration between MCP clients and the Graphlit service. Ingest anything from Slack to Gmail to podcast feeds, in addition to web crawling, into a Graphlit project - and then retrieve relevant contents from the MCP client.
Kagi MCP Server
An MCP server that integrates Kagi search capabilities with Claude AI, enabling Claude to perform real-time web searches when answering questions that require up-to-date information.
Neon Database
MCP server for interacting with Neon Management API and databases
E2B
Using MCP to run code via e2b.
Exa Search
A Model Context Protocol (MCP) server lets AI assistants like Claude use the Exa AI Search API for web searches. This setup allows AI models to get real-time web information in a safe and controlled way.
Qdrant Server
This repository is an example of how to create a MCP server for Qdrant, a vector search engine.