Skip to main content
Glama
sterion66

io.github.sterion66/godot

by sterion66

Related Servers

Alternatives to io.github.sterion66/godot

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      D
      maintenance
      Enables AI agents to create, edit, and run Godot 4.5+ games by providing tools for project scaffolding, scene manipulation, and engine interaction. It supports full game development workflows including node editing, script attachment, and project execution with debugging capabilities.
      24
      5
      MIT
    • A
      license
      C
      quality
      C
      maintenance
      Enables AI agents to interact with the Godot game engine, including project inspection, scene/script parsing, headless exports, runtime control with live scene-tree inspection and evaluation, and API documentation search.
      100
      467 npm
      4
      MIT
    • A
      license
      A
      quality
      A
      maintenance
      Enables AI agents to read and edit Godot 4.x scenes and resources, introspect the class API, run the game in a managed headless process with frame stepping, input injection and screenshots, validate scripts, and diagnose code via a built-in GDScript LSP plus a bridge to an already open editor.
      23
      MIT
    • A
      license
      C
      quality
      D
      maintenance
      Enables AI assistants to interact with and manipulate Godot game engine projects, including creating projects, launching editor, managing scenes and nodes.
      12
      467 npm
      1
      MIT

    TDQS

    B3.1/5.0

    Scored across 40 tools

    Disambiguation2/5

    Many tools overlap in purpose, especially the retrieval/listing family: godot_get_project_files, godot_watch_files, godot_find_by_pattern, godot_find_assets, and the list_scenes/list_scripts/list_resources trio all inventory project files in similar ways. godot_create_code_template vs godot_create_script and godot_edit_file vs godot_write_file also have unclear boundaries, making tool selection ambiguous.

    Naming Consistency5/5

    All tool names follow the same godot_verb_noun pattern with snake_case throughout, making the naming convention highly predictable. Minor semantic issues like godot_watch_files not actually watching files do not break the syntactic consistency.

    Tool Count2/5

    40 tools is well beyond the 25-tool threshold for a cohesive set, and the high count is driven partly by redundant file-discovery operations. While Godot integration is a broad domain, this surface feels heavier than necessary and could be consolidated.

    Completeness3/5

    The server covers creation, reading, editing, validation, running, asset downloads, and plugin/autoload inspection, so core Godot workflows are mostly represented. However, there are no delete, rename, export, or project-settings update tools, and the read-only project settings plus overlapping file operations leave notable lifecycle gaps.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues