Meshy MCP Server

Official

Overview Schema Source Related Servers Discussions Admin

Animate Rigged 3D Character

meshy_animate

Animate a rigged 3D character by applying preset actions or a text-to-motion task, producing one or multiple animation clips for download and game-engine use.

Instructions

Animate a rigged character (rig_task_id). Cost: 3 credits per action. Give exactly ONE of action_id, action_ids or motion_task_id.

meshy_rig already returns walking and running free, as separate files; include their ids in action_ids only to bundle them into one multi-clip file. meshy_download_model (task_type "animation") returns the file URLs.

Example: { rig_task_id: "abc-123", action_ids: [1, 4, 92] }

Input Schema

TableJSON Schema

Name	Required	Description	Default
`action_id`	No	One preset action; find ids with meshy_list_animations (free), never guess.
`action_ids`	No	1–10 unique preset ids, returned as ONE file with one clip per action, in this order (e.g. for a game-engine state machine).
`rig_task_id`	Yes	The SUCCEEDED rigging task
`post_process`	No	Optional post-processing
`motion_task_id`	No	A SUCCEEDED meshy_text_to_motion task (biped rigs only; within 3 days, before the clip expires).
`response_format`	No	markdown (default) or json	markdown

Output Schema

TableJSON Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.6.4Oct 15, 2026

TDQS

A4.6/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint=false, idempotentHint=false, destructiveHint=false), and the description adds genuinely useful context the annotations don't: the 3-credits-per-action cost and the fact that file URLs come from a separate download tool, implying a task-based async flow. It stops short of stating task/polling behavior explicitly.

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?

Three short, front-loaded blocks: core action and cost first, the mode constraint second, then the sibling workflow note and a compact example. No sentence is redundant.

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

Completeness4/5

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

With an output schema present and 100% schema description coverage, the description needn't explain return values, and it does supply the key non-schema facts (cost, mutual exclusion, download path). It could be slightly more explicit that the call creates an asynchronous task, but coverage is otherwise complete.

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 the baseline is 3, but the description adds real value beyond the schema by declaring the mutual exclusion of the three animating inputs and explaining why action_ids bundles clips into one file. The example object reinforces the intended call shape.

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 verb and resource: 'Animate a rigged character (rig_task_id)'. It distinguishes itself from siblings by referencing meshy_rig (which produces the rig) and meshy_download_model (which retrieves files), so an agent can tell what this tool is responsible for without opening the schema.

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?

Gives an explicit either/or constraint ('exactly ONE of action_id, action_ids or motion_task_id') that selects the correct mode, and it clarifies the workflow boundary with meshy_rig (walking/running are already free) and how to retrieve results via meshy_download_model.

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