Ext Ops Panel
Open dashboard
Comparison

OpenMesh vs kwin-mcp

OpenMesh is an MCP server published by docker. Marketplaces we read that list it: 1 (Docker MCP Catalog). kwin-mcp is a plugin bundle for AI coding tools published by Byeonghoon Yoo. Marketplaces we read that list it: 1 (Community GitHub marketplaces). As of our marketplace pass on 2026-10-14. 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
MarketplaceOpenMeshkwin-mcp
Docker MCP Catalog Listed
Version: not stated
No figure published
Not marked · First seen
Not listed
Community marketplace vibeprogramm/kwin-mcp Not listed Listed
Version: 0.9.0
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

OpenMesh vs kwin-mcp
FactOpenMeshkwin-mcp
Marketplaces that list it11
Stars (GitHub) (differs)No figure on GitHub2
Forks (GitHub) (differs)No figure on GitHub0
Last releaseNot publishedNot published
Where it runs (differs)Remote server (api.openmesh.dev/mcp)On your machine (kwin-mcp)
Transport (differs)Streamable HTTPNot stated
Tools it declares (differs)4Not published
Environment variables it asks forNot publishedNot published
Parts of the bundle (differs)Not a bundle2
Licence (differs)Apache-2.0MIT
Repository (differs)Not statedgithub.com/vibeprogramm/kwin-mcp
Changes in the last 7 days (differs)02
First seen (differs)2026-10-112026-10-14
Endpoint at the last check (differs)Not responding since 2026-10-13no 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.

kwin-mcp

In its own words, on Community GitHub marketplaces:

Bundles the kwin-mcp MCP server (uvx kwin-mcp) plus the kwin-desktop-automation skill that teaches session-mode selection, the observe-act-verify loop, US-QWERTY vs Unicode typing, and platform pitfalls (surface-local coordinates, QMenu invisibility, EIS edge limits, clipboard opt-in).

How to run each

OpenMesh As a remote MCP server

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

kwin-mcp As a Claude Code plugin

Claude Code
/plugin marketplace add vibeprogramm/kwin-mcp
/plugin install kwin-mcp@kwin-mcp

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 kwin-mcp 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: kwin-mcp · 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