Xxx91n/mcp-for-maya

# mcp-for-maya
> MCP server giving AI agents spatial awareness of Autodesk Maya scenes
## What Is This
mcp-for-maya is a Model Context Protocol (MCP) server that lets LLM agents (Codex, Claude, etc.) directly drive Autodesk Maya for 3D modeling, scene planning, and engineering-grade delivery.
Forked from chadrik/maya-mcp-server, it adds a scene-intelligence layer on top of the upstream connection stack: spatial awareness, deterministic auditing, transactional safety, and a visual loop.
Key capability: the agent stops "writing blind" — it can perceive spatial state, materials, and object relationships, then verify changes against engineering rules.
> [!WARNING]
> This server executes arbitrary Python inside Maya — that is a designed capability, not a bug. The built-in validation / rate-limit / audit pipeline is a safety net for accidents and injected instructions, not a boundary against a malicious client; the connected agent is trusted. See docs/threat-model.md.
Every asset below is a real capture produced by this project's own tool chain — no mockups: scenes were built procedurally through executecode / writemodule (plus one live assetimport), frames rendered through scenerenderpreview, the audit pair via scenereview + sceneviewportsnapshot, and the orbit sequence captured frame-by-frame with playblast (Maya 2024 GUI session).
| Prompt | Result |
| writemodule → t20movement.build() — "parametric involute gear train caliber: true involute teeth, Geneva-striped plates, blue-steel screws, ruby jewels, spiral hairspring" | |
| writemodule → t20bonsai.build() — "low-poly L-system bonsai: recursive branching, faceted foliage pads, pot + moss + stones" | |
| assetimport("vintagepocketwatch") + assetimport("metaltoolchest") → t20workbench.build() — "horologist's workbench: imported assets with textures wired, procedural involute spares" | |
| writemodule → t20street.build() — "low-poly corner block: 11 parametric buildings, gable roofs, awnings, street furniture, parked vans" | |
| writemodule → t20teapot.build() — "Utah teapot recreation: revolve-profile body, Bezier tapered spout, ear handle, checkered floor" | |
| scenereview() on a bench littered with junk → sceneplan(autofix=True) + cleanup → scenereview() again — score 53.7 → 64.2 | |
Reproduce every frame with the scripts in .github/assets-src/.
## vs blender-mcp
An honest three-tier comparison with ahujasid/mcp-for-blender (measured 2026-09):
| Tier | Contents |
| Unique to this project | ICEV enforced workflow (in server instructions), CoS notation output, checkpoint/rollback transactional safety, sceneplan holistic planning (zone mapping + layout suggestions), multi-session management, 11 deterministic audit checks, playblast render preview with metadata |
| Unique to blender-mcp | Asset ecosystem breadth (Sketchfab/Hyper3D/Hunyuan3D), first-class object CRUD tools, AI-generated-model integrations, community scale |
| Shared | MCP tool surface, Poly Haven asset source, viewport screenshot feedback, arbitrary Python execution, local socket connection |
Poly Haven model search + import shipped in 0.2.0 (issue #2 thin slice: FBX + texture wiring; HDRIs and texture packs remain roadmap). AI generation and first-class object CRUD are explicitly out of scope — the latter is already covered by executecode.