Ext Ops Panel
Open dashboard
Comparison

meta-vr vs Three.js DevTools MCP

meta-vr is a plugin bundle for AI coding tools published by meta-quest. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). Three.js DevTools MCP is an MCP server published by DmitriyGolub. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-13. 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
Marketplacemeta-vrThree.js DevTools MCP
Claude Code: claude-plugins-community Listed
Version: 1.2.2
Forks (GitHub): 22
Stars (GitHub): 216
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.2.1
Downloads/month (npm): 1 621
Downloads/week (npm): 746
Forks (GitHub): 11
Stars (GitHub): 119
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

meta-vr vs Three.js DevTools MCP
Factmeta-vrThree.js DevTools MCP
Marketplaces that list it11
Stars (GitHub) (differs)216 (better)119 (worse)
Forks (GitHub) (differs)22 (better)11 (worse)
Last releaseNot publishedNot published
Where it runs (differs)On your machine (metavr)On your machine (threejs-devtools-mcp)
Transport (differs)Not statedstdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published5, secrets among them: 0
Hooks it runs (differs)1Not published
Parts of the bundle (differs)31Not a bundle
Licence (differs)Apache-2.0Not stated
Repository (differs)github.com/meta-quest/agentic-toolsgithub.com/dmitriygolub/threejs-devtools-mcp
Changes in the last 7 days00
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

meta-vr

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

Agent skills for Meta Quest/Horizon OS development. Helps Claude assist with Quest app debugging, performance analysis, VR project setup, Unity, OpenXR, WebXR, Spatial SDK and Platform SDK integration, store submission checks, and adb/hzdb device workflows.

Three.js DevTools MCP

In its own words, on Official MCP Registry:

Inspect and edit Three.js scenes, materials, shaders, lights in real time from any AI agent

How to run each

meta-vr As a Claude Code plugin

Claude Code
/plugin marketplace add anthropics/claude-plugins-community
/plugin install meta-vr@claude-community

Three.js DevTools MCP As a local MCP server: npm package

Claude Code
claude mcp add --transport stdio threejs-devtools -- npx -y threejs-devtools-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 meta-vr publish no settings it asks for, so we do not compare settings.

What it can do: meta-vr · What it can do: Three.js DevTools MCP · Compare two other plugins

Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. 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.

Where the data comes from: how the catalog is built