Skip to main content
Glama
jxqxn

godot-ui-feedback-mcp

by jxqxn

Related Servers

Alternatives to godot-ui-feedback-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      A
      maintenance
      Enables coding agents to see and act inside a live Godot 4 editor, inspecting scene trees and capturing visual evidence while performing undo-backed, approval-gated edits with runtime verification.
      MIT
    • A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI agents to inspect, author, debug, simulate, and visually verify Godot 4.x projects through standard MCP tools, including scene editing, runtime control, and viewport capture.
      143 npm
      2
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Provides a comprehensive integration between LLMs and the Godot Engine, enabling AI assistants to intelligently manipulate project files, scripts, and the live editor. It supports advanced workflows including version-aware documentation querying, automated E2E game testing, and real-time visual context capture.
      12 npm
      26
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      Connects AI assistants to the live Godot 4 editor so they can build scenes, scripts, resources and animations, run the game, simulate input, capture screenshots and playtest scenarios, and diagnose runtime errors. Every edit flows through undoable changesets that can be diffed, approved, checkpointed or discarded.
      29
      1
      MIT

    TDQS

    B3.1/5.0

    Scored across 8 tools

    Disambiguation5/5

    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.

    Naming Consistency4/5

    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.

    Tool Count5/5

    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.

    Completeness3/5

    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.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues