Skip to main content
Glama

Related Servers

Alternatives to mcp-for-maya

No user-submitted related servers found.

    Related Servers

    • F
      license
      Not graded
      quality
      D
      maintenance
      Enables 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
      -
    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI assistants to control Autodesk Maya through natural language for scene creation, modeling, material assignment, and object manipulation.
      1
      MIT
    • A
      license
      B
      quality
      B
      maintenance
      Enables 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.
      22
      1
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI-assisted 3D modeling and scene control in Autodesk Maya through natural language commands, supporting object creation, transformation, material application, and more.
      23 npm
      7
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables natural language control of Autodesk Maya through MCP, including scene queries, Python/MEL execution, viewport screenshots, tool invocation, and customizable body rigging.
      MIT
    • A
      license
      Not graded
      quality
      Not graded
      maintenance
      Enables 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

    TDQS

    B3.4/5.0

    Scored across 25 tools

    Disambiguation3/5

    The toolset has several scene-analysis operations that overlap conceptually: scene_snapshot, scene_inspect, scene_nodes, scene_describe, scene_validate, scene_assert, scene_review, scene_plan, and scene_aesthetics all inspect or evaluate the scene. Descriptions explicitly draw boundaries and use cases, which helps, but an agent still has many plausible choices for similar-sounding 'check/analyze scene' tasks.

    Naming Consistency4/5

    Most names follow a predictable snake_case domain_action or action_noun pattern, such as scene_inspect, camera_create, asset_import, and list_sessions. Minor deviations like maya_setup_guide and scene_snapshot are still readable, but the set is not perfectly uniform in verb/noun ordering.

    Tool Count3/5

    With 25 tools, the server sits at the heavy end of the acceptable range for a broad Maya integration. The breadth across scene editing, analysis, checkpoints, cameras, assets, rendering, and sessions justifies many tools, but several scene-analysis tools could likely be consolidated into fewer higher-level operations.

    Completeness4/5

    The surface covers core Maya workflows well: scene inspection/validation, checkpoints and rollback, camera creation, asset search/import, export, rendering previews, and session management. Explicit gaps like object deletion or scene open/save are largely workable through execute_code, so the toolset is broadly complete with minor rough edges.

    Maintenance

    ActivityMaintained
    ResponsivenessWithin a week