Meshy MCP Server

Official

Overview Schema Source Related Servers Discussions Admin

Auto-Rig 3D Character

meshy_rig

Auto-rig a textured humanoid GLB for animation, producing rigged models with walk and run animations ready for download.

Instructions

Auto-rig a humanoid character for animation. Cost: 5 credits, including free walking + running animations (GLB + FBX, separate files).

REQUIREMENT: a textured humanoid (biped) model with a clear body and limbs, ≤300,000 faces (checked first; remesh if over). model_url must be a .glb facing +Z. Generate characters with pose_mode "t-pose" for the best rig.

Next steps: meshy_download_model (task_type "rigging") returns the rigged model and walk/run URLs. Other actions: meshy_list_animations → meshy_animate. A described motion: meshy_text_to_motion → meshy_animate with motion_task_id.

Input Schema

Name	Required	Description	Default
`model_url`	No	Public URL of a textured humanoid .glb (max 400 MB), or a GLB data URI (max 100 MB)
`height_meters`	No	Character height in meters; helps scaling
`input_task_id`	No	A SUCCEEDED task with a textured humanoid model
`response_format`	No	markdown (default) or json	markdown
`texture_image_url`	No	Deprecated: leave it out when the model has its own textures (Meshy models and most GLBs do), which the rig keeps. Sending it makes this image the only texture and drops the PBR maps. Only for a model_url GLB without textures: its UV-unwrapped base color (.png, max 20 MB)

Output Schema

Name	Required	Description	Default
`status`	Yes
`message`	Yes
`task_id`	Yes
`estimated_time`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv0.6.6Oct 28, 2026

changedInput schema / properties / texture_image_url / description

Previous value: -"The model's UV-unwrapped base color texture (.png, max 20 MB)"New value: +"Deprecated: leave it out when the model has its own textures (Meshy models and most GLBs do), which the rig keeps. Sending it makes this image the only texture and drops the PBR maps. Only for a model_url GLB without textures: its UV-unwrapped base color (.png, max 20 MB)"

First observedv0.6.4Oct 15, 2026

TDQS

A4.9/5.0

Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Adds substantial context beyond annotations: a hard cost figure (5 credits, animations included), the face-count validation that runs before rigging with the remesh remedy, orientation constraint, and the deprecation consequence for texture_image_url (drops PBR maps). These are exactly the operational facts annotations cannot carry.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with purpose and cost, then requirements, then next steps. Sentences are dense but every one carries constraints an agent needs; no filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Covers cost, prerequisites, failure/remedy path, and downstream tool routing for a non-idempotent paid generation tool. With an output schema present, return values needn't be explained, and the next-steps block names the retrieval tool anyway.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline is 3; the description adds real semantics the schema lacks – .glb must face +Z, the face-count gate tied to model_url, and guidance that pose_mode 't-pose' yields the best rig. Slight room left since model_url vs input_task_id alternation isn't spelled out.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific action verb (auto-rig) on a specific resource (humanoid character for animation) with the deliverable named (walking + running animations, GLB + FBX). It's clearly distinct from sibling meshy_animate, which applies animations rather than producing the rig.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicit prerequisites (textured humanoid biped, ≤300k faces checked first, .glb facing +Z, pose_mode t-pose), plus routing to alternatives: meshy_download_model with task_type 'rigging', meshy_list_animations → meshy_animate, and meshy_text_to_motion → meshy_animate for described motions. When, prerequisites, and alternatives all present.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.