mshegolev/prometheus-mcp
Provides tools for querying Prometheus metrics with PromQL, listing available metric names, inspecting active alerts, and exploring scrape targets.
prometheus-mcp
MCP server for Prometheus metrics and observability. Give Claude (or any MCP-capable agent) read access to your Prometheus instance — query metrics with PromQL, inspect active alerts, and explore scrape targets — without leaving the conversation.
Why another Prometheus MCP?
The existing Prometheus integrations require custom scripts or direct API knowledge. This server:
Speaks the standard Model Context Protocol over stdio — works with Claude Desktop, Claude Code, Cursor, and any MCP client.
Is read-only: all 5 tools carry
readOnlyHint: true— zero risk of modifying Prometheus data.Returns dual-channel output: structured JSON (
structuredContent) for programmatic use + Markdown (content) for human-readable display.Has actionable error messages that name the exact env var to fix and suggest a next step.
Supports Bearer token, HTTP Basic auth, or no auth (common for internal deployments).
Tools
Tool | Endpoint | Description |
|
| List all metric names with optional substring filter (cap 500) |
|
| Execute an instant PromQL query |
|
| Execute a PromQL range query returning time-series |
|
| List active and pending alerts |
|
| List scrape targets by health and job |
Installation
pip install prometheus-mcpOr run directly without installing:
uvx prometheus-mcpConfiguration
All configuration is via environment variables:
Variable | Required | Default | Description |
| Yes | — | Prometheus server URL, e.g. |
| No | — | Bearer token (takes precedence over Basic auth) |
| No | — | HTTP Basic auth username |
| No | — | HTTP Basic auth password |
| No |
| Set |
Copy .env.example to .env and fill in your values.
Claude Desktop / Claude Code setup
Add to your MCP config (claude_desktop_config.json or .claude/mcp.json):
{
"mcpServers": {
"prometheus": {
"command": "prometheus-mcp",
"env": {
"PROMETHEUS_URL": "https://prometheus.example.com",
"PROMETHEUS_TOKEN": "your-token-here"
}
}
}
}Or with uvx (no install required):
{
"mcpServers": {
"prometheus": {
"command": "uvx",
"args": ["prometheus-mcp"],
"env": {
"PROMETHEUS_URL": "https://prometheus.example.com"
}
}
}
}Docker
docker run --rm -e PROMETHEUS_URL=https://prometheus.example.com prometheus-mcpExample queries
Once configured, ask Claude:
"What metrics does Prometheus have about HTTP requests?"
"What is the current request rate for the payment service?"
"Show me CPU usage over the last hour with 5-minute resolution"
"Are there any firing alerts? What's their severity?"
"Which scrape targets are currently down and why?"
"How many node-exporter instances are up?"
Tool usage guide
prometheus_list_metrics
Returns all metric names Prometheus knows about. Use pattern to filter by substring (case-insensitive). Start here when you don't know which metrics are available. Output is capped at 500 metrics with a truncation hint.
prometheus_query
Execute an instant PromQL expression and get current values. Returns result type (vector/scalar/matrix/string), sample count, and per-sample labels and values.
Parameters:
query(required) — PromQL expression, e.g.up,rate(http_requests_total[5m])time(optional) — RFC3339 or Unix timestamp; defaults to now
prometheus_query_range
Execute a PromQL expression over a time window. Returns one series per matching time series with timestamped values. Total data points across all series are capped at 5000.
Parameters:
query(required) — PromQL expressionstart/end(required) — RFC3339 or Unix timestampsstep(required) — resolution like15s,1m,5m
Prometheus rejects steps that would produce > 11,000 points per series (HTTP 422). Increase step or narrow the range if this happens.
Note: The Prometheus range API does not support filtering by branch or commit — filters are expressed purely in PromQL label matchers.
prometheus_list_alerts
Returns all active/pending alerts with labels (including alertname, severity), state, activation time, and current value. Includes a state summary (firing vs pending counts).
prometheus_list_targets
Returns scrape targets with job name, instance address, health (up/down/unknown), last scrape duration in milliseconds, and any error message. Includes a per-job summary. Filter by state: active (default), dropped, or any.
Performance characteristics
All tools use a single persistent
requests.Sessionwith connection pooling.The session has
trust_env = Falseto bypass environment proxies (Prometheus is typically an internal service).Requests time out after 30 seconds.
prometheus_query_rangecaps output at 5000 total points across all series — use a larger step for long windows.prometheus_list_metricsreturns up to 500 metrics after filtering.
Development
git clone https://github.com/mshegolev/prometheus-mcp
cd prometheus-mcp
pip install -e '.[dev]'
pytest tests/ -v
ruff check src tests
ruff format src testsLicense
MIT — see LICENSE.
Maintenance
Latest Blog Posts
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/mshegolev/prometheus-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server