Clide3D MCP server
Commit Oct 27, 2026A Maya-style 3D editor in Rust that allows AI agents to sculpt, rig, animate, and render scenes through 79 specialized MCP tools.
Also known as addamb/clide3d
- Stars
- 1
- Tools
- —
- Downloads, 30 days
- —
- Latest version
- —
- Last commit
- Oct 27, 2026
- License
- Apache-2.0
What is Clide3D MCP?
Clide3D is a Maya-style 3D editor in Rust that allows AI agents to sculpt, rig, animate, and render scenes through 79 specialized MCP tools.
Summary generated from the project's README
About Clide3D MCP server
Artists and developers can build, animate, and render complex 3D scenes by driving a Maya-style desktop editor through an AI agent. Clide3D functions as a local Rust-based application that exposes its entire feature set via 79 specialized MCP tools. This allows clients like Claude Code to perform high-level tasks such as sculpting clay models, rigging characters, or setting up environmental lighting while the user watches the viewport update in real time.
The system operates as a native binary without requiring Python or cloud connections, ensuring all edits land on the same undo stack used by manual mouse inputs. Users connect an MCP client to the local server running on a specific port via Streamable HTTP. Once connected, an agent can execute commands ranging from simple object creation to complex GPU path-traced film rendering and glTF exports. The toolset covers everything from hard-surface kitbashing and human character generation to simulated garments and hair grooming.
What you can do with it
- 1Automated scene generationAn AI agent can build a complete vehicle and place it in a specific environment with custom lighting.
- 2Character creation and riggingDevelopers can instruct an agent to generate a human base with full facial details and a functional rig.
- 33D printing preparationUsers can use the agent to convert meshes into clay and prepare them for physical printing.
Written from the project's README. Every use case is checked against a quote from it.
Configuration
CLIDE3D_MCP_PORT
Automated checks
Ran Nov 15, 2026Full report →Not verified yet. A server needs a score of 80, no serious finding, and enough data for us to check. How checks work · What to fix for more points
- Source repository linked and reachableaddamb/clide3d is public and reachablegithub.com/addamb/clide3d ↗Pass
- Package names this repository as its sourceNot checked
- Build provenance (Sigstore attestation)Not checked
- Open source license (OSI)Apache-2.0spdx.org/licenses/Apache-2.0.html ↗Pass
- Commit or release in the last yearLast commit or release 2026-10-27github.com/addamb/clide3d ↗Pass
- OpenSSF ScorecardNot checked
- Package name not close to a popular packageNot checked
- No critical advisory in the package or its dependenciesNot checked
- No hidden instructions to the model0 tool descriptions and the README read; no override phrases, credential paths or hidden charactersPass
- Destructive tools are labelledNot checked
- Remote endpoint answers the MCP handshakeNot checked
README
View on GitHubWhy Clide3D?
Most 3D tools are built for a person with a mouse. Clide3D is built for both: a familiar Maya-style desktop editor and a local Model Context Protocol server that exposes the whole editor as 79 typed tools. Point Claude Code (or any MCP client) at it and the agent can build, inspect, render and export a scene while you watch the window update live, then take over with the mouse at any point. Every agent edit lands on the same undo stack as yours.
Everything is one native Rust binary: no Python runtime, no plugins, no cloud.
Highlights
| Maya-style editor | Menu sets, shelf, Outliner, Channel Box / Attribute Editor, four-view layout, time slider, hotkey editor, and a MEL command line (polyCube -n box; move 0 2 0). |
| Clay sculpting | Signed-distance "blob" modelling (spheres, capsules, lathes, sweeps with exact round tubes, extrusions, arrays, shells, bands) with smooth or sharp joins, plus brush sculpting, painting and decals on a fine detail layer; ClayPolish, which takes lumps off and keeps creases, hard edges and lip and lid lines; strokes projected onto the surface so lines drawn along a strand stay on it across blob junctions; VDM stamps (Alpha 3D) captured from any clay and stamped back with their overhangs, and curve strokes whose control points can be moved after the fact (MoveCurve). |
| Interactive sculpting | Sculpt, Paint, Mask and Groups brush tools with a live preview, a brush HUD (size, strength, falloff curve, alpha, symmetry, layers, Adjust Last, history) and pen pressure (touch force, an opt-in macOS tablet monitor, or pointer speed). Every stroke is a record in a stroke ledger that can be listed, disabled, edited, replayed or undone on its own; sculpt and paint layers with amounts, morphs exported as blend shapes, persistent masks and polygroups, detail levels that keep fine detail under coarse edits, and Sculptris Pro local refinement. |
| 3D printing | Import OBJ, STL, PLY, GLB and FBX meshes (import_mesh), turn any object into clay and combine objects with add / carve / intersect booleans (to_clay), then export_print to STL, OBJ, PLY or 3MF in millimeters, sized, optionally hollowed or simplified, with fine detail only where detail regions ask for it, a triangle limit checked before building, and a watertight / non-manifold report by kind. |
| Hard surface | Chamfered panels, bolts, vents and cables (kitbash, detail_pass), forged armor plates, battle damage stamps and vehicle wear presets. |
| Characters | A built-in human base (MakeHuman CC0 mesh, 600+ shape controls) with a full rig, face detail and facial hair, textured eyes, strand hair, and simulated, sewn garments. |
| Rigging and animation | Bones, weight painting, keyframe clips with smooth/linear/step keys, and posing that carries props and armor along. |
| Smart materials | Layered, Substance-style looks (worn iron, gold trim, old leather, dungeon stone…) over a CC0 scanned texture library, with dirt, rust, edge wear and cavity masks. |
| Environments | A modular dungeon kit, heightfield terrain, scatter, torch/candle/brazier lights and simulated fire and smoke. |
| Film renderer | A GPU path tracer (WGSL compute, with a CPU fallback) with soft studio lights, HDR skies, depth of field, motion blur, fog, bloom, film looks and denoising; render passes (depth, normal, albedo, AO, shadow, mask, emission) as PNG or EXR, and animations as PNG sequences or mp4 (through an installed ffmpeg). |
| Viewport graphics | The live viewport is lit like the film renderer: key-light shadow maps (with optional contact-hardening soft shadows), screen-space ambient occlusion, image-based lighting from the environment, HDR bloom and ACES / AgX / filmic tonemapping, a physical sun and sky, matcaps, and instanced drawing of repeated geometry (scatter, kitbash, instance_array). |
| Game-ready output | Bake clay to a triangle budget with UV unwrap, texture maps and displacement / vector-displacement maps (16-bit PNG or EXR), then export glTF (.glb) or FBX 7.4 with rigs, animation and materials. |
Gallery
The pictures in the *_check/ folders are native Clide3D renders, and each
folder includes the recipe to reproduce them (see Testing).
Quick start
You need a recent stable Rust toolchain (the crate uses the 2024 edition, so
Rust 1.85 or newer) and a GPU that wgpu supports.
git clone https://github.com/addamb/clide3d.git
cd clide3d
cargo run --release
Use --release: sculpting, meshing and rendering are much slower in debug
builds.
Platform note: Clide3D is developed and tested on macOS (Apple Silicon). It is built on cross-platform crates (
wgpu,eframe,rfd), so Windows and Linux should work, but they are not yet tested. Reports and fixes are welcome.
Driving it with an AI agent
While the editor is open it serves MCP over Streamable HTTP at
http://127.0.0.1:7878/mcp. It listens only on localhost and rejects
non-local browser origins.
Claude Code, from any folder:
claude mcp add --transport http clide3d http://127.0.0.1:7878/mcp
Inside this repository, .mcp.json already registers it. Then just ask:
"Build a modern Formula 1 car, give it a livery, then put it on a race track and render it at golden hour."
To run several editors side by side, give each one its own port:
CLIDE3D_MCP_PORT=7879 cargo run --release
Any MCP client works. Under the hood each tool is a plain JSON-RPC call:
curl -s http://127.0.0.1:7878/mcp \
-H 'content-type: application/json' \
-d '{"jsonrpc":"2.0","id":1,"method":"tools/call",
"params":{"name":"create_object",
"arguments":{"shape":"Sphere","name":"ball","translate":[0,1,0]}}}'
| Area | Tools |
|---|---|
| Scene | get_scene, new_scene, open_scene, save_scene, undo, redo, history, run_mel |
| Objects | create_object, update_object, delete_object, duplicate_object, select_object, group_objects, parent_objects, set_pivot, mirror_object |
| Clay and surfaces | edit_clay, get_clay, sculpt, paint, sculpt_layer, detail_level, morph, mask, group, brush_preset, alpha, decal, surface_point, to_clay |
| Polygon objects | poly (from clay, Catmull-Clark subdivision levels, semi-sharp creases, UVs, clay detail projected onto the levels as vector displacement), retopo (field-aligned quad retopology), export_poly (the subdivision cage as OBJ, GLB or USDA with displacement, normal, color and AO maps, checked by reading the files back; udim: true writes UDIM texture tiles and per-tile maps); UDIM texture tiles painted with paint and baked from clay with bake udim: true; render_film renders Polys subdivided and displaced about a pixel fine (subdiv_max_level, displacement, dice_rate, max_diced) |
| Stroke ledger | stroke_log, stroke_edit, sculpt_diff, probe_clay |
| Reference images and quality | set_reference (one image per view, or a turnaround sheet split into views at one scale with image planes), compare_reference, project_reference, quality_report, guides (proportion guides: head units, eye and centre lines and proportion targets, measured on the clay's field and against a turnaround sheet; drawn over views, never exported) |
| Materials and wear | set_material (presets, including the stylised skin_stylized, lips_stylized, cheek_blush, fabric_soft, with overrides and apply_to), wear, damage |
| Hard surface | kitbash, detail_pass |
| Characters | create_character (a stylised cartoon base of named, blended blobs from proportions alone: head units, head width, body, limbs, hands, feet, eyes and ears, biped or quadruped, with stylised eyes in carved sockets under eyelids that wrap the eyeball, a rig and proportion guides that measure back; edit_clay lid blobs fill eyelids from any Eye object), create_human, set_human, human_controls, face_detail, face_hair, groom (comb, lengthen, shorten, cut, clump, twist, smooth, puff and relax a Hair's guides, kept out of the head; the editor's Groom tool sends it; a Hair's grow {fur: true} covers a whole clay body in short fur combed down the body and out along the limbs, coloured from the clay at each root, excluding named parts and the eyes), cloth |
| Rigging and animation | rig, pose_bone (posing in place; mirrored blobs that a move turns unevenly, such as a head tilt or one arm, are written out as their two sides and each side follows its own bone), animate, playback |
| Environments | kit, scatter, instance_array, edit_terrain, fire |
| Camera and view | set_camera, frame_view, set_display, screenshot |
| Rendering | render_film, render_views, render_animation, job_status |
| Import and output | import_mesh, bake, export_glb, export_fbx, export_print, check_export |
Long work (renders, bakes, simulations, exports) runs as cancellable
background jobs with a progress bar in the editor; job_status polls them.
Viewport lighting. The viewport (and render_views,
render_animation) is lit like render_film: by default its studio
environment and studio lights, with key-light shadows, screen-space
ambient occlusion and ACES finishing. set_display takes lighting
("studio", an environment such as "sunset" or "overcast", a look
preset, "film" for the last render_film's lighting, "classic" for the
old fixed studio, or {environment, lights, extra_lights, look} as
render_film takes them) and ambient_occlusion (true/false or
{radius, strength}), so a film look can be previewed live; the
Lighting menu offers the same. See graphics_check/README.md.
Using the editor
| Action | Keys |
|---|---|
| Orbit | RMB drag, or Alt + LMB |
| Pan | MMB, Shift + RMB, or Shift + scroll (two fingers on a trackpad) |
| Zoom toward the mouse | Scroll, pinch, or Alt + RMB |
| Orbit around a spot | Double-click a model |
| Select / move / rotate / scale | Q / W / E / R |
| Grid snap · edit pivot | Hold X · hold D |
| Wireframe / shaded | 4 / 5 |
| Single / four view | Space |
| Frame selected / frame all | F / A |
| Group · parent · unparent | Ctrl+G · P · Shift+P |
| Hide / show | Ctrl+H / Shift+H |
| Brush tools: finer / coarser detail level · X symmetry | D / Shift+D · X (instead of pivot and snap while a brush tool is on) |
| Brush tools: size · strength · focal shift | Hold S · U · O and move the mouse sideways |
| Poly objects: finer / coarser shown subdivision level | Page Up / Page Down |
| Brush tools: smooth · invert · mask · erase mask · lasso | Shift · Alt · Ctrl · Ctrl+Alt · Ctrl+Shift (RMB orbits) |
| Play animation | Alt+V |
| Undo / redo | ⌘Z / ⇧⌘Z |
| Duplicate · delete | ⌘D · ⌫ |
| Save · open | ⌘S · ⌘O |
Selection works like Maya: click, Shift-click to toggle, Ctrl-click to remove, or drag a box; the last selected object is the lead (green). In the Outliner, drag rows onto each other to parent them. Rebind anything in Windows → Settings/Preferences → Hotkey Editor.
Scenes are saved as .json files.
Documentation
The user guide covers every feature in depth: sculpting from reference images, wing membranes, materials and eyes, hair, film renders, adaptive detail, interactive sculpting (brushes, the HUD, the stroke ledger, layers, masks, detail levels, VDM stamps and curve strokes), 3D printing, viewport graphics, render passes and movies, environments, human bases and faces, animation, garments, forged armor, kitbashing, mirroring and posing, fire and smoke, battle damage, photographic camera looks, and export.
How it works
src/
├── main.rs window setup (eframe + wgpu)
├── app/ the editor: panels, viewport, tools, jobs, timeline, MCP tool handlers
├── mcp.rs the MCP server (tiny_http, JSON-RPC, tool schemas)
├── scene.rs the saved scene model
├── clay.rs signed-distance clay → adaptive meshes
├── hard_surface.rs extrude / lathe / sweep / shell / array / band forms
├── tube.rs exact tube fields for sweeps (field: segments)
├── brush/ strokes: spec, resolver, falloff and pressure curves, symmetry, alphas and VDM stamps
├── sculpt/ the sculpt engine and brushes
├── paint.rs, surface.rs, detail.rs, adaptive.rs
├── quality.rs, guides.rs field quality measures and proportion guides
├── rig.rs, pose.rs skeletons, skinning and posing
├── character.rs stylised character bases from proportions
├── human.rs, face.rs, eyeball.rs, hair.rs, face_hair.rs, groom.rs
├── cloth.rs, fire.rs, damage.rs, weather.rs
├── material.rs, smart.rs PBR materials and layered smart materials
├── render.rs the real-time viewport renderer
├── film/ the path tracer: BVH, shading, lighting, dicing, denoise, GPU (trace.wgsl)
├── bake.rs, export_atlas.rs game-ready meshes, UVs (xatlas), texture and displacement maps
├── outputs.rs 16-bit PNG / EXR files and mp4 through an external ffmpeg
├── mesh_import/, mesh_asset.rs, to_clay.rs mesh import, print export, clay from any object
└── gltf.rs, fbx.rs, glb_read.rs export and re-import checks
Clay objects are lists of signed-distance "blobs" that are meshed on demand,
across all CPU cores, into adaptive triangle meshes. The viewport draws them
with wgpu. Film renders path-trace the same meshes on the GPU when they fit
in GPU memory, and on the CPU otherwise. The MCP server runs on its own
thread and hands each call to the UI thread, so agent edits and mouse edits
share one scene, one selection and one undo history.
Testing
cargo test --release
This runs 659 fast unit and integration tests. Another 58 are
#[ignore]d: visual acceptance checks that render the pictures in the
*_check/ folders, and timing reports; each folder's README.md says what it verifies and how to
reproduce it, for example:
cargo test --release kitbash_catalog -- --ignored --nocapture
Contributing
Issues and pull requests are welcome. Before opening a PR:
- Run
cargo test --release, andcargo clippyif you have it installed. - If your change affects how things look, rerun the matching
*_checktest and include before and after pictures. - Keep new MCP tools typed and documented in
src/mcp.rs, so agents can discover them.
Third-party assets
- Human base mesh and shape targets: converted from
MakeHuman, CC0 1.0. See
assets/makehuman/LICENSE.md. - Detail texture library: from ambientCG, CC0
1.0. See
assets/textures/LICENSE.md.
Clide3D's interface is inspired by Autodesk Maya. Clide3D is an independent project and is not affiliated with or endorsed by Autodesk. Maya is a trademark of Autodesk, Inc.
License
Licensed under either of
- Apache License, Version 2.0 (LICENSE-APACHE)
- MIT license (LICENSE-MIT)
at your option.
Unless you explicitly state otherwise, any contribution intentionally submitted for inclusion in the work by you, as defined in the Apache-2.0 license, shall be dual licensed as above, without any additional terms or conditions.
Clide3D MCP questions
How can an AI agent use Clide3D?
AI agents can drive the editor through a built-in MCP server that exposes the entire editor as 79 typed tools, allowing them to build, inspect, render, and export scenes.
Does Clide3D require external runtimes like Python?
No, everything is contained within a single native Rust binary with no Python runtime, plugins, or cloud requirements.
Can I use the editor manually while an agent is working?
Yes, you can take over with the mouse at any point, and every agent edit lands on the same undo stack as yours.