mordor-forge/trident-mcp
by Various
Multi-provider 3D model generation MCP server (Tripo, Meshy, Rodin). Text/image/multiview-to-3D, retopology, format conversion, stylization.
MCP
mordor-forge/trident-mcp
Added 1 June 2026
Overview
Trident MCP is a Go-based server that provides a unified interface for generating 3D models from multiple providers including Tripo, Meshy, and Rodin. It supports text-to-3D, image-to-3D, and multiview-to-3D conversion along with retopology, format conversion, and stylization capabilities.
Best for
Best for
Developers building pipelines that need to switch between 3D model generation services.
Use cases
- Generate 3D assets from text prompts or images for prototyping
- Convert between 3D formats and apply retopology in pipelines
- Stylize existing 3D models using different provider backends
Notes
Trident MCP is a Go-based server that provides a unified interface for generating 3D models from multiple providers including Tripo, Meshy, and Rodin. It supports text-to-3D, image-to-3D, and multiview-to-3D conversion along with retopology, format conversion, and stylization capabilities.
3 stars on GitHub. Last updated 2026-05-07. Licensed Apache-2.0.
Use cases
- Generate 3D assets from text prompts or images for prototyping
- Convert between 3D formats and apply retopology in pipelines
- Stylize existing 3D models using different provider backends
Pros
- Supports multiple 3D generation providers through one interface
- Includes retopology and format conversion for production workflows
- Lightweight Go implementation with MCP protocol for tool integration
Cons
- Limited to 3 developers with no community contributions or issues resolved
- Dependency on external provider APIs which may have costs or rate limits
- No built-in fallback or caching for provider failures
Indexed from awesome-mcp-servers-punkpeye and enriched against its public facts.
Pros
- Supports multiple 3D generation providers through one interface
- Includes retopology and format conversion for production workflows
- Lightweight Go implementation with MCP protocol for tool integration
Cons
- Limited to 3 developers with no community contributions or issues resolved
- Dependency on external provider APIs which may have costs or rate limits
- No built-in fallback or caching for provider failures
Pairs with
Other entries in the index that connect to this one. Click through to see the chain.