Ext Ops Panel
Open dashboard
Comparison

Unity vs text-to-reality

Unity is a plugin bundle for AI coding tools published by Unity-Technologies. Marketplaces we read that list it: 2 (Claude Code: claude-plugins-official, Claude: knowledge-work-plugins). text-to-reality is an MCP server published by ai-wes. Marketplaces we read that list it: 2 (Official MCP Registry, 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
MarketplaceUnitytext-to-reality
Claude Code: claude-plugins-official Listed
Version: 0.1.6-beta
Forks (GitHub): 42
Stars (GitHub): 409
Not marked · First seen
Not listed
Claude: knowledge-work-plugins Listed
Version: 0.1.6-beta
Forks (GitHub): 42
Stars (GitHub): 409
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.1.1
Downloads/month (PyPI): 0
Downloads/week (PyPI): 277
Forks (GitHub): 0
Stars (GitHub): 0
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

Unity vs text-to-reality
FactUnitytext-to-reality
Marketplaces that list it22
Stars (GitHub) (differs)409 (better)0 (worse)
Forks (GitHub) (differs)42 (better)0 (worse)
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleOn your machine (text-to-reality)
Transport (differs)Not statedstdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published1, secrets among them: 0
Parts of the bundle (differs)311
Licence (differs)LicenseRef-Unity-Companion-LicenseMIT
Repository (differs)github.com/unity-technologies/unity-agent-plugingithub.com/ai-wes/text-to-reality
Changes in the last 7 days (differs)02
First seen2026-10-112026-10-11

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

Unity

In its own words, on Claude Code: claude-plugins-official:

Unity's official plugin for Claude Code, with curated skills for game development, monetization, and performance optimization.

text-to-reality

In its own words, on Official MCP Registry:

Turn an idea into a device anyone can build: parts, printed parts, wiring, code and a picture guide.

How to run each

Unity As a Claude Code plugin

Claude Code
/plugin install unity@claude-plugins-official

text-to-reality As a local MCP server: PyPI package

Claude Code
claude mcp add --transport stdio text-to-reality -- uvx text-to-reality mcp

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

Tools each declares

Neither one's marketplaces publish a list of tools, so there is nothing to compare.

Settings each asks for

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

What it can do: Unity · What it can do: text-to-reality · Compare two other plugins

Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-official/blob/HEAD/.claude-plugin/marketplace.json. Data comes from the public marketplace file https://github.com/anthropics/knowledge-work-plugins/blob/HEAD/.claude-plugin/marketplace.json. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. 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