Ext Ops Panel
Open dashboard
Comparison

OpenMesh vs Muggle Works

OpenMesh is an MCP server published by docker. Marketplaces we read that list it: 1 (Docker MCP Catalog). Muggle Works is an MCP server published by multiplex-ai. Marketplaces we read that list it: 2 (Official MCP Registry, npm registry (MCP servers)). 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
MarketplaceOpenMeshMuggle Works
Docker MCP Catalog Not seen in the last pass
Version: not stated
No figure published
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 5.35.0
No figure published
Not marked · First seen
npm registry (MCP servers) Not listed Listed
Version: 5.34.1
Downloads/month (npm): 22 193
Downloads/week (npm): 17 102
Forks (GitHub): 2
Stars (GitHub): 16
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

OpenMesh vs Muggle Works
FactOpenMeshMuggle Works
Marketplaces that list it (differs)1 (worse)2 (better)
Stars (GitHub) (differs)No figure on GitHub16
Forks (GitHub) (differs)No figure on GitHub2
Last release (differs)Not published2026-11-09
Where it runs (differs)Remote server (api.openmesh.dev/mcp)On your machine (@muggleai/works)
Transport (differs)Streamable HTTPstdio
Tools it declares (differs)4Not published
Environment variables it asks forNot publishedNot published
LicenceApache-2.0Apache-2.0
Repository (differs)Not statedgithub.com/multiplex-ai/muggle-ai-works
Changes in the last 7 days (differs)07
First seen (differs)2026-10-112026-10-12
Endpoint at the last check (differs)No HTTP response at the last check (7 h ago)no remote endpoint we check

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

In its own words, on Docker MCP Catalog:

Discover and connect to a curated marketplace of MCP servers for extending AI agent capabilities.

Muggle Works

In its own words, on Official MCP Registry:

Acceptance test agent for coding agents: real-browser tests, with screenshots on the PR.

How to run each

OpenMesh As a remote MCP server

Claude Code
claude mcp add --transport http openmesh https://api.openmesh.dev/mcp

Muggle Works As a local MCP server: npm package

Claude Code
claude mcp add --transport stdio muggle -- npx -y @muggleai/works serve

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

Only OpenMesh has a remote endpoint we check. How we check endpoints

Tools each declares

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

Settings each asks for

Neither one's marketplaces publish the settings it asks for.

What it can do: OpenMesh · What it can do: Muggle Works · 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. Package data comes from the public npm registry (registry.npmjs.org). 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