Skip to main content
Glama
RBG-WebDesign

MCPBridge Server

Related Servers

Alternatives to MCPBridge Server

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to control and query Unreal Engine 4.27.2 editor through MCP, supporting asset creation, level editing, and project inspection via Python remote execution.
      411 npm
      25
      MIT
    • A
      license
      A
      quality
      A
      maintenance
      Enables AI agents to operate the Unreal Editor via MCP: reading, creating, and editing blueprints at the node level, authoring materials and UMG widgets, auditing projects, and verifying runtime behavior in PIE with read-back checks.
      23
      Apache 2.0
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI coding agents to work inside a live Unreal Editor for Fortnite session: write and compile Verse, place and wire Creative devices, edit Scene Graph entities, manipulate actors and assets, take screenshots, run playtests, and read editor logs via MCP.
      MIT
    • 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
    • A
      license
      Not graded
      quality
      A
      maintenance
      Unreal Engine 5.7 editor plugin that gives AI assistants full read/write access to Blueprints, Materials, Animation, Niagara, Config, and more via MCP. 119 actions across 9 domains, pure C++, embedded Streamable HTTP server.
      319
      MIT

    TDQS

    B3.1/5.0

    Scored across 122 tools

    Disambiguation2/5

    Several tools overlap: blueprint_info, blueprint_inspect, and blueprint_document all inspect Blueprint structure; blueprint_build_from_json and blueprint_build_from_description both build graphs; bridge_clear_log and clear_output_log are exact aliases. While many tools are domain-specific, these overlaps create selection ambiguity.

    Naming Consistency3/5

    Most tools follow a consistent <domain>_<action> pattern (actor_spawn, asset_list, material_create), but outliers like undo, redo, help, test_connection, python_proxy, and ue_logs break the pattern. There are also mixed conventions such as level_actors vs actor_spawn and clear_output_log as a bare verb.

    Tool Count1/5

    With 122 tools, this is an extreme over-scoping for a single server. The calibration guide marks 50+ as extreme, and this is more than double that, making it difficult for an agent to efficiently select the right tool.

    Completeness3/5

    The tool surface is remarkably broad, covering assets, actors, blueprints, materials, viewport, input, AI, data tables, and C++, but it lacks basic delete operations for many asset types (e.g., asset_delete, material_delete, blueprint_delete) and has no rename or list for data tables. It's extensive but not fully comprehensive.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues