tripo-studio-mcp
Related Servers
Alternatives to tripo-studio-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceEnables AI agents to create, manage, and download 3D models, textures, images, rigged characters, and animations through natural conversation using the Meshy AI platform.MIT

Meshy MCP Serverofficial
AlicenseAqualityBmaintenanceEnables AI agents to create, manage, and download 3D models, textures, images, rigged characters, and animations through natural conversation.2826,720 npm93MIT- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to interact with the Tripo3D AI API to generate 3D models from text, images, or multiview inputs. It supports advanced features like model animation, stylization, and real-time task status tracking.7ISC
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to create, edit, and export 3D models (GLB, USDZ) from natural-language descriptions and YAML, with rendering and problem detection.16 npmMIT

SpicyAPI MCP Serverofficial
AlicenseAqualityBmaintenanceOfficial MCP server for SpicyAPI, an unrestricted AI API with no platform content filter: browse 200+ image, video, audio and chat models, get exact USD quotes, upload local files, create generation tasks and collect results, with a confirmation before every paid step.15168 npm1MIT- AlicenseAqualityBmaintenancePublish 3D scenes, walkthroughs and worlds, from a single product to a whole city, as links that open in any browser on everyday devices. Your assistant can publish a file or public URL and get back a Verse link, embed code, a private share link or a guided camera tour. Sign in with Verse at https://verse.ctruh.com/mcp, no API key needed, or run it locally with npx.12480 npmMIT
TDQS
Scored across 18 tools
Most tools map to clearly distinct pipeline stages (generate, remesh, uv, rig, animate, segment, pbr, upscale), and descriptions explicitly disambiguate overlapping ones like tripo_texture vs tripo_pbr vs tripo_upscale. The weakest pair is tripo_image (2D image generation) vs tripo_generate_image (image-to-3D), whose names invite misselection even though the descriptions clarify.
All tools share a tripo_ prefix and snake_case, which is highly predictable. However, the stems mix verb_noun (generate_text, list_projects, download) with bare nouns/verbs (status, remesh, uv, rig, pbr, image, complete), so the pattern is recognizable but not uniform.
18 tools is slightly above the comfortable range, but this is a multi-stage 3D asset pipeline where each tool corresponds to a genuine, non-redundant operation. No tool looks padded, and consolidating further (e.g., merging rig/animate) would harm clarity.
Strong lifecycle coverage: import, text/image/multiview generation, remesh, texture, UV, rig, animate, segment, complete, PBR, upscale, plus discovery (list_projects, list_motions) and download. Gaps are operational rather than core — no delete/cleanup, no explicit cancel-job, and no asset/project metadata retrieval beyond listing.