io.github.Brunovncs/texel-mcp vs three.ws 3D Studio
io.github.Brunovncs/texel-mcp is an MCP server published by Brunovncs. 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-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 |  io.github.Brunovncs/texel-mcp |  three.ws 3D Studio |
|---|---|---|
| Official MCP Registry | Listed Version: 0.9.2 Downloads/month (npm): 245 Downloads/week (npm): 69 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
Listed Version: 1.0.1 Forks (GitHub): 73 Stars (GitHub): 270 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 | io.github.Brunovncs/texel-mcp | three.ws 3D Studio |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 0 (worse) | 270 (better) |
| Forks (GitHub) (differs) | 0 (worse) | 73 (better) |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (texel-mcp) | Remote server (three.ws/api/mcp-3d) |
| Transport (differs) | stdio | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Licence | Not stated | Not stated |
| Repository (differs) | github.com/brunovncs/texel-mcp | github.com/nirholas/three.ws |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Answered with HTTP 402 (9 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
io.github.Brunovncs/texel-mcp
Minecraft skins and textures as code: JSON specs compiled to PNG, with a review an agent can act on.
three.ws 3D Studio
Turn text or an image into an animation-ready 3D model (GLB): generate, rig, animate, retexture.
How to run each
io.github.Brunovncs/texel-mcp As a local MCP server: npm package
claude mcp add --transport stdio texel-mcp -- npx -y texel-mcpthree.ws 3D Studio As a remote MCP server
claude mcp add --transport http threews-3d-studio https://three.ws/api/mcp-3dCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only three.ws 3D Studio has a remote endpoint we 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: io.github.Brunovncs/texel-mcp · 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.