Turn your DCC instances into one creation pipeline, powered by Meshy and your agent.
Meshy DCC Core gives an AI agent one local entry point to the 3D apps and game engines you have open. Prepare a connector for each app and configure native projects where required; every call goes to the exact running instance, and each app's tools load as skills when they are needed, so one agent can carry a Meshy model through every app it touches.
Documentation: docs.meshy.ai
| App | Versions |
|---|---|
| Blender | 4.5 – 5.2 |
| Unity | 2018.4 – 6000.5 |
| Godot | 4.4 – 4.7 |
| Unreal Engine | 5.0 – 5.8 |
| Maya | 2023 – 2027 |
| 3ds Max | 2023 – 2027 |
| Houdini | 20.5 – 22.0 |
| Substance 3D Painter | 10.0 – 12.1 |
| ZBrush | 2026.1 – 2026.2 |
| Roblox Studio | current release |
| FreeCAD | 1.0 – 1.1 |
| OpenSCAD | 2021.01; 2026.09 – 2026.10 snapshots |
| Material Maker | 1.7 |
On macOS (Apple Silicon) and Windows x64; 3ds Max on Windows only.
macOS:
curl -fsSL https://cdn.meshy.ai/meshy-dcc-core/install.sh | bashWindows (PowerShell):
irm https://cdn.meshy.ai/meshy-dcc-core/install.ps1 | iexOr with npm:
npm install -g meshy-dcc
meshy-dcc agent-skill --executePackage-managed deployments leave global agent Skills unchanged on ordinary
invocations. Run agent-skill --execute explicitly to install or update them;
automatic refresh remains available for direct CLI installations.
In mainland China, use cdn.meshy.cn in place of cdn.meshy.ai.
Then add a connector for each app, from meshy-dcc ui or with
meshy-dcc install --dcc-type <app>.
| Component | Role |
|---|---|
meshy-dcc |
CLI discovery, adapter preparation and project lifecycle, with the meshy-dcc agent Skill |
meshy-dcc-server |
The local MCP gateway for project lifecycle and exact-instance host execution |
meshy_dcc_core |
The Python runtime the connectors are built on |
Connectors live in meshy-dcc-adapters.
Meshy generation and your Meshy account stay with
meshy-cli.
Gateway and adapter integrations use the request metadata and deadline contract. MCP and CLI clients use the software preparation and project lifecycle contract. CLI clients can recover safe-stop ownership through the instance lifecycle contract.
Meshy DCC Core sends anonymous, aggregate usage counts once a day. Turn it off
with meshy-dcc telemetry off or DO_NOT_TRACK=1. See
docs/telemetry.md for every field.
Requires Rust 1.95.
cargo build -p meshy-dcc -p meshy-dcc-server
cargo test -p meshy-dccUse scripts/release/build_release.sh <output-directory> for portable release
artifacts. It checks for build-machine paths, installs the exact wheel offline
in a temporary environment and initializes its native extension. With the
pinned Rust 1.95 toolchain, macOS wheel builds avoid its defective Mach-O
stripping pass; Apple's strip tool removes local/debug paths and the native
member is re-signed before its wheel checksum is updated. CLI and server
executable profiles retain their usual stripping.