Ext Ops Panel
Open dashboard
Comparison

Plugged.in Proxy vs hai-agents

Plugged.in Proxy is an MCP server published by VeriTeknik. Marketplaces we read that list it: 1 (Docker MCP Catalog). hai-agents is a plugin bundle for AI coding tools published by hcompai. Marketplaces we read that list it: 1 (Community GitHub marketplaces). 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

Where each is published
MarketplacePlugged.in Proxyhai-agents
Docker MCP Catalog Listed
Version: sha256:b7c32590b270
Forks (GitHub): 30
Pulls (Docker Hub): 35 901
Stars (Docker Hub): 3
Stars (GitHub): 136
Not marked · First seen
Not listed
Community marketplace hcompai/agents-api-demos Not listed Listed
Version: not stated
No figure published
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 hai-agents
FactPlugged.in Proxyhai-agents
Marketplaces that list it11
Stars (GitHub) (differs)136No figure on GitHub
Pulls (Docker Hub) (differs)35 901No figure on Docker Hub
Forks (GitHub) (differs)30No figure on GitHub
Last releaseNot publishedNot published
Where it runs (differs)On your machine (mcp/pluggedin-mcp-proxy)Remote server (agp.eu.hcompany.ai/mcp)
Transport (differs)stdioStreamable HTTP
Tools it declares (differs)6Not published
Environment variables it asks for (differs)2, secrets among them: 1Not published
Parts of the bundle (differs)Not a bundle4
Licence (differs)Apache-2.0Not stated
Repository (differs)github.com/veriteknik/pluggedin-mcp-proxygithub.com/hcompai/agents-api-demos
Changes in the last 7 days (differs)02
First seen (differs)2026-10-112026-10-20
Endpoint at the last check (differs)no remote endpoint we checknot checked yet

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.

hai-agents

In its own words, on Community GitHub marketplaces:

Expert knowledge of the H Company APIs: portal (auth, orgs, API keys), agent platform v2 (sessions, agents, skills, environments, vaults), hai-agents Python/TS SDKs, automated HAI_API_KEY setup, and agent-view run replay.

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)

hai-agents As a Claude Code plugin

Claude Code
/plugin marketplace add hcompai/agents-api-demos
/plugin install hai-agents@hai-skills

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

Tools each declares

The marketplaces of hai-agents publish no list of tools, so we do not compare tools.

Settings each asks for

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

What it can do: Plugged.in Proxy · What it can do: hai-agents · 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