Prometheus MCP Server — Watchlist

MCP100 Assessment

Watchlist / Tracking

Why we’re tracking it

Track Prometheus API and query-tool compatibility as observability stacks change

Reviewed Oct 5, 2026 · Documentation review; complete setup workflow not independently tested

Best fit

Prometheus metric querying and PromQL analysis for operations agents.

What we know

MCP server for executing PromQL and analyzing Prometheus metrics over stdio/HTTP/SSE with several authentication options.

Maintenance / activity evidence

Observed Oct 2, 2026 (UTC)chore(deps): bump pygments from 2.19.2 to 2.20.0 ( 149)

Tracking evidence observed Oct 5, 2026. These dated signals do not establish current maintenance. Reviewed enrichment confidence: high.

Activity source · commits ↗Activity source · releases ↗

Verification gaps / watch-outs

Installation and comprehensive security have not been independently audited.
Read/query permissions of configured monitoring endpoint.
Prometheus credentials.
Sensitive access: Operational metrics, Monitoring credentials

Read-oriented monitoring access, but telemetry often exposes sensitive service/infra details.

Security source · repository notice ↗

Full authority, access and evidence limits are available in Review context and Access & risk.

Popularity

517 repository stars

Stars observed Sep 25, 2026.

Do not overwrite existing reviewed stars/download metrics with nulls from this enrichment batch.

All limitations / Review context

Which PromQL and metric-discovery capabilities remain documented?

The bounded assessment reviewed the official README, repository notices, security policy path, and security page for known material public-tracking blockers. No such blocker was identified. This is a public-tracking assessment, not an installation safety certification.

Read-oriented monitoring access, but telemetry often exposes sensitive service/infra details.
Read/query permissions of configured monitoring endpoint.
Prometheus credentials.
Metrics/query results are returned to the client.
Sensitive access: Operational metrics, Monitoring credentials
Installation, client compatibility and comprehensive security have not been independently audited. Authentication and access depend on the configured services.
A project-specific SECURITY.md policy was not available at the fetched official path; the review remains limited to published repository notices.
No installation, runtime, client matrix, or complete tool-contract audit was performed in this review.
The fetched official SECURITY.md path returned HTTP 404; it was not treated as positive evidence.
Requires a reachable Prometheus server.
Metrics may reveal sensitive infrastructure behavior.
Remote HTTP/SSE needs endpoint/network protection.

Original activity observations

2026-10-02T07:01:53Z: chore(deps): bump pygments from 2.19.2 to 2.20.0 ( 149)

Technical identity

github.com/pab1it0/prometheus-mcp-server

Exact implementation source: https://github.com/pab1it0/prometheus-mcp-server ↗
Reviewed resource type: MCP Server
Repository identity: pab1it0/prometheus-mcp-server

Evidence & Sources

Evidence basis: Recorded source evidence
Setup runtime verification: Not independently runtime-tested by MCP100 for this setup workflow.

Reviewed Oct 5, 2026 · Latest source observation Oct 7, 2026

GitHub repository ↗
pab1it0/prometheus-mcp-server
Recorded repository material and project history.

Setup · Watchlist

Install & Agents

claude-code

Publisher instructions with a documented client setup path.

Source evidence observed Oct 14, 2026.

Additional setup details required — see the specific gaps below.

Install / connect
Publisher instructions
Publisher CLI example: `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`. Docker Desktop MCP catalog is a separate installation path.
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
Configure / authenticate
Publisher instructions
Prometheus MCP runs via Docker/Helm; specify PROMETHEUS_URL and optional PROMETHEUS_TOKEN/TLS. Prometheus credentials belong to configured deployment; default remote endpoint not provided.
Check connection
Suggested check
Use publisher health_check / read-only metrics query under least privilege.
Remove / uninstall / revoke
MCP100 setup guide
For publisher Claude Code route; Docker Toolkit must be disabled in Docker Desktop if that installation path was used. Don’t shut down Prometheus.
Distinguish client registration removal from software uninstall, persistent data deletion and provider OAuth/API-key revocation.
claude mcp remove prometheus

Official Documentation & Sources

What it does

MCP server for executing PromQL and analyzing Prometheus metrics over stdio/HTTP/SSE with several authentication options.

Capability: Cloud & DevOps
Resource type: MCP Server
Best fit: Prometheus metric querying and PromQL analysis for operations agents.

Representative uses

Execute PromQL
Inspect metrics/labels/metadata
Analyze monitoring state
Connect to authenticated Prometheus endpoints

Limitations

Requires a reachable Prometheus server.
Metrics may reveal sensitive infrastructure behavior.
Remote HTTP/SSE needs endpoint/network protection.

Reviewed access

Access & risk

Review the exact access boundary before connecting this MCP to accounts, credentials, or sensitive data.

Authentication: Prometheus credentials.
Permissions: Read/query permissions of configured monitoring endpoint.
Data handling: Metrics/query results are returned to the client.
Cost: free
Risk and cautions: Read-oriented monitoring access, but telemetry often exposes sensitive service/infra details.

Access scope and cautions

Write actions: None in the reviewed inventory
Sensitive access: Operational metrics Monitoring credentials
Risk level: moderate

FAQ

Based on reviewed evidence as of 2026-10-07. Watchlist tracking is not a recommendation or a security certification.

Which tasks are documented for this implementation?

The reviewed tasks include: Execute PromQL; Inspect metrics/labels/metadata; Analyze monitoring state; Connect to authenticated Prometheus endpoints.

What setup and authentication are documented?

Recorded installation/entrypoint step: docker run -i --rm -e PROMETHEUS_URL=http://your-prometheus:9090 ghcr.io/pab1it0/prometheus-mcp-server:latest. Recorded transport: stdio, streamable_http, sse. Recorded environment-variable notes: PROMETHEUS_URL; PROMETHEUS_USERNAME/PASSWORD optional; PROMETHEUS_TOKEN optional. No configuration values are supplied here. Prerequisites: Prometheus server. These are the documented setup details, not a claim that installation or client compatibility was independently tested. Authentication: Prometheus basic/bearer/client-cert auth as configured.

Can it modify data or perform write operations?

The reviewed inventory lists no write actions. An empty inventory alone does not establish read-only authority. Recorded permission boundary: Read/query permissions of configured monitoring endpoint.

What data-handling boundary should I consider?

Metrics/query results are returned to the client. Recorded sensitive-access context: Operational metrics; Monitoring credentials.

What limitations and risks should I check before use?

Read-oriented monitoring access, but telemetry often exposes sensitive service/infra details. Requires a reachable Prometheus server. Metrics may reveal sensitive infrastructure behavior. Remote HTTP/SSE needs endpoint/network protection. A project-specific SECURITY.md policy was not available at the fetched official path; the review remains limited to published repository notices.

Is this an official MCP?

pab1it0 is listed as Community implementation in MCP100’s current evidence.