Three.js DevTools MCP vs BlenderLens
Three.js DevTools MCP is an MCP server published by DmitriyGolub. Marketplaces we read that list it: 1 (Official MCP Registry). BlenderLens is an MCP server published by pzalutski-pixel. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-28. 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
| Marketplace | ||
|---|---|---|
| Official MCP Registry | Listed Version: 0.2.1 Downloads/month (npm): 2 602 Downloads/week (npm): 1 188 Forks (GitHub): 13 Stars (GitHub): 128 Not marked · First seen |
Listed Version: 0.2.0 Downloads/month (npm): 444 Downloads/week (npm): 444 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
| Fact | Three.js DevTools MCP | BlenderLens |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 128 (better) | 0 (worse) |
| Forks (GitHub) (differs) | 13 (better) | 0 (worse) |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (threejs-devtools-mcp) | On your machine (blenderlens-mcp) |
| Transport | stdio | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | 5, secrets among them: 0 | 11, secrets among them: 1 |
| Licence | Not stated | Not stated |
| Repository (differs) | github.com/dmitriygolub/threejs-devtools-mcp | github.com/pzalutski-pixel/blenderlens-mcp |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-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
Three.js DevTools MCP
Inspect and edit Three.js scenes, materials, shaders, lights in real time from any AI agent
BlenderLens
MCP server that lets AI agents build, check, preview and export game assets in Blender
How to run each
Three.js DevTools MCP As a local MCP server: npm package
claude mcp add --transport stdio threejs-devtools -- npx -y threejs-devtools-mcp
BlenderLens As a local MCP server: npm package
claude mcp add --env "BLENDERLENS_TOKEN=<YOUR_BLENDERLENS_TOKEN>" --transport stdio blenderlens -- npx -y blenderlens-mcp
Requires: BLENDERLENS_TOKEN (secret)
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
Only Three.js DevTools MCP asks for
BRIDGE_PORTBROWSERCHROME_PATHDEV_PORTHEADLESS
Only BlenderLens asks for
BLENDERLENS_ALLOWED_DIRSBLENDERLENS_ALLOW_PYTHONBLENDERLENS_HOSTBLENDERLENS_MODEBLENDERLENS_PORTBLENDERLENS_RENDER_DIRBLENDERLENS_RUNTIME_DIRBLENDERLENS_START_TIMEOUTBLENDERLENS_TIMEOUTBLENDERLENS_TOKEN (secret)BLENDER_BIN
Settings as each marketplace publishes them. Asking for fewer is not better in itself.
What it can do: Three.js DevTools MCP · What it can do: BlenderLens · Compare two other plugins
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.