Skip to main content
Glama
zhiqi-li

browser-mcp-cdp

by zhiqi-li
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to browser-mcp-cdp

No user-submitted related servers found.

    Related Servers

    • Antigravity Browser Operator

      hashan-lakshitha
      A
      license
      A
      quality
      A
      maintenance
      Enables AI agents to drive the user's already-running Google Chrome through a WebSocket bridge, listing and switching tabs, navigating, clicking, typing, scrolling, extracting DOM, taking screenshots, and evaluating JavaScript. It works without restarting Chrome and preserves all existing logins, cookies, and 2FA sessions.
      11
      MIT

    • Browser MCP

      Agent360dk
      A
      license
      A
      quality
      A
      maintenance
      Enables AI agents to drive your real, logged-in Chrome browser with existing sessions and cookies, bypassing CAPTCHA and anti-bot measures, with support for multi-session and human-in-the-loop workflows.
      40
      46
      MIT

    • chrome-agent-mcp

      otaviosenne
      A
      license
      B
      quality
      D
      maintenance
      Enables AI agents to fully control Google Chrome: navigate, click, fill forms, inspect DevTools, and manage tabs with parallel execution and session isolation.
      24
      7 npm
      MIT

    • Fast Browser MCP

      kqlio67
      A
      license
      C
      quality
      B
      maintenance
      Enables AI agents and developers to automate real Chrome/Chromium browsers through the Chrome DevTools Protocol, with token-efficient snapshots, multi-action batching, shadow DOM traversal, system-page control, extension management, and network/WebSocket inspection.
      64
      MIT
    Deploy Server
    Give agents eyes on the webHosted screenshot MCP. Send a URL, get a pixel-perfect image. $0.002 per grab. Works with Claude, Cursor, and Codex.grabbit.liveAd

    TDQS

    A3.7/5.0

    Scored across 13 tools

    Disambiguation5/5

    Each tool targets a distinct action (navigate, click, fill, etc.) with clear boundaries. No two tools do the same thing; even click variants differ by selector vs coordinates.

    Naming Consistency4/5

    All tools use the 'browser_' prefix with a consistent verb_noun pattern (e.g., get_url, click_at). The only outlier is 'browser_tabs' which uses a noun instead of a verb, but it's still clear.

    Tool Count5/5

    13 tools is well-scoped for browser automation, covering navigation, interaction, content extraction, scrolling, and tab management without being overwhelming.

    Completeness4/5

    Covers most core browser operations (navigate, click, fill, read, screenshot, JS eval). Minor gaps like back/reload or cookie handling exist but are not critical for typical use cases.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources