Proxmox VE vs briq
Proxmox VE is an MCP server published by GethosTheWalrus. Marketplaces we read that list it: 1 (Docker MCP Catalog). briq is an MCP server published by briq.cloud. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-21. 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 |   Proxmox VE |   briq |
|---|---|---|
| Docker MCP Catalog | Listed Version: sha256:6e30b4d837b2 Forks (GitHub): 15 Pulls (Docker Hub): 34 798 Stars (Docker Hub): 3 Stars (GitHub): 212 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 1.0.2 Forks (GitHub): 0 Stars (GitHub): 0 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 | Proxmox VE | briq |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 212 (better) | 0 (worse) |
| Pulls (Docker Hub) (differs) | 34 798 | No figure on Docker Hub |
| Forks (GitHub) (differs) | 15 (better) | 0 (worse) |
| Last release (differs) | Not published | 2026-10-19 |
| Where it runs (differs) | On your machine (mcp/proxmox) | Remote server (api.briq.cloud/mcp) |
| Transport (differs) | stdio | Streamable HTTP |
| Tools it declares (differs) | 286 | Not published |
| Environment variables it asks for (differs) | 8, secrets among them: 2 | Not published |
| Licence (differs) | NOASSERTION | Not stated |
| Repository (differs) | github.com/gethosthewalrus/proxmox-mcp | github.com/briq-cloud/briq-mcp |
| Changes in the last 7 days (differs) | 0 | 4 |
| First seen (differs) | 2026-10-11 | 2026-10-12 |
| Endpoint at the last check (differs) | no remote endpoint we check | Responded 4 days ago, requires a key |
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
Proxmox VE
Manage Proxmox VE infrastructure including virtual machines, containers, storage, networking, firewall rules, high availability, and more.
briq
Give your agent its own cloud: Postgres, Redis, a sandbox or any Docker image, in one MCP call.
How to run each
Proxmox VE As a local MCP server: Docker image
claude mcp add --env "PROXMOX_PASSWORD=<YOUR_PROXMOX_PASSWORD>" --env "PROXMOX_TOKEN_VALUE=<YOUR_PROXMOX_TOKEN_VALUE>" --transport stdio proxmox -- docker run -i --rm -e PROXMOX_PASSWORD -e PROXMOX_TOKEN_VALUE mcp/proxmoxRequires: PROXMOX_PASSWORD (secret), PROXMOX_TOKEN_VALUE (secret)
briq As a remote MCP server
claude mcp add --transport http briq https://api.briq.cloud/mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only briq has a remote endpoint we check. How we check endpoints
Tools each declares
The marketplaces of briq publish no list of tools, so we do not compare tools.
Settings each asks for
The marketplaces of briq publish no settings it asks for, so we do not compare settings.
What it can do: Proxmox VE · What it can do: briq · Compare two other plugins
Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.