Skip to main content
Glama
Sign In
tech-lead-bunny

agenteyes-mcp

by tech-lead-bunny
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to agenteyes-mcp

No user-submitted related servers found.

    Related Servers

    • webshot-mcp

      Brandon-35
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables agents to take screenshots and extract text from web pages using a persistent Chrome browser via CDP, with built-in SSRF protection.
      5 npm
      MIT
    • JsonLink MCP Server by mauriblint

      JsonLink MCP Serverofficial

      mauriblint
      A
      license
      A
      quality
      C
      maintenance
      Enables AI agents to read any web page as clean Markdown, pull title/description/preview metadata, capture desktop, mobile, or full-page screenshots, and list every link or image on a URL. JavaScript-heavy pages are rendered in a real browser and blocked requests retried through a proxy, so agents can reach content they'd otherwise miss.
      5
      58 npm
      MIT

    • getsnap-mcp

      rokas-kve
      A
      license
      A
      quality
      B
      maintenance
      Enables Claude and other agents to capture web page screenshots and PDFs, compare two pages with a visual diff, and run WCAG accessibility audits. Captured images are returned inline so a model can inspect the page it just requested within a single turn.
      5
      975 npm
      MIT

    • rasterly-mcp

      rasterly-dev
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to read, screenshot, or convert web pages to PDF using a real headless browser, turning any URL into clean Markdown, a visual image, or a print-ready document.
      82 npm
      MIT
    Deploy Server
    Let your AI agent see the webWeb-to-screenshot MCP for Claude, Cursor and Codex. No cookie banners. Free to start.snap-render.comAd

    TDQS

    B3.4/5.0

    Scored across 2 tools

    Disambiguation4/5

    The two tools are mostly distinct: screenshot_url includes screenshots, while get_page_text does not. However, both return accessibility snapshots and visible text, creating some overlap that could lead to arbitrary selection when only text/snapshot is needed.

    Naming Consistency3/5

    Both names use snake_case, but verb patterns are inconsistent: 'screenshot' acts as a verb/noun, while 'get_page_text' uses the verb 'get'. The mix is readable but not a predictable pattern.

    Tool Count3/5

    Two tools is thin for a web content extraction service. While each tool has a role, the surface feels minimal and could benefit from additional focused tools (e.g., raw HTML, links).

    Completeness3/5

    Core capabilities (screenshot and text/snapshot) are covered, but notable gaps exist: no way to retrieve raw HTML, page links, or interact with the page. Agents may hit dead ends for structured data extraction.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources