codex-meshy-multiview
Related Servers
Alternatives to codex-meshy-multiview
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityBmaintenanceMCP server that exposes ComfyUI image and 3D generation as a single tool with smart prompt classification. It enables AI assistants to generate assets directly by selecting and running the appropriate ComfyUI workflow.-
- AlicenseNot gradedqualityCmaintenanceMCP server for Meshwright, enabling agents to create 3D models from text prompts via a LangGraph pipeline. Supports configurable image providers, background removal, and TRELLIS reconstruction backends.MIT
- AlicenseBqualityBmaintenanceAI 3D model generation and post-processing MCP server — text/image/multiview-to-3D via Tripo, retopology, format conversion (GLB/FBX/OBJ/STL/USDZ), and stylization. Single Go binary, 10 tools.296Apache 2.0
- AlicenseNot gradedqualityBmaintenanceAn MCP server that enables an image-to-3D-to-rigged character pipeline, offering tools to generate images with FLUX, create textured 3D meshes with TRELLIS, and rig characters with SkinTokens/TokenRig, all driven through MCP.GPL 3.0
- FlicenseAqualityCmaintenanceStandalone MCP server and CLI for generating images via ChatGPT backend, with reliable exact file paths and multi-account login support.25-
- FlicenseBqualityBmaintenanceEnables local CLI and MCP agents to drive Tencent Hunyuan 3D web workbench for multi-view uploads, model generation, background task monitoring, automatic downloads, and Blender asset handoff using the user's existing web login and quota.19-
TDQS
Scored across 8 tools
Each tool has a distinct role in the workflow, and the paid-task boundaries are clearly marked. There is mild potential confusion between meshy_advance_workflow and meshy_workflow_status, but the local-vs-remote distinction is clearly described.
All tools share a consistent meshy_ prefix and use snake_case, which is easy to follow. Minor deviations like meshy_doctor (noun) and meshy_workflow_status (noun_noun) break the otherwise verb_object pattern.
Eight tools is well-scoped for a 3D generation workflow: credential check, planning, paid submission, workflow advancement, status, download, recovery, and task listing. No tool feels redundant or unnecessary.
The core lifecycle from planning through submission, remesh, status, and download is covered, including a recovery path for uncertain submissions. Minor gaps exist around cancellation, cleanup, or credential configuration, but agents can complete the main workflow without dead ends.