Skip to main content
Glama
deng1986

chrome-bridge-mcp

by deng1986
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to chrome-bridge-mcp

No user-submitted related servers found.

    Related Servers

    • Konnect

      grandmaster451
      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

    • chrome-devtools-mcp

      zhang77-X
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI coding assistants to control and inspect a live Chrome browser through Chrome DevTools for automation, debugging, and performance analysis.
      3,138,727 npm
      Apache 2.0

    • Chrome MCP Bridge

      Weiktseng
      F
      license
      Not graded
      quality
      D
      maintenance
      AI-driven browser automation for real Chrome with cookies, login sessions, and extensions intact, enabling Claude Code to control a visible Chrome browser via the Chrome DevTools Protocol.
      1
      -

    • Chrome DevTools MCP

      dinesh-nalla-se
      A
      license
      Not graded
      quality
      D
      maintenance
      Lets AI coding assistants control and inspect a live Chrome browser using full Chrome DevTools capabilities for browser automation, debugging, and performance analysis.
      3,138,727 npm
      Apache 2.0
    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

    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

    Resources