Prometheus MCP Server vs tierproxy
Prometheus MCP Server is an MCP server published by pab1it0. Marketplaces we read that list it: 2 (Official MCP Registry, Docker MCP Catalog). tierproxy is an MCP server published by tierproxy. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-13. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.
Where each is published
| Marketplace | ||
|---|---|---|
| Official MCP Registry | Listed Version: 1.6.2 Forks (GitHub): 104 Stars (GitHub): 518 Not marked · First seen |
Listed Version: 0.4.0 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
| Docker MCP Catalog | Listed Version: sha256:3c3921301229 Forks (GitHub): 104 Stars (GitHub): 518 Not marked · First seen |
Not listed |
Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.
The facts side by side
| Fact | Prometheus MCP Server | tierproxy |
|---|---|---|
| Marketplaces that list it (differs) | 2 (better) | 1 (worse) |
| Stars (GitHub) (differs) | 518 (better) | 0 (worse) |
| Forks (GitHub) (differs) | 104 (better) | 0 (worse) |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (ghcr.io/pab1it0/prometheus-mcp-server:1.6.2) | On your machine (tierproxy) |
| Transport | stdio | stdio |
| Tools it declares (differs) | 6 | Not published |
| Environment variables it asks for (differs) | 14, secrets among them: 2 | 1, secrets among them: 1 |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/pab1it0/prometheus-mcp-server | github.com/tierproxy/python-sdk |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.
What each says it does
Prometheus MCP Server
MCP server providing Prometheus metrics access and PromQL query execution for AI assistants
tierproxy
Multi-provider proxy infrastructure for AI/ML. Geo, sessions, cost-aware routing, usage tools.
How to run each
Prometheus MCP Server As a local MCP server: Docker image
claude mcp add --env "PROMETHEUS_PASSWORD=<YOUR_PROMETHEUS_PASSWORD>" --env "PROMETHEUS_TOKEN=<YOUR_PROMETHEUS_TOKEN>" --env "PROMETHEUS_URL=<YOUR_PROMETHEUS_URL>" --transport stdio prometheus-mcp-server -- docker run -i --rm -e PROMETHEUS_PASSWORD -e PROMETHEUS_TOKEN -e PROMETHEUS_URL ghcr.io/pab1it0/prometheus-mcp-server:1.6.2
Requires: PROMETHEUS_PASSWORD (secret), PROMETHEUS_TOKEN (secret), PROMETHEUS_URL
tierproxy As a local MCP server: PyPI package
claude mcp add --env "TIERPROXY_API_KEY=<YOUR_TIERPROXY_API_KEY>" --transport stdio python-sdk -- uvx --spec "tierproxy[mcp]" tierproxy tierproxy-mcp
Requires: TIERPROXY_API_KEY (secret)
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Tools each declares
The marketplaces of tierproxy publish no list of tools, so we do not compare tools.
Settings each asks for
Only Prometheus MCP Server asks for
ORG_IDPROMETHEUS_CLIENT_CERTPROMETHEUS_CLIENT_KEYPROMETHEUS_CUSTOM_HEADERSPROMETHEUS_DISABLE_LINKSPROMETHEUS_MCP_BIND_HOSTPROMETHEUS_MCP_BIND_PORTPROMETHEUS_MCP_SERVER_TRANSPORTPROMETHEUS_MCP_STATELESS_HTTPPROMETHEUS_PASSWORD (secret)PROMETHEUS_TOKEN (secret)PROMETHEUS_URL
Show the remaining 2
PROMETHEUS_URL_SSL_VERIFYPROMETHEUS_USERNAME
Only tierproxy asks for
TIERPROXY_API_KEY (secret)
Settings as each marketplace publishes them. Asking for fewer is not better in itself.
What it can do: Prometheus MCP Server · What it can do: tierproxy · Compare two other plugins
Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.