Skip to main content
Glama
Sign In
layerdock-mcp

layerdock-mcp

Official
by LayerDock
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to layerdock-mcp

No user-submitted related servers found.

    Related Servers

    • feedbug-mcp

      joffreyBerrier
      A
      license
      A
      quality
      C
      maintenance
      Read visual bug reports from Feedbug in your AI coding agent: screenshot, console logs, failed network requests, session replay and the DOM context of the element the tester clicked. Trace the bug to its source file, comment and resolve without leaving the editor.
      7
      7 npm
      MIT

    • loopback

      joshidikshant
      A
      license
      A
      quality
      C
      maintenance
      Interactive feedback layer that lets users pin comments on live web apps with auto-captured context (failing requests, console, AI metadata), and coding agents fix issues via MCP, turning pins green upon verification.
      10
      84 npm
      MIT

    • unide

      trxphxle
      A
      license
      Not graded
      quality
      B
      maintenance
      Lets users pin elements on live web pages, describe desired changes, and send those annotations to coding agents. Agents receive the selected targets, notes, screenshots, and source or style context needed to implement the edits.
      MIT

    • Browser Feedback MCP

      itk-dev
      A
      license
      A
      quality
      C
      maintenance
      Enables visual browser feedback collection directly into Claude Code. Users can point at elements in their browser and send annotated feedback that Claude can act on immediately.
      12
      1
      MIT
    Deploy Server
    Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

    TDQS

    A4.4/5.0

    Scored across 5 tools

    Disambiguation5/5

    Each tool targets a clearly distinct operation: list_feedback retrieves pins across docks, list_docks retrieves sites, get_feedback retrieves one detailed brief, update_feedback_status changes workflow state, and reply_to_feedback posts a message. Descriptions explicitly clarify boundaries (e.g., lean summary vs. full brief, server-side stamping) leaving no realistic misselection.

    Naming Consistency5/5

    All names use snake_case with a consistent verb_noun pattern: list_feedback, list_docks, get_feedback, update_feedback_status, reply_to_feedback. The minor prep in reply_to_feedback does not break the overall predictable convention.

    Tool Count5/5

    Five tools are well-scoped for an agent that fixes feedback pins: see open work, find a dock, get the fix brief, update status, and reply. No tool feels redundant or missing for the stated purpose.

    Completeness5/5

    The surface covers the full agent workflow: discover open pins (list_feedback), resolve dock context (list_docks), retrieve all fix details (get_feedback), change lifecycle state (update_feedback_status), and communicate with the reviewer (reply_to_feedback). No obvious dead ends for the coding-agent use case.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues

    Resources