Skip to main content
Glama
deng1986

chrome-bridge-mcp

by deng1986

Related Servers

Alternatives to chrome-bridge-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      A
      maintenance
      Lets AI coding tools drive the real, already-logged-in Chrome browser over local stdio—snapshotting and reading pages, clicking, typing, managing tabs, capturing screenshots, and inspecting network, console, storage, and cookies—without opening a remote-debugging port. It installs as a Chrome extension plus native-messaging bridge, so agents work in the user's authenticated sessions while passing bot detection.
      1 npm
      ISC
    • A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI coding tools to drive the real Chrome browser you already have open — navigating, clicking, typing, reading pages, taking screenshots, and inspecting cookies, network traffic, and storage from within your existing logged-in sessions. All communication stays local to your machine.
      1 npm
      ISC
    • A
      license
      Not graded
      quality
      A
      maintenance
      Lets AI coding tools drive the user's already-signed-in Chrome browser — reading and snapshotting pages, clicking, typing, uploading files, screenshotting, and inspecting tabs, cookies, console, and network traffic. It works through a local Chrome extension bridge, so no remote debugging port is opened and the real, authenticated browser session is used.
      1 npm
      ISC
    • A
      license
      Not graded
      quality
      A
      maintenance
      Bridges AI agents to a real browser using a persistent daemon and Chrome extension for driving actual login sessions, cookies, and tabs.
      MIT

    TDQS

    B3.1/5.0

    Scored across 22 tools

    Disambiguation3/5

    There are multiple tools for interacting with Google AI (e.g., ask_ai_page, google_ai_ask, open_google_ai) that could confuse an agent about which to use. Also, detect_human_intervention and wait_for_user serve similar purposes. However, most tools for general browser control are distinct.

    Naming Consistency2/5

    Most tools follow a verb_noun pattern (e.g., click_selector, open_url), but several start with the noun (e.g., google_ai_ask, google_search) breaking consistency. Additionally, names like search_google_and_extract are overly verbose.

    Tool Count4/5

    With 22 tools, the server covers both general browser automation and Google AI interactions. This is slightly high but still reasonable; each tool has a clear purpose, though some duplication could be consolidated.

    Completeness3/5

    The general browser tools cover core actions like open, click, fill, and get page info. Google AI session management is thorough. However, missing tools for closing tabs, keyboard input, or screenshots create minor gaps.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues