Maya Retopo MCP
Related Servers
Alternatives to Maya Retopo MCP
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceGives LLM agents spatial awareness inside Autodesk Maya, enabling scene inspection and measurement, aesthetic and engineering audits, camera planning, checkpoint/rollback safety, asset import, and viewport or render previews. Agents can also execute arbitrary Python in Maya to build and verify 3D scenes against engineering rules instead of writing blind.2576 PyPI5MIT
- FlicenseBqualityBmaintenanceEnables AI agents to control a live 3ds Max session directly, including creating and editing objects, materials, animation, and scene inspection, with undo support.17-
- AlicenseBqualityCmaintenanceEnables 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
- AlicenseBqualityBmaintenanceEnables AI agents to directly control Autodesk 3ds Max for modeling, shading, rigging, animation, rendering, baking, and engine export through MCP.3753MIT
- AlicenseNot gradedqualityNot gradedmaintenanceEnables AI assistants to connect to and control Autodesk Maya for 3D modeling, animation, and rendering operations through the Model Context Protocol, supporting object creation, transformation, scene queries, and Python command execution.MIT
- 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-
TDQS
Scored across 1 tool
With only a single tool there is no possibility of confusion; maya.health has a clearly distinct and well-defined purpose (connection/version/scene health check). No competing tools exist to misselect between.
The single name maya.health uses a readable namespace-dot convention, but with only one tool there is no pattern to verify against, so consistency cannot really be established.
A server branded as a retopology MCP exposing exactly one tool (a health check) is an extreme mismatch between stated purpose and surface area; the actual retopo operations are entirely absent.
The surface is severely incomplete: there are no tools for any retopology workflow (mesh inspection, retopo operations, bake/transfer, export), only a connectivity check, making real tasks dead ends.