Ext Ops Panel
Open dashboard
Comparison

Polyfork low-poly 3D assets vs three.ws 3D Studio

Polyfork low-poly 3D assets is an MCP server published by polyfork.dev. Marketplaces we read that list it: 1 (Official MCP Registry). three.ws 3D Studio is an MCP server published by nirholas. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-16. 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
MarketplacePolyfork low-poly 3D assetsthree.ws 3D Studio
Official MCP Registry Listed
Version: 1.0.0
No figure published
Not marked · First seen
Listed
Version: 1.0.1
Forks (GitHub): 64
Stars (GitHub): 237
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

Polyfork low-poly 3D assets vs three.ws 3D Studio
FactPolyfork low-poly 3D assetsthree.ws 3D Studio
Marketplaces that list it11
Stars (GitHub) (differs)No figure on GitHub237
Forks (GitHub) (differs)No figure on GitHub64
Last releaseNot publishedNot published
Where it runs (differs)Remote server (polyfork.dev/mcp)Remote server (three.ws/api/mcp-3d)
TransportStreamable HTTPStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
LicenceNot statedNot stated
Repository (differs)Not statedgithub.com/nirholas/three.ws
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last check (differs)Responded 30 h agoAnswered with HTTP 402 (7 h ago)

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

Polyfork low-poly 3D assets

In its own words, on Official MCP Registry:

Low-poly 3D models and kits for three.js and game engines: search, match, remix, preview.

three.ws 3D Studio

In its own words, on Official MCP Registry:

Turn text or an image into an animation-ready 3D model (GLB): generate, rig, animate, retexture.

How to run each

Polyfork low-poly 3D assets As a remote MCP server

Claude Code
claude mcp add --transport http polyfork https://polyfork.dev/mcp

three.ws 3D Studio As a remote MCP server

Claude Code
claude mcp add --transport http threews-3d-studio https://three.ws/api/mcp-3d

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

Only the endpoint of Polyfork low-poly 3D assets responded at the last daily check. How we check endpoints

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: Polyfork low-poly 3D assets · What it can do: three.ws 3D Studio · 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.

Where the data comes from: how the catalog is built