Skip to main content
Glama
woohq

Godette

by woohq
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to Godette

No user-submitted related servers found.

    Related Servers

    • Godot MCP

      jamesdowzard
      A
      license
      B
      quality
      C
      maintenance
      An MCP server that enables AI agents to interact with the Godot game engine by launching the editor, running projects, capturing debug output, and managing scenes and resources. It provides tools for project analysis, scene creation, and execution control to help agents understand and debug Godot projects in real-time.
      14
      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

    • Godot MCP Pro

      youichi-uda
      F
      license
      Not graded
      quality
      A
      maintenance
      Premium MCP server for Godot game engine with 84 tools across 14 categories. Scene editing, scripting, animation, tilemap, shader, input simulation, runtime debugging, profiling, theme/UI, batch operations, and export support.
      602
      -
    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

    B3.4/5.0

    Scored across 52 tools

    Disambiguation4/5

    Most tools are clearly distinct by their target (scenes, nodes, resources, project config, runtime, files). However, there is some overlap between find_resource and find_resources_of_type (explicitly an alias), and read_file vs list_dir vs find_file could be confused for file browsing. Overall, the domains are well-separated.

    Naming Consistency4/5

    The naming convention is mostly verb_noun (e.g., get_scene_tree, find_node, create_scene, modify_node_property) with a few exceptions like onboarding, rescaffold_plugin (verb alone), and switch_mode. The verb choice is mostly consistent (get/find/create/insert/delete/modify) but there are mixed verb styles (add_node vs create_scene, remove_node vs delete_lines).

    Tool Count3/5

    With 52 tools, the server is on the heavy side, even for a comprehensive Godot IDE integration. While many tools are domain-appropriate screens, resources, file editing, runtime—the count is excessive and may overwhelm an agent. It could be trimmed to ~30-40 by consolidating overlapping operations (e.g., find_resource/find_resources_of_type, insert_after_symbol/insert_before_symbol).

    Completeness5/5

    The tool surface is impressively complete for the stated purpose: it covers static scene/resource inspection, file manipulation, symbol-level code editing, project configuration, and runtime control/debugging (run, stop, state capture, screenshot, console). It even includes signal tracing and mode switching. No major dead ends or missing lifecycle operations are apparent.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources