Maya MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MAYA_MCP_TOKEN | No | An optional matching token that can protect the local Maya MCP endpoint. | |
| MAYA_MCP_ENDPOINT | No | The ZMQ endpoint used by both the MCP server and the Maya bridge. Override the default endpoint in both processes with MAYA_MCP_ENDPOINT. | tcp://127.0.0.1:51608 |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| logging | {} |
| prompts | {
"listChanged": true
} |
| resources | {
"subscribe": false,
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| scene_contextC | Get scene metadata, selection, roots, units, time, and node counts. |
| scene_namingC | Summarize common prefixes, suffixes, families, and NURBS control candidates. |
| scene_hierarchyC | Read a compact text DAG hierarchy from roots or the current selection. |
| scene_connectionsC | Follow compact input/output plug connections from nodes or plugs. |
| viewport_captureC | Capture the active Maya viewport or a specified camera and return it as a PNG image. |
| maya_commandC | Execute one native maya.cmds command or a batch in a single undo chunk. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
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.