Skip to main content
Glama
escapeWu

chrome-agent-bridge

by escapeWu
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to chrome-agent-bridge

No user-submitted related servers found.

    Related Servers

    • chrome-mcp

      wzxklm
      A
      license
      Not graded
      quality
      B
      maintenance
      Local MCP server for persistent Chrome automation with multi-profile support, enabling tab management, page inspection, element interaction, JavaScript evaluation, and screenshots while preserving login sessions across restarts.
      96 npm
      3
      MIT

    • agent-browser-mcp

      LinVireo
      A
      license
      A
      quality
      A
      maintenance
      MCP server that drives your real Chrome/Edge/Opera browser through a Chrome extension and DevTools Protocol, preserving logins and session state, and can also perform OS-level mouse and keyboard input behind approval.
      51
      203 PyPI
      2
      MIT

    • newton-browser

      Koala-Studios
      A
      license
      Not graded
      quality
      A
      maintenance
      MCP server for local browser control via Chrome/Edge extension, enabling agents to open isolated tabs, observe pages, take screenshots, and interact with accessible controls using an existing browser profile. It is agent-agnostic, local-only, and supports safe session scoping with origin grants and sensitive-data blocking.
      MIT

    • universal-browser-bridge

      code-x-coffee
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables MCP-compatible AI agents to securely control Chrome tabs via a local bridge, with explicit per-tab sharing and human approval for consequential actions.
      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

    C2.4/5.0

    Scored across 96 tools

    Disambiguation2/5

    Many tools overlap significantly, such as browser_click vs browser_act, debugger_capture_hit vs debugger_wait_for_paused, and get_object_properties vs get_scope_variables_enhanced. The abundance of similarly prefixed tools (proto_*, sourcemap_*, analysis_*) makes it hard for an agent to pick the right one without deep inspection.

    Naming Consistency2/5

    Naming conventions are mixed: some tools use verb_noun (browser_open_tab), some use noun_verb (sourcemap_fetch_and_parse), and others are single nouns (breakpoint, watch) or ad-hoc (understand_code, ast_transform_preview). Snake_case is used throughout, but the inconsistent patterns and occasional abbreviations reduce predictability.

    Tool Count1/5

    With 96 tools, this server is far beyond any reasonable scope, even for a Chrome DevTools bridge. The count alone overwhelms agent tool selection and introduces unnecessary complexity, making it an extreme mismatch.

    Completeness4/5

    The surface is remarkably comprehensive, covering browser automation, CDP, network monitoring, debugging, source maps, binary formats, and JavaScript analysis. Minor gaps like dedicated cookie editing exist, but these can be worked around via browser_cdp_send or debugger_evaluate.

    Maintenance

    ActivitySlowing
    ResponsivenessWithin a week

    Resources