Skip to main content
Glama
sachin-sbu

agentic3d-mcp

by sachin-sbu
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

Related Servers

Alternatives to agentic3d-mcp

No user-submitted related servers found.

    Related Servers

    • codex3d

      kytianhong
      A
      license
      B
      quality
      A
      maintenance
      Enables natural language creation and refinement of Blender scenes through structured MCP tools, with persistent object identity, visual validation, and reversible edits.
      23
      MIT

    • blender-mcp-synthgen

      scott-createplay
      A
      license
      Not graded
      quality
      B
      maintenance
      MCP server for procedural 3D synthetic-data generation in Blender, providing 33 grounded tools for node graph authoring, scene-graph traversal, and parameter sweeps with schema verification.
      MIT

    • chisel

      EYamanS
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI agents to construct, edit, and export 3D models using geometric primitives and boolean operations, with multi-view rendering to facilitate spatial reasoning.
      7
      MIT

    • Hayba

      zajalist
      A
      license
      Not graded
      quality
      C
      maintenance
      An MCP server enabling AI agents to author Unreal Engine 5 scenes directly, with tools for spawning actors, building PCG graphs, validating physics, generating terrain, and more through a single MCP connection.
      13
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.9/5.0

    Scored across 13 tools

    Disambiguation5/5

    Each tool maps to a distinct action in the 3D scene editing workflow: loading, segmenting, querying, adding/removing, transforming, undo, rendering, saving, and high-level editing. Even load_scene and segment_scene are clearly separated by their roles despite both returning scene info. No two tools appear to perform the same operation.

    Naming Consistency5/5

    Tool names consistently follow a snake_case verb_noun pattern (load_scene, add_object, render_scene). Minor deviations like get_scene_info and edit_with_agent are still verb-first and fit the broader convention. The naming is predictable and easy to scan.

    Tool Count5/5

    13 tools is well-scoped for a 3D scene composition server. Each tool covers a core lifecycle or editing operation without unnecessary redundancy. The count feels appropriate for the domain.

    Completeness5/5

    The server provides full coverage of the scene editing workflow: load, segment, inspect, add/remove, transform, replace, undo, render, and save. Object manipulation covers the essential operations agents need, and edit_with_agent offers a high-level fallback for complex changes. No obvious dead ends or critical missing operations.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources