Ext Ops Panel
Open dashboard
Comparison

OpenMesh vs Thrixel

OpenMesh is an MCP server published by docker. Marketplaces we read that list it: 1 (Docker MCP Catalog). Thrixel is a plugin bundle for AI coding tools published by Thrixel. Marketplaces we read that list it: 2 (Community GitHub marketplaces, PyPI (MCP servers)). 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

Where each is published
MarketplaceOpenMeshThrixel
Docker MCP Catalog Listed
Version: not stated
No figure published
Not marked · First seen
Not listed
PyPI (MCP servers) Not listed Listed
Version: 1.3.28
Downloads/month (PyPI): 2 880
Downloads/week (PyPI): 1 039
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 Thrixel
FactOpenMeshThrixel
Marketplaces that list it (differs)1 (worse)2 (better)
Last release (differs)Not published2026-11-05
Where it runs (differs)Remote server (api.openmesh.dev/mcp)On your machine (thrixel-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
LicenceApache-2.0Apache-2.0
Repository (differs)Not statedgithub.com/thrixel/build-world
Changes in the last 7 days (differs)04
First seen (differs)2026-10-112026-10-13
Endpoint at the last check (differs)No HTTP response at the last check (2 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.

Thrixel

In its own words, on Community GitHub marketplaces:

Build playable 3D games with AI-generated assets. Bundles the build-world skill and the Thrixel connector: generate, refine and texture game-ready .glb models, then build the game around them in Three.js, Unity, Unreal or Roblox.

How to run each

OpenMesh As a remote MCP server

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

Thrixel As a Claude Code plugin

Claude Code
/plugin marketplace add thrixel/build-world
/plugin install thrixel@thrixel

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 Thrixel 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: Thrixel · 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. Package data comes from the Python Package Index (pypi.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