Skip to main content
Glama
local-chrome-cdp-probe-mcp

local-chrome-cdp-probe-mcp

Related Servers

Alternatives to local-chrome-cdp-probe-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      A
      maintenance
      Enables MCP clients to drive your real Chrome profile through a local, token-protected bridge, so agents can open and navigate tabs, read page snapshots, click, type, scroll, wait, run JavaScript, and take screenshots while keeping your existing logins and extensions. It runs inside the Chrome you already use rather than a separate clean profile.
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables fast browser automation on a real Chrome tab via a local hub, providing MCP tools for clicking, filling, snapshotting, and navigating without launching a full browser instance.
      MIT
    • F
      license
      Not graded
      quality
      A
      maintenance
      Gives AI agents a private, locally-run Chrome-for-Testing browser they drive directly, letting them fetch WAF-protected pages, capture network and screenshot evidence, harvest e-commerce catalogs, and run performance, accessibility, SEO, and cross-engine QA inspections through standard MCP tools. It also provides click-flow smoke tests, visual baselines, page comparison, and diagnostics, all without a cloud relay or the user's personal Chrome profile.
      -
    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables MCP clients to drive a real, logged-in Chrome browser for web automation tasks like navigation, clicking, typing, and screenshotting.
      9 npm
      MIT
    • A
      license
      B
      quality
      C
      maintenance
      Exposes a live Chrome browser to any MCP client through a single local endpoint, enabling real-tab control, DOM interaction, cookies and session use, network/console capture, PDF export, and CDP-powered debugging.
      28
      MIT
    • A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI agents to see and control the user's real Chrome/Brave/Edge profile over MCP, so they can read pages, click, type, take screenshots, audit layouts, debug CSS, and scrape paginated or infinite-scroll data. Because it drives the normal browser via the DevTools protocol with real input events, it works on modern JavaScript apps and on sites where the user is logged in.
      20 npm
      1
      MIT

    TDQS

    A3.9/5.0

    Scored across 2 tools

    Disambiguation5/5

    The two tools have clearly distinct roles: probe_available is a preflight/environment check (node, bundled script, Chrome detection) while probe_page performs the actual measurement/screenshot work. There is no overlap in purpose, so an agent can pick correctly without hesitation.

    Naming Consistency5/5

    Both tools use the same snake_case, 'probe_' prefixed pattern (probe_available, probe_page), which reads as a deliberate, predictable namespace. No mixing of conventions or verb styles.

    Tool Count3/5

    Two tools is on the thin side, though the server's scope (a local Chrome CDP probe) is intentionally narrow. Much of the capability is folded into probe_page's many parameters, so the count is defensible but borderline minimal.

    Completeness4/5

    The surface covers preflight, navigation, viewport emulation, authenticated JSON login, arbitrary in-page measurement, and screenshots, which is solid for the stated purpose. Gaps exist around multi-page/batch probing, wait conditions (network idle, selector waits), and console/error capture, but the free-form measure_js escape hatch lets agents work around most of them.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues