io.github.BlueprintLabIO/tidebase vs Prometheus MCP Server
io.github.BlueprintLabIO/tidebase is an MCP server published by BlueprintLabIO. Marketplaces we read that list it: 1 (Official MCP Registry). Prometheus MCP Server is an MCP server published by pab1it0. Marketplaces we read that list it: 2 (Official MCP Registry, Docker MCP Catalog). As of our marketplace pass on 2026-10-19. 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 |  io.github.BlueprintLabIO/tidebase |  Prometheus MCP Server |
|---|---|---|
| Official MCP Registry | Listed Version: 0.1.1 Downloads/month (npm): 134 Downloads/week (npm): 15 Forks (GitHub): 0 Stars (GitHub): 1 Not marked · First seen |
Listed Version: 1.6.2 Forks (GitHub): 104 Stars (GitHub): 519 Not marked · First seen |
| Docker MCP Catalog | Not listed | Listed Version: sha256:3c3921301229 Forks (GitHub): 104 Stars (GitHub): 519 Not marked · First seen |
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 | io.github.BlueprintLabIO/tidebase | Prometheus MCP Server |
|---|---|---|
| Marketplaces that list it (differs) | 1 (worse) | 2 (better) |
| Stars (GitHub) (differs) | 1 (worse) | 519 (better) |
| Forks (GitHub) (differs) | 0 (worse) | 104 (better) |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (@tidebase/mcp) | On your machine (ghcr.io/pab1it0/prometheus-mcp-server:1.6.2) |
| Transport | stdio | stdio |
| Tools it declares (differs) | Not published | 6 |
| Environment variables it asks for (differs) | 1, secrets among them: 0 | 14, secrets among them: 2 |
| Licence (differs) | Apache-2.0 | MIT |
| Repository (differs) | github.com/blueprintlabio/tidebase | github.com/pab1it0/prometheus-mcp-server |
| Changes in the last 7 days (differs) | 4 | 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
io.github.BlueprintLabIO/tidebase
Inspect Tidebase agent runs, resolve approval gates, and trigger recovery from your AI assistant.
Prometheus MCP Server
MCP server providing Prometheus metrics access and PromQL query execution for AI assistants
How to run each
io.github.BlueprintLabIO/tidebase As a local MCP server: npm package
claude mcp add --transport stdio tidebase -- npx -y @tidebase/mcpPrometheus 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.2Requires: PROMETHEUS_PASSWORD (secret), PROMETHEUS_TOKEN (secret), PROMETHEUS_URL
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Tools each declares
The marketplaces of io.github.BlueprintLabIO/tidebase publish no list of tools, so we do not compare tools.
Settings each asks for
Only io.github.BlueprintLabIO/tidebase asks for
TIDEBASE_URL
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
Settings as each marketplace publishes them. Asking for fewer is not better in itself.
What it can do: io.github.BlueprintLabIO/tidebase · What it can do: Prometheus MCP Server · Compare two other plugins
Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Data comes from public marketplace files in GitHub repositories of their authors. 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.