Skip to main content
Glama
Sign In
godotlens-mcp

godotlens-mcp

by pzalutski-pixel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to godotlens-mcp

No user-submitted related servers found.

    Related Servers

    • Godette

      woohq
      A
      license
      B
      quality
      D
      maintenance
      An MCP server for Godot game development that provides 45 tools for reading, analyzing, and editing projects. It enables users to manage scene trees, navigate GDScript symbols, and interact with the Godot runtime for debugging and state capture.
      52
      MIT

    • godot-correctness-mcp

      TMHSDigital
      A
      license
      Not graded
      quality
      C
      maintenance
      Offline static correctness MCP server for Godot 4.x GDScript projects that lints code, looks up API symbols, and validates scenes/resources, all without a running editor.
      6 npm
      Creative Commons Attribution Non Commercial No Derivatives 4.0 International

    • Minimal Godot MCP

      ryanmazzolini
      A
      license
      A
      quality
      B
      maintenance
      Provides instant GDScript syntax validation and diagnostics by bridging Godot's native Language Server Protocol to MCP clients. Enables real-time syntax checking in AI assistants without requiring custom plugins or context switching to the Godot editor.
      4
      327 npm
      47
      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 49 tools

    Disambiguation3/5

    Two large families overlap heavily: debug_run/debug_output/debug_pause/debug_step_over/debug_inspect/debug_evaluate/debug_terminate mirror runtime_run/runtime_output/runtime_pause/runtime_step/runtime_inspect/runtime_eval/runtime_stop, and gdscript_references vs gdscript_references_in_file vs gdscript_references_batch, or gdscript_sync_file(s) vs gdscript_diagnostics, blur together. The descriptions do carefully explain the distinction (editor run slot vs separate process, breakpoint vs live, single vs batch), so an attentive agent can choose correctly, but the boundaries are not self-evident from names alone.

    Naming Consistency4/5

    Names use a predictable snake_case namespace_verb/noun pattern with clean subsystem prefixes (gdscript_, debug_, runtime_, project_, scene_), and plural suffixes cleanly mark batch variants. Minor deviation: within families the second token mixes verbs and nouns (gdscript_complete vs gdscript_status vs gdscript_find), but this stays readable and consistent overall.

    Tool Count2/5

    At 49 tools this is far past the comfortable range, and much of the bulk comes from parallel variants rather than distinct capabilities (three _batch wrappers, _sync_file vs _sync_files, references vs references_in_file, two near-identical run/inspect/output stacks). The breadth of the domain (LSP, debug adapter, standalone runtime, scene, project) explains some of it, but the surface is heavy enough that tool selection becomes a real burden.

    Completeness4/5

    Coverage is unusually strong end to end: navigation, hover, signature help, rename, validation-without-write, diagnostics, engine API lookup, project/scene validation, and both breakpoint debugging and live runtime introspection. Minor gaps remain, such as no workspace-wide symbol search and no hot-reload path for edited .tscn files or new assets (runtime_reload is GDScript-only), but these are workaround-able.

    Maintenance

    ActivityNo data
    ResponsivenessSyncing

    Resources