GameDevBench MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GODOT_EXEC_PATH | No | Path to the Godot 4.x executable. Required if 'godot' is not available in your system PATH. | |
| GODOT_SCREENSHOT_DISPLAY | Yes | The display number to use for screen capture. This is required for the MCP server screenshot functionality on macOS. |
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 |
|---|---|
| godot-screenshotC | Launch Godot editor on specified display and take a screenshot |
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 1 tool
With only one tool, there is no possibility of ambiguity or overlap between tools. The tool's purpose is clearly defined and distinct by default.
A single tool inherently has perfect naming consistency, as there are no other tools to compare it against. The name 'godot-screenshot' follows a clear noun-verb pattern.
A single tool for a server named 'GameDevBench MCP' suggests an extremely limited scope that does not align with the implied breadth of game development tasks. This feels thin and incomplete for the domain.
The tool set is severely incomplete for game development, covering only a niche screenshot function. There are obvious gaps in core operations like asset management, testing, or build processes, making it inadequate for the stated purpose.