OpenMesh vs PlugMCP directory
OpenMesh is an MCP server published by docker. Marketplaces we read that list it: 1 (Docker MCP Catalog). PlugMCP directory is an MCP server published by plugmcp.ai. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-08. 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 |  OpenMesh |  PlugMCP directory |
|---|---|---|
| Docker MCP Catalog | Listed Version: not stated No figure published Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 0.1.4 Forks (GitHub): 0 Stars (GitHub): 2 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 | OpenMesh | PlugMCP directory |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | No figure on GitHub | 2 |
| Forks (GitHub) (differs) | No figure on GitHub | 0 |
| Last release (differs) | Not published | 2026-11-05 |
| Where it runs (differs) | Remote server (api.openmesh.dev/mcp) | Remote server (plugmcp.ai/mcp-server) |
| Transport | Streamable HTTP | Streamable HTTP |
| Tools it declares (differs) | 4 | Not published |
| Environment variables it asks for (differs) | Not published | 1, secrets among them: 1 |
| Licence (differs) | Apache-2.0 | Not stated |
| Repository (differs) | Not stated | github.com/plugmcp-ai/plugmcp-mcp |
| Changes in the last 7 days (differs) | 0 | 3 |
| First seen (differs) | 2026-10-11 | 2026-11-05 |
| Endpoint at the last check (differs) | Status out of date: no HTTP response at the last check 2 days ago | Status out of date: last check 30 h ago returned HTTP 200 |
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
OpenMesh
Discover and connect to a curated marketplace of MCP servers for extending AI agent capabilities.
PlugMCP directory
Search MCP servers and agent skills, compare them, and get install configs for your client.
How to run each
OpenMesh As a remote MCP server
claude mcp add --transport http openmesh https://api.openmesh.dev/mcpPlugMCP directory As a remote MCP server
claude mcp add --transport http directory https://plugmcp.ai/mcp-server --header "Authorization: Bearer <YOUR_TOKEN>"Requires: PLUGMCP_API_KEY (secret), Authorization header
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only the endpoint of PlugMCP directory responded at the last daily check. How we check endpoints
Tools each declares
The marketplaces of PlugMCP directory publish no list of tools, so we do not compare tools.
Settings each asks for
The marketplaces of OpenMesh publish no settings it asks for, so we do not compare settings.
What it can do: OpenMesh · What it can do: PlugMCP directory · 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.