Skip to main content
Glama
JaDi03

Browser Intelligence MCP

by JaDi03
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to Browser Intelligence MCP

No user-submitted related servers found.

    Related Servers

    • Browser-Debugger

      Selvadinesh-giga
      F
      license
      Not graded
      quality
      D
      maintenance
      Enables AI agents to automate and debug real Chromium browsers with capabilities like screenshots, video recording, performance analysis, visual regression testing, and OCR text extraction.
      13
      -

    • Chrome DevTools MCP

      az9713
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI assistants to control and inspect a live Chrome browser for automated web debugging, performance analysis, and Lighthouse audits. It allows agents to capture screenshots, monitor network requests, and measure Core Web Vitals using plain-English prompts.
      1,516,489 npm
      Apache 2.0

    • 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

    • agent-browser

      gopendrasharma89-tech
      A
      license
      Not graded
      quality
      C
      maintenance
      Provides a headless Chromium browser through MCP, enabling AI agents to browse JavaScript-rendered pages, search the web, capture screenshots, extract tables and data, and run stateful multi-step interactions like clicking, typing, and form submission.
      1,070,795 npm
      1
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A4/5.0

    Scored across 3 tools

    Disambiguation5/5

    Each tool has a clear, non-overlapping purpose: take_screenshot captures visual state, scrape_page extracts content and links, and run_visual_test performs assertion-based checks. No ambiguity in usage.

    Naming Consistency5/5

    All three tools follow a consistent verb_noun pattern (take_screenshot, scrape_page, run_visual_test) with clear, descriptive verbs. Naming is uniform and predictable.

    Tool Count5/5

    With 3 tools, the set is minimal but well-scoped for a focused browser intelligence server. Each tool serves a distinct core function (capturing, extracting, testing) and earns its place without unnecessary bloat.

    Completeness4/5

    The surface covers the primary browser intelligence workflows (screenshot, scrape, and visual checks). Minor gaps exist—such as no support for full HTML extraction or waiting for dynamic content—but for the stated purpose, the coverage is solid and workable.

    Maintenance

    ActivityMaintained
    ResponsivenessSyncing

    Resources