godot-devtool
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GODOT_PATH | No | Path to the Godot executable (optional if 'godot' is on PATH). | |
| GODOT_DEVTOOL_WS_PORT | No | WebSocket port for the bridge (default 8766). | 8766 |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_capabilitiesA | Return a lightweight godot-devtool tool catalog by default, with optional filtered input schemas by route group, transport, risk level, tool name, or query |
| get_godot_versionA | Get the installed Godot version |
| list_projectsA | List Godot projects in a directory |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 3 tools
Each tool has a distinct purpose: returning the tool catalog, retrieving the Godot version, and listing projects. There is no overlap.
All tools follow a consistent verb_noun pattern with underscores (get_capabilities, get_godot_version, list_projects).
With only 3 tools, the set is small but not unreasonable for a focused development tool. It could be more comprehensive but feels appropriate for a minimal server.
The tools cover basic information retrieval (version, project listing) but lack actions like running or exporting projects. Notable gaps exist for a development tool server.