Trident MCP

What mordor-forge/trident-mcp does

The mordor-forge/trident-mcp MCP server connects an MCP client to Tripo v3 for AI-assisted 3D asset workflows. It covers model generation from text, images, or multiple views, along with several post-processing operations. The documented tool surface includes image preparation, splat workflows, file upload and download, format conversion, retopology, stylization, texture and refinement operations, segmentation, completion, rig checks, rigging, animation retargeting, and model or configuration inspection.

Supported output formats listed by the project include GLB, FBX, OBJ, STL, and USDZ. Generated files are downloaded to a local output directory, which defaults to ~/generated_models unless changed through configuration.

How it works

The mordor-forge/trident-mcp MCP server is implemented in Go and communicates with MCP clients through a local stdio process. Its current provider implementation calls the Tripo v3 API, while provider capability interfaces define the boundary for those API operations.

Many generation requests are asynchronous. A client starts a task and uses polling-related functionality to determine when processing is complete before downloading or continuing with later operations. API calls for generation, task status, downloads, and post-processing use the configured Tripo credentials. Live end-to-end tests can create real generation jobs and consume Tripo credits when the relevant opt-in flags are enabled.

Setup and configuration

Build the binary from the repository with Go, then start it with the Tripo credential in the environment:

go build -o ./trident-mcp ./cmd/trident-mcp
TRIPO_API_KEY=tsk_your_key_here ./trident-mcp

TRIPO_API_KEY is required. TRIPO_BASE_URL is optional and defaults to https://openapi.tripo3d.ai/v3; it can point the server at a private deployment or test endpoint. MODEL_OUTPUT_DIR optionally changes where downloaded models are saved.

An MCP client can launch the compiled trident-mcp executable as a stdio server and pass these variables in its server configuration. The executable must be built locally because the provided setup instructions describe compiling the Go project rather than installing a published package.

Tools and capabilities

The mordor-forge/trident-mcp MCP server is intended for agent-driven 3D asset pipelines, including:

• Creating models from text, a single image, or multiple views.
• Preparing images and handling splat-related workflows.
• Uploading source files and downloading generated results.
• Converting models between documented 3D formats.
• Applying retopology, stylization, texturing, refinement, segmentation, and completion operations.
• Checking rigs, rigging models, and retargeting animations.
• Inspecting model and service configuration, account balance, and usage.
• Starting asynchronous work and checking task progress.

Limitations and notes

The project documentation identifies Tripo v3 as the current backend, so available behavior depends on that API and its documented quirks. A valid Tripo API key is needed for runtime operations. Some live tests can spend account credits, and the repository recommends reviewing its operational documentation before enabling them. The server is described as a local stdio binary; no hosted endpoint or specific MCP desktop client is identified in the provided material.

Getting started with this mordor-forge/trident-mcp MCP server

Always refer to the official documentation for the most accurate and up-to-date information.