Skip to main content
Glama
meshy-dev

Meshy MCP Server

Official
by meshy-dev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Download Model or Image

meshy_download_model
Idempotent

Save a finished Meshy task's output locally: download a 3D model in one chosen format (GLB, OBJ, FBX, etc.), images, or Creative Lab parts. Returns URL if download fails.

Instructions

Save a finished task's output under meshy_output/ (project folders with history), or at save_to.

  • 3D tasks: ONE model format — ask the user which first (GLB viewing, OBJ white-model printing, 3MF multicolor printing, FBX game engines, USDZ AR, BLEND Blender); never download all. A format exists only if it was generated: 3mf needs target_formats ["3mf"] at creation, meshy_convert or meshy_process_multicolor.

  • Creative Lab: omit format to save every part.

  • Images and text-to-motion clips save their own files and ignore format.

  • Rigging and animation tasks are not saved: they return their file URLs. If a download fails, its URL is returned instead.

Example (print): { task_id: "abc-123", format: "obj", print_ready: true, print_height_mm: 100 }

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
formatNoModel format (default glb; omit for every Creative Lab part).
save_toNoAbsolute file path to save to instead of meshy_output/{timestamp}_{prompt}_{id}/
task_idYesTask ID
task_typeNoOptional: if omitted or wrong, the server finds the task and reports its real type.
print_readyNoOBJ only: rotate Y-up to Z-up, scale to print_height_mm, center, bottom at Z=0. Changes only the local file (free); meshy_resize (1 credit) rescales the model on Meshy.
parent_task_idNoEarlier task of the same chain (e.g. the preview of a refine); saves into its project folder.
print_height_mmNoHeight in mm with print_ready (default 75; '15 cm' → 150).
include_texturesNoAlso save the texture maps

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.4

TDQS

A4.9/5.0
Behavior5/5

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

Annotations only declare idempotent/non-destructive/openWorld, but the description adds substantial behavioral context: that files land on local disk, that a format only exists if generated at creation time (3mf prerequisites), and that a failed download returns the URL instead of erroring. These are non-obvious traits an agent could not infer from the schema or annotations.

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 the core action and destination, then organized into scannable bullets grouped by task type, closing with a concrete example call. Every sentence carries operational information; nothing is 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?

For an 8-parameter tool with no output schema, the description covers destination behavior, format prerequisites, per-task-type exceptions, failure handling, and includes a worked example. An agent has everything needed to invoke it correctly without further inference.

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 already 100%, so the baseline is 3, but the description genuinely adds meaning beyond the schema: it explains the format selection trade-off (never download all), the conditional relevance of format per task type, and the difference between print_ready's free local transform versus meshy_resize's credit-consuming server rescale.

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?

Opens with a specific verb and resource ('Save a finished task's output') and names the exact destination semantics (meshy_output/ with project folders, or save_to). It clearly distinguishes itself from siblings like meshy_convert, meshy_resize, and the generation tools by being the terminal save step.

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 explicit when-to-use rules per task class: 3D tasks require choosing ONE format (with a mapped rationale per format), Creative Lab omits format, images/motion clips ignore format, and rigging/animation tasks are not saved at all. It even instructs the agent to ask the user before downloading, which is actionable routing guidance.

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

Deploy Server

Other Tools