Skip to main content
Glama
Sign In
Beckett — MCP for Godot

Beckett — MCP for Godot

by beckettlab
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

Related Servers

Alternatives to Beckett — MCP for Godot

No user-submitted related servers found.

    Related Servers

    • godot-forge

      gregario
      A
      license
      A
      quality
      C
      maintenance
      Godot 4 MCP server with: Test running (GUT/GdUnit4) with structured pass/fail results API docs search with 30+ Godot 3→4 migration mappings Script analysis detecting 10 common GDScript pitfalls Scene/resource file parsing with antipattern detection Viewport screenshot capture LSP diagnostics from Godot's language server TypeScript, cross-platform (macOS/Windows/Linux), published on npm
      8
      74 npm
      9
      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.
      49
      MIT

    • 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.
      166 npm
      2
      AGPL 3.0

    • Godot MCP

      k0nkupa
      A
      license
      Not graded
      quality
      C
      maintenance
      A security-first MCP server and Godot editor addon enabling AI agents to observe and control Godot games through bounded, permission-gated tools for debugging, input automation, and project editing.
      MIT
    Deploy Server
    Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

    TDQS

    A3.6/5.0

    Scored across 56 tools

    Disambiguation3/5

    Several tool pairs overlap: read_file/read_script, write_file/write_script, logs_read/game_logs, get_scene_tree/get_remote_tree, and describe_class/describe_object. Descriptions clarify editor-vs-runtime and text-vs-GDScript context, so an agent can often choose correctly, but the redundancy leaves real misselection risk.

    Naming Consistency4/5

    Names are predominantly snake_case and action-oriented (find_nodes, create_node, set_property), with minor exceptions like logs_read, script_patch, game_logs, ui_snapshot, and single-word doctor/screenshot/help. The pattern is readable and mostly predictable rather than chaotic.

    Tool Count1/5

    At 56 tools the surface is far beyond the 3-15 sweet spot and past the 50+ extreme threshold for agent tool lists. The broad Godot domain explains some breadth, but batch_execute, help, doctor, and effort tiers largely compensate for an over-scoped surface.

    Completeness4/5

    The set covers scene CRUD, scripts, files, signals, resources, project settings, runtime inspection, profiling, screenshots/UI, templates, C# builds, and diagnostics. Gaps remain around runtime mutation (no runtime_set_property/runtime_call in this list), file/resource deletion, and input interaction, but most core workflows are covered.

    Maintenance

    ActivityNo data
    ResponsivenessSyncing

    Resources