Meshy AI MCP Server
Related Servers
Alternatives to Meshy AI MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceEnables to generate 3D models from text and images, apply textures, and remesh models using the Meshy AI API.6MIT
- AlicenseNot gradedqualityDmaintenanceGenerates 3D models, textures, rigs, animations, and 3D-print files from Meshy AI, plus image generation and task management tools.MIT
- AlicenseAqualityDmaintenanceEnables AI assistants to generate 3D models, textures, and images via the Meshy API using natural language, supporting text-to-3D, image-to-3D, remeshing, retexturing, rigging, and animation workflows.3618 npm1MIT
- AlicenseAqualityFmaintenanceEnables Claude to generate 3D models from text or images, apply textures, and export to GLB/FBX/USDZ using the Meshy AI API.63MIT
- 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.20,478 npmMIT
- AlicenseNot gradedqualityAmaintenanceEnables LLMs to control Blender for 3D scene creation, object manipulation, material assignment, shader configuration, modifier application, keyframing, and rendering via the Model Context Protocol.2GPL 3.0
TDQS
Scored across 51 tools
Most tools are distinguishable by action prefix and modality, so create_text_to_3d_task vs create_image_to_3d_task vs create_remesh_task are reasonably clear. However, the text_to_texture task family duplicates the retexture task family using the same underlying /v1/retexture API, creating real misselection risk across five pairs of tools.
The task tools consistently follow a snake_case action_resource pattern: create_, retrieve_, list_, stream_, and delete_ combined with the task type. The only deviation is get_balance, which is a unique account operation and does not disrupt overall predictability.
At 51 tools, the surface is far larger than a practical agent-facing set, with five similar operations repeated across ten task families. Some breadth is justified by Meshy's multiple modalities, but the duplicated text_to_texture/retexture family and per-task stream/list/delete tools make it excessively heavy.
Each task family has create, retrieve, list, stream, and delete coverage, plus balance retrieval, so the lifecycle is essentially complete. No obvious domain gap prevents an agent from running generation, refinement, rigging, animation, and cleanup workflows.