Skip to main content
Glama

Related Servers

Alternatives to annotation-overlay-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables visual annotation on web pages for Claude Code, allowing element selection, comment addition, screenshot capture, and structured UI feedback for code fixes via an MCP server.
      MIT
    • F
      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
      -
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables drawing annotations directly on local web pages and sending screenshots, DOM data, and annotation context to your IDE agent for precise code edits.
      31 npm
      3
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables users to capture any screen or URL, box the region they mean, attach notes, and deliver that annotated feedback—including cropped images, numbered boxes, and the underlying DOM elements or component names—directly to an AI coding agent over MCP. It also lets agents open the annotator, capture a URL, and wait for or retrieve feedback bundles from earlier sessions.
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables users to draw marks and leave numbered notes on a running localhost page in a Chrome window, then send the batch into the active Claude Code session with each note's element, React component, source line, and screenshot. Progress and per-note results stream back onto the page, and the marks persist across navigation, all locally with no cloud.
      1
      MIT

    TDQS

    A4/5.0

    Scored across 2 tools

    Disambiguation5/5

    read_annotations and clear_annotations have completely distinct purposes: one retrieves feedback, the other removes it. There is no overlap or ambiguity between the two operations.

    Naming Consistency5/5

    Both tools follow the same verb_noun pattern (read_annotations, clear_annotations), with clear and predictable naming. The convention is consistent across the entire server.

    Tool Count3/5

    With only 2 tools, the server feels minimal. While the read/clear pair covers the core workflow, the count is borderline for a standalone MCP server.

    Completeness4/5

    The server covers the essential operations for consuming and resetting annotation feedback. There is no per-annotation update or delete, but the batch read/clear model fits the described usage pattern well.

    Maintenance

    ActivitySlowing
    ResponsivenessUnresponsive