Skip to main content
Glama
nickschuetz

o3de-mcp

by nickschuetz
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to o3de-mcp

No user-submitted related servers found.

    Related Servers

    • Game Studio MCP

      pkurri-gamezone
      F
      license
      Not graded
      quality
      D
      maintenance
      This server enables AI assistants to directly control the Unity Editor via MCP, supporting scene manipulation, script editing, level generation, monetization management, build pipelines, and more—all with zero external dependencies.
      -

    • unreal-engine-mcp

      harn3ss
      A
      license
      B
      quality
      C
      maintenance
      An MCP server that gives AI agents broad control over Unreal Engine 5.7, enabling actor/asset/level management, Blueprint and material creation, screenshots, automation, and arbitrary editor Python execution.
      35
      MIT

    • soft-ue-cli

      softdaddy-o
      A
      license
      Not graded
      quality
      A
      maintenance
      MCP server for controlling Unreal Engine 5 from AI agents, providing 120+ commands for spawning actors, editing Blueprints, managing assets, and more via CLI or MCP.
      16 PyPI
      211
      MIT

    • mcp-bridge

      firekula
      A
      license
      Not graded
      quality
      B
      maintenance
      MCP server for Cocos Creator that enables AI tools to automate scene editing, resource management, and project operations via HTTP and stdio interfaces.
      12 npm
      226
      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

    B3.2/5.0

    Scored across 66 tools

    Disambiguation3/5

    The toolset covers many distinct areas, but several near-overlapping pairs exist: build_project/start_build, run_editor_python/exec_in_session, get_bus_schema/get_bus_schema_live, and get_scene_snapshot/get_entity_tree/list_entities. Descriptions help clarify the differences, but the sheer number of similarly-purposed tools makes misselection likely.

    Naming Consistency4/5

    The dominant verb_noun snake_case pattern is consistent and predictable across most tools (list_*, create_*, get_*, set_*, enable_*, disable_*). Minor outliers like undo, redo, exec_in_session, and wait_for_assets break the pattern slightly without causing major confusion.

    Tool Count1/5

    66 tools is far beyond what is typically appropriate for a coherent MCP surface, even for a complex engine. Many tools could be consolidated, such as blocking vs background builds, one-off vs persistent Python execution, and multiple scene/entity listing variants, making the set heavy and difficult for an agent to navigate.

    Completeness4/5

    The surface is remarkably comprehensive for the O3DE domain: engine registration, project and gem management, builds, asset processing, logs, levels, entities, components, prefabs, viewport control, Python sessions, bus schemas, and console commands are all covered. Minor lifecycle gaps exist, such as no delete project/gem/level or entity rename, but core workflows do not hit dead ends.

    Maintenance

    ActivityMaintained
    ResponsivenessSlow

    Resources