Trident (Tripo 3D) vs three.ws 3D Studio
Trident (Tripo 3D) is an MCP server published by mordor-forge. 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 | ||
|---|---|---|
| Official MCP Registry | Listed Version: 0.4.0 Forks (GitHub): 1 Stars (GitHub): 5 Not marked · First seen |
Listed Version: 1.0.1 Forks (GitHub): 74 Stars (GitHub): 271 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 | Trident (Tripo 3D) | three.ws 3D Studio |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 5 (worse) | 271 (better) |
| Forks (GitHub) (differs) | 1 (worse) | 74 (better) |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (ghcr.io/mordor-forge/trident-mcp:0.4.0) | 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/mordor-forge/trident-mcp | github.com/nirholas/three.ws |
| Changes in the last 7 days | 0 | 0 |
| First seen (differs) | 2026-10-18 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Status out of date: last check 32 h ago returned HTTP 402 |
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
Trident (Tripo 3D)
Unofficial MCP server for the Tripo 3D API: text/image to 3D, texturing, rigging, conversion
three.ws 3D Studio
Turn text or an image into an animation-ready 3D model (GLB): generate, rig, animate, retexture.
How to run each
Trident (Tripo 3D) As a local MCP server: Docker image
claude mcp add --transport stdio trident-mcp -- docker run -i --rm -v "<YOUR_HOST_OUTPUT_DIR>:/output" -e "TRIPO_API_KEY=<YOUR_API_KEY>" -e "TRIPO_BASE_URL=<YOUR_BASE_URL>" ghcr.io/mordor-forge/trident-mcp:0.4.0
three.ws 3D Studio As a remote MCP server
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 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: Trident (Tripo 3D) · 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.