Plugged.in Proxy vs Autodesk Revit MCP Server
Plugged.in Proxy is an MCP server published by VeriTeknik. Marketplaces we read that list it: 1 (Docker MCP Catalog). Autodesk Revit MCP Server is an MCP server published by Sam-AEC. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-24. 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 |  Plugged.in Proxy |  Autodesk Revit MCP Server |
|---|---|---|
| Docker MCP Catalog | Listed Version: sha256:b7c32590b270 Forks (GitHub): 30 Pulls (Docker Hub): 36 055 Stars (Docker Hub): 3 Stars (GitHub): 137 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 0.1.1 Forks (GitHub): 22 Stars (GitHub): 74 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 | Plugged.in Proxy | Autodesk Revit MCP Server |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 137 (better) | 74 (worse) |
| Pulls (Docker Hub) (differs) | 36 055 | No figure on Docker Hub |
| Forks (GitHub) (differs) | 30 (better) | 22 (worse) |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (mcp/pluggedin-mcp-proxy) | On your machine (https://github.com/Sam-AEC/Autodesk-Revit-MCP-Server/releases/download/v0.1.1/revit-mcp-server-0.1.1.mcpb) |
| Transport | stdio | stdio |
| Tools it declares (differs) | 6 | Not published |
| Environment variables it asks for (differs) | 2, secrets among them: 1 | 6, secrets among them: 0 |
| Licence (differs) | Apache-2.0 | Not stated |
| Repository (differs) | github.com/veriteknik/pluggedin-mcp-proxy | github.com/sam-aec/autodesk-revit-mcp-server |
| 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
Plugged.in Proxy
A unified MCP proxy that aggregates multiple MCP servers into one interface, enabling seamless tool discovery and management across all your AI interactions. Manage all your MCP servers from a single connection point with RAG capabilities and real-time notifications.
Autodesk Revit MCP Server
MCP server connecting AI assistants to Autodesk Revit through a local bridge.
How to run each
Plugged.in Proxy As a local MCP server: Docker image
claude mcp add --env "PLUGGEDIN_API_KEY=<YOUR_PLUGGEDIN_API_KEY>" --transport stdio pluggedin-mcp-proxy -- docker run -i --rm -e PLUGGEDIN_API_KEY mcp/pluggedin-mcp-proxyRequires: PLUGGEDIN_API_KEY (secret)
Autodesk Revit MCP Server
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
Requires: MCP_REVIT_ALLOWED_DIRECTORIES, MCP_REVIT_WORKSPACE_DIR
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Tools each declares
The marketplaces of Autodesk Revit MCP Server publish no list of tools, so we do not compare tools.
Settings each asks for
Only Plugged.in Proxy asks for
PLUGGEDIN_API_BASE_URLPLUGGEDIN_API_KEY (secret)
Only Autodesk Revit MCP Server asks for
MCP_REVIT_ALLOWED_DIRECTORIESMCP_REVIT_AUDIT_LOGMCP_REVIT_BRIDGE_URLMCP_REVIT_LOG_LEVELMCP_REVIT_MODEMCP_REVIT_WORKSPACE_DIR
Settings as each marketplace publishes them. Asking for fewer is not better in itself.
What it can do: Plugged.in Proxy · What it can do: Autodesk Revit MCP Server · 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.