MCP Prometheus MCP Server

Mcp prometheus mcp server connects MCP Prometheus to AI assistants that speak the Model Context Protocol. An [MCP (Model Context Protocol)][mcp] server for Prometheus and Mimir, written in Go. Deployed in-cluster at Giant Swarm to give AI assistants authenticated, multi-tenant access to metrics infrastructure.

What MCP Prometheus does

An [MCP (Model Context Protocol)][mcp] server for Prometheus and Mimir, written in Go. Deployed in-cluster at Giant Swarm to give AI assistants authenticated, multi-tenant access to metrics infrastructure.

Tools it exposes

Once connected, the assistant can call these 4 tools directly:

• Tenancy — The Tenancy tool exposed by this server
• Observability — The Observability tool exposed by this server
• Endpoints — The Endpoints tool exposed by this server
• Advanced — Large query results are automatically truncated with guidance for the AI to refine its query

Installing the mcp prometheus mcp server

Setup follows the standard MCP pattern: clone or install the server, then register it in your client's configuration file and restart the client. The configuration snippets on this page cover Claude Desktop, Claude Code and Cursor.

Configuration

Before the server will start you need to supply 8 environment variables: PROMETHEUS_URL, PROMETHEUS_TOKEN, MCP_OAUTH_ENCRYPTION_KEY, VALKEY_URL, DEX_ISSUER_URL, DEX_CLIENT_ID, DEX_CLIENT_SECRET, DEX_REDIRECT_URL. Keep credentials in your client's env block or a secrets manager rather than committing them.

Where it fits

Monitoring servers replace the paste-the-stack-trace ritual with an assistant that reads the real event, with all its surrounding context intact. MCP Prometheus sits in that group, and the shape of its toolset — Tenancy, Observability, Endpoints among others — tells you what it is really for. Worth comparing against the other monitoring security servers in this directory before you commit to one, since several overlap in scope but differ sharply in setup cost and permissions.

Practical notes

• This is a hosted server — you point your client at an endpoint rather than running a local process, so there is nothing to keep updated on your machine.
• It will not start until its required credentials are present, so set those before wondering why the tools never appear.
• Maintained by giantswarm, written in Go.
• MCP clients ask for confirmation before each tool call by default. Keep that on while you learn what the mcp prometheus mcp server actually does with your data.
• Every entry in this directory is reviewed by hand before it goes live, and details are checked against the project's own documentation.