Ext Ops Panel
Open dashboard
Comparison

Plugged.in Proxy vs rove

Plugged.in Proxy is an MCP server published by VeriTeknik. Marketplaces we read that list it: 1 (Docker MCP Catalog). rove is a plugin bundle for AI coding tools published by Sma1lboy. Marketplaces we read that list it: 1 (Community GitHub marketplaces). As of our marketplace pass on 2026-11-11. 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

Where each is published
MarketplacePlugged.in Proxyrove
Docker MCP Catalog Listed
Version: sha256:b7c32590b270
Forks (GitHub): 29
Pulls (Docker Hub): 36 699
Stars (Docker Hub): 3
Stars (GitHub): 139
Not marked · First seen
Not listed
Community marketplace sma1lboy/rove Not listed Listed
Version: 0.1.0
Forks (GitHub): 13
Stars (GitHub): 184
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

Plugged.in Proxy vs rove
FactPlugged.in Proxyrove
Marketplaces that list it11
Stars (GitHub) (differs)139 (worse)184 (better)
Pulls (Docker Hub) (differs)36 699No figure on Docker Hub
Forks (GitHub) (differs)29 (better)13 (worse)
Last releaseNot publishedNot published
Where it runs (differs)On your machine (mcp/pluggedin-mcp-proxy)Installs as a plugin bundle
Transport (differs)stdioNot stated
Tools it declares (differs)6Not published
Environment variables it asks for (differs)2, secrets among them: 1Not published
Hooks it runs (differs)Not published11
Parts of the bundle (differs)Not a bundle11
Licence (differs)Apache-2.0Not stated
Repository (differs)github.com/veriteknik/pluggedin-mcp-proxygithub.com/sma1lboy/rove
Changes in the last 7 days (differs)02
First seen (differs)2026-10-112026-11-06

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

In its own words, on Docker MCP Catalog:

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.

rove

In its own words, on Community GitHub marketplaces:

Rove activity hooks (session/turn/compact/subagent reporting to the Rove daemon) plus the bundled `rove api` agent skill.

How to run each

Plugged.in Proxy As a local MCP server: Docker image

Claude Code
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-proxy

Requires: PLUGGEDIN_API_KEY (secret)

rove As a Claude Code plugin

Claude Code
/plugin marketplace add sma1lboy/rove
/plugin install rove@rove

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Tools each declares

The marketplaces of rove publish no list of tools, so we do not compare tools.

Settings each asks for

The marketplaces of rove publish no settings it asks for, so we do not compare settings.

What it can do: Plugged.in Proxy · What it can do: rove · Compare two other plugins

Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. Data comes from public marketplace files in GitHub repositories of their authors. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.

Where the data comes from: how the catalog is built