Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Description from the maker (original English)
Prometheus MCP server for AI agents: PromQL queries, alert explanations, series discovery.
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
PROM_URL, PROM_TOKEN, PROM_TIMEOUTValues marked secret are keys to your account. Never share them or paste them into a chat.
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Download the maker’s .mcpb file
The link goes to the maker’s own file; we do not host or repackage it. Open the file and Claude Desktop installs it.
Run this in your terminal
Fill in the empty values before running it.
Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.
Your choice stays on this device in a cookie; no account needed.
PROM_URL envPROM_TIMEOUT envThese settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
Runs on your computer; the tool list appears in your AI app after you install it.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 6, 2026
The registry name was verified with the GitHub account aniketatgithub, which owns the repo
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Runs on your computer; we can only read tool lists from internet endpoints
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
You need to fill in: PROM_TOKEN
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
The GitHub repo last changed –, and the latest version (0.2.0) reached the registry 28 days ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need MCPB on your computer.
In the same category: Spec Driven Development, Remote Desktop Commander, Whisper
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
One routable IPv6 per AI agent, verifiable from the DNS root. Keyless tools need no signup.
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
prom-mcp is a Prometheus MCP server (Model Context Protocol) that gives AI agents production-grade eyes on your metrics. Connect Claude Code, Cursor, or any MCP client to Prometheus and let the agent run PromQL queries, explain firing alerts with their rule definitions, and discover which series actually exist before querying — so it investigates instead of guessing.
Built by a production engineer who works on-call, so the output reads like a triage note, not a raw JSON dump.
5 tools • 2 resources • 1 triage prompt • single Go binary • zero dependencies • stdio
Download the bundle for your platform, then open it or drag it into Claude Desktop (Settings → Extensions). You will be asked for your Prometheus URL, which defaults to http://localhost:9090.
| Platform | MCPB bundle |
|---|---|
| macOS (Apple silicon) | prom-mcp_v0.2.0_darwin_arm64.mcpb |
| macOS (Intel) | prom-mcp_v0.2.0_darwin_amd64.mcpb |
| Linux (x86_64) | prom-mcp_v0.2.0_linux_amd64.mcpb |
| Linux (arm64) | prom-mcp_v0.2.0_linux_arm64.mcpb |
With the binary on your PATH (release download or go install, see below):
claude mcp add prom -- prom-mcp
Set PROM_URL in your shell first if your Prometheus is not at http://localhost:9090, or pass --env PROM_URL=... to the command. More variants in examples/claude-code.md.
Add to ~/.cursor/mcp.json (same file as examples/cursor-mcp.json):
{
"mcpServers": { "prom": { "command": "prom-mcp", "env": { "PROM_URL": "http://localhost:9090" } } } }
Add to .vscode/mcp.json (same file as examples/vscode-mcp.json):
{
"servers": { "prom": { "command": "prom-mcp", "env": { "PROM_URL": "http://localhost:9090" } } } }
go install github.com/aniketatgithub/prom-mcp@latest
git clone https://github.com/aniketatgithub/prom-mcp && cd prom-mcp
go build -o prom-mcp ./cmd/prom-mcp
Plain binaries for all four platforms are also on the v0.2.0 release, next to the MCPB bundles above.
| You ask | prom-mcp does |
|---|---|
| "Why is NodeDown firing?" | prom_alerts_explain returns the active alert joined with its rule expression, group, for, labels, and annotations. |
| "What jobs and instances actually exist?" | prom_series_discover and prom_label_values list real series and label values before any query is written. |
| "Is this getting worse?" | prom_query_range summarizes the window per series: points, first, last, min, max. |
Alert triage: why is the node down?
Discover what exists before querying:
Check the trend: is node1 getting worse?
Ask your agent *"why is the node down?"* and the alert tool answers in triage shape:
1 active alert(s)
[firing] NodeDown (since 2026-10-08T10:00:00Z, value 0) labels: {alertname="NodeDown", instance="node1:9100", job="node", severity="critical"} summary: Node node1:9100 is down description: Scrapes failing for 5m rule: up{job="node"} == 0 group: node.rules for: 5m0s
Plus a built-in triage prompt template that walks the agent through alerts, discovery, and trend checks in order.
| Tool | What it does |
|---|---|
prom_query | Instant PromQL query, rendered as compact labelled series and values. |
prom_query_range | Range query over the last N minutes; per-series points, first, last, min, max. |
prom_alerts_explain | Active alerts joined with alerting-rule expressions, rule group, for duration, and annotations. |
prom_label_values | Lists real values of a label (optionally scoped), so the agent learns actual job/instance names. |
prom_series_discover | Checks which series exist for a label matcher, so the agent stops hallucinating metric names. |
Resources: prometheus://alerts (explained alerts), prometheus://config. Prompt: triage.
prom-mcp demo # fixture-backed self-test: query, alert explanation, series discovery
prom-mcp query 'up' # one-shot CLI query against $PROM_URL
| Setting | Env var | Config file key |
|---|---|---|
| Prometheus base URL | PROM_URL | base_url |
| Bearer token (auth-protected Prometheus) | PROM_TOKEN | token |
| Request timeout | PROM_TIMEOUT (e.g. 30s) | timeout_seconds |
| Config file path | PROM_CONFIG |
Config file is JSON, looked up at $PROM_CONFIG, then ./prom-mcp.json, then ~/.prom-mcp.json:
{ "base_url": "https://prometheus.example.com", "token": "…", "timeout_seconds": 30 }
Env vars override the file. No config at all defaults to http://localhost:9090.
Agents drown in raw Prometheus JSON and invent metric names that do not exist. prom-mcp returns terse, labelled, triage-shaped text and makes the agent discover before querying. That is the difference between an agent that guesses and an agent that investigates.
Single Go binary, zero dependencies, works fully offline against your own Prometheus.
Comparing servers? See docs/comparison.md for an honest side-by-side with pab1it0/prometheus-mcp-server and the Prometheus org's prometheus/prometheus-mcp.
Which AI clients work with prom-mcp? Any MCP client: Claude Code, Cursor, Windsurf, Zed, and custom agents. It speaks newline-delimited JSON-RPC 2.0 over stdio.
How do I connect prom-mcp to a remote Prometheus? Set PROM_URL to your Prometheus base URL (for example http://localhost:9090 or your internal endpoint) when adding the server.
Can an AI agent explain why a Prometheus alert is firing? Yes. prom_alerts_explain joins active alerts with the rule that fired them (expression, summary, description), so the agent can reason about the cause instead of reporting raw JSON.
Does prom-mcp need any API keys or cloud services? No. It is a single local binary talking only to your Prometheus.
How does prom-mcp compare to the other Prometheus MCP servers? See docs/comparison.md. Short version: prom-mcp is the focused alert-triage option with 5 tools; the others cover more of the Prometheus API or ship more deployment machinery.
How is this different from exposing the Prometheus HTTP API to an agent? Raw API access returns nested JSON the agent must parse and invites invented metric names. prom-mcp renders compact labelled text, joins alerts with the rules that fired them, caps long outputs, and nudges discovery before querying. It also retries transient failures and supports bearer-token auth.
Does it work with a remote or auth-protected Prometheus? Yes: set PROM_URL and PROM_TOKEN (or a JSON config file). See Configuration.
Which Prometheus versions are supported? Any server exposing the standard HTTP API (/api/v1/query, query_range, alerts, rules, series, label/ /values).
MIT. See LICENSE.