Model Context Protocol server for Rollbar
Prometheus is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
What it does
An API-complete MCP server to manage Prometheus-compatible backends.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user prometheus-mcp-2 '--' docker run -i --rm docker.io/prom/prometheus-mcp:v0.19.0-rc.0
# 2 — ask your agent for something these tools do
# query, range_query, exemplar_query and 27 more
Prometheus costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. This one runs on your machine: your client starts Prometheus as a process under your own user, with your files and your network, so the tool surface below is what it can do to your computer rather than to a server somewhere else. It has not been scanned here, so read the surface, and its source, before you approve it.
This is a public server: you run it yourself and this marketplace is not in the path. You need Docker installed and running. Claude Code registers it in one command; --scope user makes it available in every project. The '--' is in quotes so that PowerShell passes it on.
claude mcp add --scope user prometheus-mcp-2 '--' docker run -i --rm docker.io/prom/prometheus-mcp:v0.19.0-rc.0Reconnect, or start a new session, and the tools appear in the model’s tool list.
One config entry your client uses to start the process locally. A local server runs with your file system and your network, which is why it is priced without metering.
30 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Read from its source code. A server that builds its tool list when it starts can list more tools than this.
Execute an instant query against the Prometheus datasource, returning one value per series at a single point in time
No parameter schema on file.
Execute a range query against the Prometheus datasource, returning values over a time window; use for graphing and trend analysis
No parameter schema on file.
Execute an exemplar query against the Prometheus datasource to find trace exemplars associated with metric samples
No parameter schema on file.
Finds series by label matches
No parameter schema on file.
Returns the unique label names present in the block in sorted order by given time range and matches
No parameter schema on file.
Performs a query for the values of the given label, time range and matches
No parameter schema on file.
Returns metadata about metrics currently scraped by the metric name.
No parameter schema on file.
Returns metadata about metrics currently scraped by the target
No parameter schema on file.
Get overview of Prometheus Alertmanager discovery
No parameter schema on file.
Get runtime flags
No parameter schema on file.
List all active alerts
No parameter schema on file.
Get usage and cardinality statistics from the TSDB
No parameter schema on file.
Get Prometheus build information
No parameter schema on file.
Get Prometheus runtime information
No parameter schema on file.
List all alerting and recording rules that are loaded
No parameter schema on file.
Get overview of Prometheus target discovery
No parameter schema on file.
Get current WAL replay status
No parameter schema on file.
Removes the deleted data from disk and cleans up the existing tombstones. I/O- and CPU-intensive; prefer low-traffic periods and confirm with the user before calling.
No parameter schema on file.
No parameter schema on file.
creates a snapshot of all current data into snapshots/<datetime>-<rand> under the TSDB's data directory and returns the directory as response. Safe, but confirm with the user before calling.
No parameter schema on file.
Management API endpoint that can be used to check Prometheus health.
No parameter schema on file.
Management API endpoint that can be used to check Prometheus is ready to serve traffic (i.e. respond to queries.)
No parameter schema on file.
Management API endpoint that can be used to trigger a reload of the Prometheus configuration and rule files. Safe; applies changes without downtime.
No parameter schema on file.
Management API endpoint that can be used to trigger a graceful shutdown of Prometheus. Only call this when the user explicitly requests a shutdown.
No parameter schema on file.
List of Official Prometheus Documentation Files.
No parameter schema on file.
Read the named markdown file containing official Prometheus documentation from the prometheus/docs repo
No parameter schema on file.
Search the markdown files containing official Prometheus documentation from the prometheus/docs repo
No parameter schema on file.
No parameter schema on file.
Read the named runbook: a guided workflow (Agent Skill) for a common Prometheus task, expressed in terms of this server's tools. Follow its guidance when a user request matches a runbook's purpose; runbooks_list shows what is available.
No parameter schema on file.
List all store API servers
No parameter schema on file.
- Every tool, no call limit
- No card, and mcprush charges nothing for it
- Source published under Apache-2.0
- Runs on your machine — nothing of it reaches our gateway
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Prometheus or to call it, at any volume.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
This listing ships as a container image. The scanner reads packages on npm and PyPI and public source; an image is neither, so there is no grade here — not a withheld one, an unmeasured one.
Release history
It installs from a container image rather than from a versioned package, so the command cannot be pinned to a release. The history below is for reading; the current release on file is 0.19.0-rc.0.
No release note was published with this version.
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Any signed-in account that does not publish Prometheus can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.