Ext Ops Panel
Open dashboard
Comparison

threenative-asset-mcp vs paprika3d (three.js games and 3D pages end to end, for coding agents)

threenative-asset-mcp is an MCP server published by ThreeNativeHQ. Marketplaces we read that list it: 1 (npm registry (MCP servers)). 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-09. 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
Marketplacethreenative-asset-mcppaprika3d (three.js games and 3D pages end to end, for coding agents)
npm registry (MCP servers) Listed
Version: 0.16.0
Downloads/month (npm): 6 400
Downloads/week (npm): 1 264
Forks (GitHub): 1
Stars (GitHub): 5
Not marked · First seen
Not listed
Official MCP Registry Not listed 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

threenative-asset-mcp vs paprika3d (three.js games and 3D pages end to end, for coding agents)
Factthreenative-asset-mcppaprika3d (three.js games and 3D pages end to end, for coding agents)
Marketplaces that list it11
Stars (GitHub) (differs)5 (worse)6 (better)
Forks (GitHub) (differs)1 (better)0 (worse)
Last release (differs)2026-11-08Not published
Where it runs (differs)On your machine (threenative-asset-mcp)Not stated
TransportNot statedNot stated
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Licence (differs)UNLICENSEDNot stated
Repository (differs)github.com/threenativehq/threenative-asset-mcpgithub.com/keeno-corp/paprika3d
Changes in the last 7 days (differs)12
First seen (differs)2026-10-122026-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

threenative-asset-mcp

In its own words, on npm registry (MCP servers):

MCP server for discovering and safely downloading 3D and game-audio assets from curated public sources.

paprika3d (three.js games and 3D pages end to end, for coding agents)

In its own words, on Official MCP Registry:

Three.js MCP server: build three.js games and 3D pages end to end, from references to a live link

How to run each

threenative-asset-mcp

No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.

paprika3d (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

Neither one's marketplaces publish the settings it asks for.

What it can do: threenative-asset-mcp · What it can do: paprika3d (three.js games and 3D pages end to end, for coding agents) · Compare two other plugins

Package data comes from the public npm registry (registry.npmjs.org). 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