mcp-for-maya
Related Servers
Alternatives to mcp-for-maya
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityDmaintenanceEnables AI assistants to programmatically control Autodesk Maya via natural language using over 30 tools for 3D modeling, lighting, and animation. It connects through Maya's command port to facilitate procedural scene generation and complex production-ready workflows.1-
- AlicenseBqualityBmaintenanceConnects AI assistants such as Claude, Cursor, and VS Code to a running Autodesk Maya session through Maya's commandPort, exposing 23 tools for scene inspection, object creation and transforms, materials, attributes, rendering, file import/export, viewport screenshots, and arbitrary Python execution. This lets users build and modify Maya scenes, query scene data, and run renders using natural language.232MIT
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to control Autodesk Maya through natural language for scene creation, modeling, material assignment, and object manipulation.1MIT
- AlicenseBqualityBmaintenanceEnables AI agents to drive Autodesk Maya through semantic tools covering scene, object, material, animation, and rendering operations, paired with execute_python/execute_mel escape hatches and read-only resources. Also supports multi-instance routing, viewport capture for visual iteration, and asynchronous render job polling.221MIT
- AlicenseNot gradedqualityDmaintenanceEnables AI-assisted 3D modeling and scene control in Autodesk Maya through natural language commands, supporting object creation, transformation, material application, and more.28 npm8MIT
- AlicenseNot gradedqualityBmaintenanceEnables natural language control of Autodesk Maya through MCP, including scene queries, Python/MEL execution, viewport screenshots, tool invocation, and customizable body rigging.MIT
TDQS
Scored across 25 tools
The server provides explicit Boundary sections disambiguating overlapping scene tools, and most tools have clearly distinct purposes. However, the large cluster of scene_* analysis and validation tools (validate, review, plan, assert, aesthetics) could still cause misselection without careful reading.
All names use snake_case, but the convention is mixed: some use a domain prefix (scene_*, camera_*, asset_*), while others are bare verb_noun (list_sessions, write_module, execute_code). This is readable and mostly consistent, with minor deviations.
25 tools is heavy for a single server, even a complex Maya integration. While each tool appears purposeful, the count sits at the upper end of the borderline-heavy range and increases cognitive load.
The surface covers scene inspection, validation, checkpoints, camera, assets, export, rendering, sessions, and code execution. Minor gaps like explicit object creation/deletion or material editing are workable via execute_code, but not dedicated tools.