Skip to main content
Glama
Estiwito

Game engine runtime mcp

by Estiwito
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to Game engine runtime mcp

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.
      -

    • ach-mcp

      achieveonepark
      F
      license
      Not graded
      quality
      C
      maintenance
      An in-editor MCP server that exposes Unity convenience tools to AI assistants, allowing them to read console logs, execute menu items, dump scene hierarchies, and take screenshots.
      -

    • HullForge MCP Connector

      jigwright
      A
      license
      A
      quality
      C
      maintenance
      An MCP server that enables Claude to drive a running Unreal Engine 5 editor, managing communication between the editor plugin and the LLM client through stdio transport with session discovery, idempotent operations, and honest failure reporting.
      1
      MIT

    • Godot-MCP

      IvanMurzak
      A
      license
      Not graded
      quality
      A
      maintenance
      Open-source MCP server connecting AI agents (Claude, Cursor, GitHub Copilot, Gemini, and more) to the Godot Editor and runtime (Godot 4.x, C#).
      253
      Apache 2.0

    • godot-mcp

      blentz
      A
      license
      Not graded
      quality
      B
      maintenance
      An MCP server that lets an AI agent work on a Godot 4.x project the way a developer does: read and edit scenes, write scripts, build, test, run, look at the result, and debug what went wrong.
      159 npm
      AGPL 3.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.6/5.0

    Scored across 4 tools

    Disambiguation5/5

    Each tool targets a distinct concern: scene hierarchy inspection, test execution, safe code editing, and log/memory analysis. There is no meaningful overlap or risk of an agent selecting the wrong tool.

    Naming Consistency5/5

    All tool names follow the same verb_noun pattern in lowercase snake_case: inspeccionar, ejecutar, escribir, analyzar. The naming is uniform and predictable.

    Tool Count4/5

    Four tools is a reasonable size for a focused engine-runtime toolbox. Each tool appears to serve a distinct workflow, though the set could be slightly richer for a broad 'runtime' server.

    Completeness3/5

    The set covers scene inspection, test execution, code editing, and log analysis, but lacks direct runtime control and live state mutation features like play/pause, object property changes, or scene manipulation. These gaps limit what an agent can accomplish in an actual running game engine session.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources