Skip to main content
Glama
jigwright

HullForge MCP Connector

by jigwright
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to HullForge MCP Connector

No user-submitted related servers found.

    Related Servers

    • unreal-mcp-server

      Jeanosasco
      F
      license
      Not graded
      quality
      C
      maintenance
      MCP server that connects Claude to Unreal Engine 5.8 via the official Remote Control API, enabling asset manipulation, actor control, level operations, and AI-powered 3D model generation (via Meshy) through natural language.
      -

    • UnrealMCP

      AvatarGanymede
      A
      license
      Not graded
      quality
      A
      maintenance
      A native MCP server for Unreal Engine 5.7 that lets AI assistants inspect and control an open Unreal Editor through a single 'unreal' tool, supporting Python/console command execution and async tasks.
      2
      MIT

    • 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

    • uefn-mcp

      quangdang46
      F
      license
      Not graded
      quality
      F
      maintenance
      A two-process MCP bridge for Unreal Editor for Fortnite that lets Claude Code, Cursor, and other MCP clients drive a live UEFN editor safely.
      9
      -

    • Unreal-MCP

      IvanMurzak
      A
      license
      Not graded
      quality
      A
      maintenance
      Open-source MCP server connecting AI agents (Claude, Cursor, GitHub Copilot, Gemini, and more) to Unreal Engine 5.7, editor and runtime (C++ plugin + .NET sidecar).
      39
      Apache 2.0
    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.8/5.0

    Scored across 1 tool

    Disambiguation5/5

    With only a single tool, there is no possibility of overlapping purposes or confusion. The tool's purpose is clearly defined as a status check for the HullForge-Unreal connection.

    Naming Consistency5/5

    The single tool name 'hf_bridge_status' follows a consistent snake_case convention and is descriptive of its function. There are no other tools to create inconsistency.

    Tool Count1/5

    The server exposes only one tool for a connector that is expected to provide interaction with a running Unreal editor. The description hints at additional tools appearing dynamically, but the current set is extremely limited, making it a severe mismatch for the server's apparent scope.

    Completeness1/5

    The server's purpose is to bridge HullForge and Unreal Editor, yet the only tool available is a status check. There are no tools to perform any actual actions (e.g., launching assets, executing commands, or modifying editor state), leaving critical gaps that render the surface incomplete.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources