MCP For Maya

What mcp-for-maya does

The mcp-for-maya MCP server gives agents access to Autodesk Maya for procedural modeling, scene planning, inspection, validation, and delivery. It adds a scene-intelligence layer around the Maya connection, allowing an agent to examine spatial state, object relationships, materials, and visual output instead of relying only on generated code.

The workflow supports both construction and review. An agent can inject reusable Python modules or run code directly, inspect the resulting scene, apply planning or cleanup steps, and verify the result with audits or visual captures. Scene export supports FBX, OBJ, and USD for the whole scene or selected named objects.

Tools and capabilities

The mcp-for-maya MCP server exposes capabilities in several groups:

• Spatial inspection: scene_snapshot, scene_inspect, and scene_measure provide scene-level information and distance, overlap, and gap measurements.
• Scene analysis: scene_aesthetics evaluates color use, composition, proportions, lighting, and visual flow.
• Planning and validation: scene_plan offers organization and layout guidance; scene_review, scene_validate, and scene_assert support deterministic checks, custom constraints, and state assertions.
• Code-based editing: execute_code runs arbitrary Python in Maya, while write_module adds reusable modules.
• Recovery: scene_checkpoint, scene_rollback, and scene_checkpoint_list support in-memory scene snapshots and explicit rollback.
• Visual feedback: scene_viewport_snapshot captures the viewport, and scene_render_preview creates a single-frame playblast preview in GUI sessions. playblast can capture orbit sequences.
• Cameras and sessions: camera_create, camera_orbit, list_sessions, add_session, and maya_setup_guide cover camera planning, animation, session discovery, attachment, and connection guidance.
• Assets and export: asset_search and asset_import use Poly Haven CC0 models with host-side downloads, while scene_export writes FBX, OBJ, or USD output.
• Scene graph inspection: scene_describe and scene_nodes expose node types, attribute metadata, and connection information.

Limitations and notes

The mcp-for-maya MCP server runs arbitrary Python inside Maya. Its validation, rate limiting, and audit pipeline is intended to reduce accidents and handle injected instructions; it is not a security boundary against a malicious client. Use it only with a trusted connected agent.

Visual render previews require a Maya GUI session. Asset importing currently covers Poly Haven models, including FBX import and texture wiring; HDRIs and texture packs remain on the roadmap. AI model generation and first-class object CRUD are outside the stated scope, with object operations available through execute_code instead.

Asset downloads occur on the host through HTTPS with host allowlisting, MD5 verification, size limits, sanitized filenames, caching, and polycount and dimension guards. Maya itself does not access the network for this path. Export format is inferred from the file extension, and conflicting format information produces an error rather than an implicit choice.