This server inspects an open Autodesk Maya scene and runs native Maya commands through a bridge.
scene_context — read scene metadata: current scene, selection, roots, units, time, plugins, and node counts.
scene_naming — summarize naming prefixes, suffixes, control families, and NURBS control candidates.
scene_hierarchy — dump a compact DAG hierarchy from roots or selection, with depth, type filters, and shape toggles.
scene_connections — trace plug/node connections inward or outward, filtered by node type and depth.
viewport_capture — capture the active viewport or a chosen camera as a PNG image.
maya_command — low-level fallback to run a single maya.cmds command or a batch in one undo chunk.
Provides tools for inspecting and editing a running Autodesk Maya scene, including scene context, naming, hierarchy, connections, viewport capture, and executing native Maya commands.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type @ followed by the MCP server name and your instructions, e.g., "@Maya MCP Show the scene hierarchy under my character root joint"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Maya MCP connects an AI client to an open Autodesk Maya scene. It has two parts: an external MCP server and a small bridge running inside Maya.
Python 3.10 or newer for the external MCP server.
Autodesk Maya with pyzmq installed in Maya's Python environment.
Rig Builder and RigSystem available in Maya for reusable, module-based rig workflows. Scene inspection and direct MCP tools can be used without them.
Related MCP server: maya-mcp
Install the MCP server in a regular Python environment outside Maya:
cd D:\path\to\maya_mcp
py -m venv .venv
.\.venv\Scripts\python.exe -m pip install -e .In your MCP client, configure the server to run:
D:\path\to\maya_mcp\.venv\Scripts\python.exe -m maya_mcp.mcp_serverIn Maya's Python Script Editor, start the bridge:
import sys
project_path = r"D:\path\to\maya_mcp"
if project_path not in sys.path:
sys.path.insert(0, project_path)
import maya_mcp
maya_mcp.start()The default local endpoint is tcp://127.0.0.1:51608. Set the same
MAYA_MCP_ENDPOINT in both environments to change it. Optionally, set the same
MAYA_MCP_TOKEN in both environments to protect the connection. Stop the
bridge from Maya with maya_mcp.stop().
The server provides these tools:
scene_context — current scene, selection, roots, units, references, and counts.
scene_naming — naming patterns and likely control families.
scene_hierarchy — a focused DAG hierarchy.
scene_connections — connections between nodes and attributes.
viewport_capture — an image of the Maya viewport.
maya_command — a low-level fallback for native maya.cmds calls.
For rig edits, the intended workflow is to find or compose modules in Rig Builder and use RigSystem's high-level APIs from those modules. Inspect and verify the scene with Maya MCP before and after running a workflow. Do not guess ambiguous inputs such as edge loops or guide curves; provide them as module inputs and run the module after they are specified.
AI workflow guidance is included in the server instructions and available as
the maya://ai-workflow MCP resource.
Execute one native maya.cmds command or a batch in a single undo chunk.
Inputs: args, kwargs, command, commands. Returns: object
Follow compact input/output plug connections from nodes or plugs.
Inputs: depth, targets, direction, exclude_types, +2 more. Returns: object
Get scene metadata, selection, roots, units, time, and node counts.
Inputs: root_limit, count_types, include_plugins. Returns: object
Read a compact text DAG hierarchy from roots or the current selection.
Inputs: depth, roots, max_nodes, include_types, +1 more. Returns: object
Summarize common prefixes, suffixes, families, and NURBS control candidates.
Inputs: family_limit, max_examples, prefix_limit, suffix_limit. Returns: object
Capture the active Maya viewport or a specified camera and return it as a PNG image.
Inputs: panel, width, camera, height, +2 more.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Scored across 6 tools
The four scene_* inspection tools have distinct targets: metadata, naming patterns, hierarchy, and connections. The only ambiguity comes from maya_command, a generic escape hatch that can overlap with every specialized tool, though its intended use as a native-command executor is clear.
All names use consistent two-word snake_case with clear domain prefixes such as scene_ and viewport_. The convention is predictable and readable even though it is noun-oriented rather than verb_noun.
Six tools is a well-scoped set for Maya scene inspection plus command execution. Each tool has a focused role, and there is no bloat or missing obvious specialization.
The set covers key read operations, viewport capture, and arbitrary command execution, so agents are not blocked. It lacks dedicated structured tools for common write or attribute-editing workflows, but maya_command provides a workaround.
Control Unreal Engine to browse assets, import content, and manage levels and sequences. Automate…
Build and inspect browser-based 3D games: projects, scenes, Lua scripts, assets and publishing.
Search, inspect, organize, annotate, share, and automate creative assets in Shade.
Connect your AI assistant to Blender for 3D modeling, Geometry Nodes, materials, lighting, animation, rendering and export. Inspect real scenes and viewport images, refine the result and restore checkpoints. OAuth connects your chat to Blender Bridge Desktop on an online Windows 10/11 x64 computer running Blender 4.2+. The chat can run on another device. Requires an active Blender Bridge account; 7-day trial available. AI model access is separate.
