godot-ui-feedback-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GODOT_BIN | No | The path to the Godot executable. Defaults to 'godot' if not set. | godot |
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 |
|---|---|
| capture_godot_ui_referenceC | Capture a real Godot UI screenshot and node metadata from a scene. |
| generate_godot_ui_proxyC | Deprecated alias for capture_godot_ui_reference. |
| parse_browser_feedbackC | Parse Codex browser comments into existing-page or new-page design feedback records. |
| suggest_godot_scenesC | Suggest Godot scenes for a screenshot or text description. |
| collect_godot_ui_contextC | Collect bounded static Godot UI scene, theme, font, image, layout, and style context for existing-page style support and new-page design. Use complete capture_godot_ui_reference screenshots as the reliable visual basis. |
| ensure_exporter_installedC | Install the managed Godot capture exporter scripts into the target project. |
| uninstall_exporterC | Remove managed Godot capture exporter scripts from the target project. |
| describe_workflowA | Describe the screenshot-to-proxy-to-feedback workflow. |
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 8 tools
Each tool has a distinct purpose: capture screenshots, collect context, install/uninstall exporter, parse feedback, suggest scenes, and describe workflow. The deprecated alias is clearly marked, so no confusion.
All tools use snake_case and mostly follow verb_noun pattern. The deprecated 'generate_godot_ui_proxy' is a minor inconsistency but it's clearly an alias.
With 8 tools, the set is well-scoped for a UI feedback MCP. It covers capture, context, installation, feedback parsing, and scene suggestion without being bloated.
The tool surface covers core workflows (capture, context, feedback parsing) but lacks tools for managing feedback records (e.g., list, update, delete), which is a notable gap.