Developer · Local MCP server

Prometheus MCP Server

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

Visit Prometheus MCP Server's website

What the MCP Registry states

The entry as published to the official MCP Registry (read 2026-10-04), latest version.

Registry name
io.github.pab1it0/prometheus-mcp-server
Version
1.6.2
Status
Active
Category
developer
Transport
stdio (local process)
Package
OCI image (Docker)
Published
2026-08-03
Updated
2026-08-03
Publisher
pab1it0 (GitHub)
Listed under
Prometheus MCP servers
Website
pab1it0.github.io/prometheus-mcp-server
Repository
github.com/pab1it0/prometheus-mcp-server
Source
Registry API entry

Packages

RegistryPackageVersionTransportEnvironment variables
OCI image (Docker)ghcr.io/pab1it0/prometheus-mcp-server:1.6.2—stdioPROMETHEUS_URL (required), PROMETHEUS_URL_SSL_VERIFY, PROMETHEUS_DISABLE_LINKS, PROMETHEUS_USERNAME, PROMETHEUS_PASSWORD (secret), PROMETHEUS_TOKEN (secret), ORG_ID, PROMETHEUS_CLIENT_CERT, PROMETHEUS_CLIENT_KEY, PROMETHEUS_MCP_SERVER_TRANSPORT, PROMETHEUS_MCP_BIND_HOST, PROMETHEUS_MCP_BIND_PORT, PROMETHEUS_MCP_STATELESS_HTTP, PROMETHEUS_CUSTOM_HEADERS

How to connect Prometheus MCP Server

Prometheus MCP Server runs locally from a container image in an OCI registry such as Docker Hub or GitHub Container Registry: ghcr.io/pab1it0/prometheus-mcp-server:1.6.2. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Docker or another OCI container runtime; started with docker run — the usual command is docker 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. It reads these environment variables: PROMETHEUS_URL (required), PROMETHEUS_URL_SSL_VERIFY, PROMETHEUS_DISABLE_LINKS, PROMETHEUS_USERNAME, PROMETHEUS_PASSWORD (secret), PROMETHEUS_TOKEN (secret), ORG_ID, PROMETHEUS_CLIENT_CERT, PROMETHEUS_CLIENT_KEY, PROMETHEUS_MCP_SERVER_TRANSPORT, PROMETHEUS_MCP_BIND_HOST, PROMETHEUS_MCP_BIND_PORT, PROMETHEUS_MCP_STATELESS_HTTP and PROMETHEUS_CUSTOM_HEADERS; set them in the client's configuration for this server.

In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):

{
  "mcpServers": {
    "prometheus-mcp-server": {
      "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": "<value>",
        "PROMETHEUS_URL_SSL_VERIFY": "<value>",
        "PROMETHEUS_DISABLE_LINKS": "<value>",
        "PROMETHEUS_USERNAME": "<value>",
        "PROMETHEUS_PASSWORD": "<secret>",
        "PROMETHEUS_TOKEN": "<secret>",
        "ORG_ID": "<value>",
        "PROMETHEUS_CLIENT_CERT": "<value>",
        "PROMETHEUS_CLIENT_KEY": "<value>",
        "PROMETHEUS_MCP_SERVER_TRANSPORT": "<value>",
        "PROMETHEUS_MCP_BIND_HOST": "<value>",
        "PROMETHEUS_MCP_BIND_PORT": "<value>",
        "PROMETHEUS_MCP_STATELESS_HTTP": "<value>",
        "PROMETHEUS_CUSTOM_HEADERS": "<value>"
      }
    }
  }
}

Derived from the registry entry, not tested here. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect

More developer servers

All 6,250 →
ServerRunsEndpoint or package
ProjectmemCoding agent memory — one local MCP server for every project. Warns before repeating failed fixes.Local · stdioPyPI: projectmem
projectmindPersistent project memory for AI coding agents: one compact digest instead of re-reading the repo.Local · stdionpm: @nodemint/projectmind
ProjectPulse MCPMonitor GitHub repo health, DORA metrics and CI signals from your AI assistant.Local · stdionpm: projectpulse-mcp
ProjGraph MCP ServerAnalyze.NET solutions: Generate Mermaid graphs, ERDs, class diagrams, and project metrics.Local · stdioNuGet: ProjGraph.Mcp
Prompt CompassDecision-only prompt routing and firewall checks for local/cloud routing, PII and jailbreak risk.Remote & Local · HTTP, stdioapi.mpcfintech.com
Prompt Injection ScannerScans RAG content/scraped pages for indirect prompt injection.Local · stdionpm: @guardbee/mcp-prompt-injection-scanner
Prompt Leak ScannerCatches leaked credentials and PII in outbound LLM prompts.Local · stdionpm: @guardbee/mcp-prompt-leak-scanner
Prompt TimeClaude Desktop reminders for Windows. Survives MSIX boundary; persists across restarts. Zero deps.Local · stdioMCP Bundle (.mcpb): RyanJamesStewart/prompt-time/releases/download/v