Skip to main content
Glama

Related Servers

Alternatives to maya-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI assistants like Claude Desktop to control Autodesk Maya via natural language through the Model Context Protocol.
      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
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables Claude and other MCP clients to control Autodesk Maya 2024 through 244 typed tools, including modeling, rigging, previs, FX, Arnold rendering, asset libraries, AI 3D generation, and a real-time change stream for Unreal.
      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
      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.
      14 npm
      8
      MIT
    • 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
      -

    TDQS

    B3.4/5.0

    Scored across 17 tools

    Disambiguation3/5

    Most tools target distinct operations, and the descriptions go out of their way to distinguish rendering paths (maya_viewport_capture vs maya_session render_still vs review_turntable) and import vs reference. However, maya_session is a god-tool bundling 13 actions (render, publish, turntable, delete, execute_python) that overlap conceptually with dedicated tools like maya_import_file and maya_viewport_capture, making boundaries hard to reason about.

    Naming Consistency4/5

    The core tools use a predictable maya_verb_noun snake_case pattern (maya_create_primitive, maya_assign_material, maya_transform). A few deviate with a noun-verb or no-prefix form (search_maya_docs, learn_pattern, session_stats, reset_session_stats), but all remain snake_case and readable.

    Tool Count3/5

    17 top-level tools is slightly above the comfortable range, but the real issue is that three of them (maya_session, maya_vision3d, maya_worldlabs) are multi-action mega-tools hiding ~27 additional actions, making the effective surface far larger than the count suggests.

    Completeness4/5

    Coverage of the DCC automation domain is broad: primitives, transforms, materials, lights, cameras, mesh ops, keyframes, import, references, rendering, publishing, docs search, and learning. Minor gaps exist (no standalone delete/update for objects beyond transform, no rigging/joint tools), but they are workable via maya_session(execute_python).

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues