Trident MCP

What mordor-forge/trident-mcp MCP server does

mordor-forge/trident-mcp MCP server exposes Tripo 3D’s documented and deployed v3 workflows to MCP-compatible agents. It can create meshes from text prompts, a single image, or multiple views; produce reference images and multiview sets; and process existing assets. Supported processing includes texturing, retopology, UV unwrapping, segmentation, rigging, animation, stylization, and format conversion. It can also produce Gaussian splats.

The project is relevant to the 🎥 Multimedia Process category because its output is 3D media saved as local files. Supported export formats include GLB, FBX, OBJ, STL, and USDZ, according to the listing description. The repository is an independent Tripo API client and is not affiliated with Tripo, VAST, or Holymolly Ltd.

How it works

mordor-forge/trident-mcp MCP server runs as one Go executable and communicates with an MCP client over standard input and output. A task-starting tool validates arguments, uploads local inputs when needed, and returns a task ID. The wait_for_task tool monitors that task, reports progress notifications, and writes the resulting files beneath a directory named for the task ID.

Task IDs can be passed into later operations to form pipelines. For example, an agent can turn an image into a mesh, send the result through rigging and animation, and then request an FBX conversion. Tool arguments generally use Tripo’s field names. One documented convenience difference is that multiview inputs can be supplied as a map containing front, left, back, and right images.

Setup and configuration

To run mordor-forge/trident-mcp MCP server, build or install the trident-mcp Go binary and register it as an MCP server. The repository provides a go install command and a JSON configuration example for clients that launch stdio servers. Claude Code users can also install the associated plugin, which adds the tripo-3d workflow skill and requests the API key and output directory during setup.

Set TRIPO_API_KEY to a key from the Tripo platform. MODEL_OUTPUT_DIR controls where completed files are stored and defaults to ~/generated_models; the directory is created if it does not exist. TRIPO_BASE_URL defaults to https://openapi.tripo3d.ai/v3; China-region keys use https://openapi.tripo3d.com/v3 instead.

Tools and capabilities

The repository documents 28 MCP tools, including task creation and task waiting. The available workflows cover:

• Text, single-image, and multiview mesh generation
• Reference-image and multiview-set creation
• Texturing, retopology, UV unwrapping, and segmentation
• Rigging and animation
• Mesh conversion to supported formats
• Stylization and Gaussian splat generation
• Local-file upload as part of task submission
• Progress reporting and output-file storage

The full argument and behavior reference is maintained in docs/MCP_TOOLS.md. Tripo’s developer documentation applies to the underlying API fields, while the MCP documentation describes project-specific behavior.

Limitations and notes

mordor-forge/trident-mcp MCP server requires access to the Tripo service and a user-provided API key. Generated assets are written to disk rather than returned only as in-memory MCP results. Tripo’s terms govern API usage, including requirements to protect the key and obtain written authorization before offering a shared or hosted deployment to other users.

Ownership of generated models depends on the Tripo plan. Pricing information can change, so the current Tripo pricing page is authoritative. The Apache-2.0 license applies to this repository’s code, not to Tripo’s service or the models it generates. A few Tripo endpoints are intentionally not exposed; consult the project’s tool documentation for the exact boundary.