Skip to main content
Glama
jxqxn

godot-ui-feedback-mcp

by jxqxn
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to godot-ui-feedback-mcp

No user-submitted related servers found.

    Related Servers

    • Godot Codex Bridge MCP

      ItsHege
      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

    • godot-mcp

      SrDarkoll
      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.
      194 npm
      3
      MIT

    • godot-mcp

      CyberIce2077
      A
      license
      Not graded
      quality
      C
      maintenance
      Lets AI agents launch a Godot 4 project, then observe and interact with the running game — capturing screenshots, inspecting the live scene tree, pressing Input Map actions, and reading stdout/stderr and script errors.
      194 npm
      MIT

    • godot-loop

      AI-osho
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI agents to verify their own work on real Godot 4 projects: edit scenes and scripts safely, launch the game, send real keyboard/mouse input, wait on conditions, read live runtime state, capture screenshots and errors, and run declarative scenario play-tests that return per-step pass/fail reports with the observed failing value.
      MIT
    Deploy Server
    Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

    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

    Resources