Three.js DevTools MCP vs paprika3d (three.js games and 3D pages end to end, for coding agents)
Three.js DevTools MCP is an MCP server published by DmitriyGolub. Marketplaces we read that list it: 1 (Official MCP Registry). paprika3d (three.js games and 3D pages end to end, for coding agents) is an MCP server published by Keeno-Corp. Marketplaces we read that list it: 1 (Official MCP Registry). 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
| Marketplace |  Three.js DevTools MCP |  paprika3d (three.js games and 3D pages end to end, for coding agents) |
|---|---|---|
| Official MCP Registry | Listed Version: 0.2.1 Downloads/month (npm): 10 934 Downloads/week (npm): 4 706 Forks (GitHub): 13 Stars (GitHub): 129 Not marked · First seen |
Listed Version: 0.4.2 Forks (GitHub): 0 Stars (GitHub): 6 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 | paprika3d (three.js games and 3D pages end to end, for coding agents) |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 129 (better) | 6 (worse) |
| Forks (GitHub) (differs) | 13 (better) | 0 (worse) |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (threejs-devtools-mcp) | Not stated |
| Transport (differs) | stdio | Not stated |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | 5, secrets among them: 0 | Not published |
| Licence | Not stated | Not stated |
| Repository (differs) | github.com/dmitriygolub/threejs-devtools-mcp | github.com/keeno-corp/paprika3d |
| Changes in the last 7 days (differs) | 0 | 2 |
| First seen (differs) | 2026-10-11 | 2026-11-06 |
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
paprika3d (three.js games and 3D pages end to end, for coding agents)
Three.js MCP server: build three.js games and 3D pages end to end, from references to a live link
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-mcppaprika3d (three.js games and 3D pages end to end, for coding agents)
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
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 paprika3d (three.js games and 3D pages end to end, for coding agents) publish no settings it asks for, so we do not compare settings.
What it can do: Three.js DevTools MCP · What it can do: paprika3d (three.js games and 3D pages end to end, for coding agents) · 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.