Skip to main content
Glama
adityaairlangga12

lentera-godot-mcp

by adityaairlangga12
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to lentera-godot-mcp

No user-submitted related servers found.

    Related Servers

    • godot-mcp

      youssof20
      A
      license
      Not graded
      quality
      B
      maintenance
      A TypeScript MCP server bridging MCP clients to Godot 4 editor, enabling scene, node, script editing and more via WebSocket.
      159 npm
      MIT

    • Beckett — MCP for Godot

      beckettlab
      A
      license
      A
      quality
      A
      maintenance
      Zero-sidecar MCP server embedded directly in the Godot 4 editor as a GDScript EditorPlugin — no Node or Python sidecar. Reflection-driven tools over any engine class, validate-before-write GDScript, scene/script/resource authoring, and a runtime play-test loop (play, screenshot, input, assert).
      55
      23
      MIT

    • Funplay MCP for Godot

      FunplayAI
      A
      license
      Not graded
      quality
      A
      maintenance
      The most advanced MCP server for Godot Editor that lets AI assistants operate directly inside your running Godot project for scene creation, script generation, UI authoring, and more.
      39
      MIT

    • Gear

      wvfp
      A
      license
      A
      quality
      D
      maintenance
      An MCP server that enables AI assistants to directly run, inspect, modify, and debug Godot game development projects through 110+ tools covering scenes, scripts, resources, runtime debugging, and asset management.
      33
      21 npm
      2
      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

    C2.7/5.0

    Scored across 63 tools

    Disambiguation4/5

    Most tools have clearly distinct purposes, but get_node_signals and list_signals both deal with node signals and could be confused. Some clustering around physics layers and signal handling creates minor overlap, though descriptions mostly clarify.

    Naming Consistency5/5

    All tool names follow a consistent snake_case verb_noun pattern, such as launch_editor, create_scene, add_node, set_keyframe, and validate_collision_setup. The naming convention is uniformly applied across the entire set.

    Tool Count1/5

    With 63 tools, the server is far beyond what is typical for an MCP server, even for a comprehensive Godot integration. The sheer number is overwhelming and exceeds the calibration threshold of 50+ for extreme mismatch.

    Completeness4/5

    The toolset covers a broad range of Godot operations: editor lifecycle, scene editing, nodes, scripts, assets, animations, tilemaps, signals, autoloads, project settings, running/testing, and physics layers. Minor gaps exist, such as lack of delete/update operations for animations and some overlap in physics layer utilities, but the core workflows are well-covered.

    Maintenance

    ActivityMaintained
    ResponsivenessSyncing

    Resources