Skip to main content
Glama
xiyiyiru

chrome-mcp

by xiyiyiru
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to chrome-mcp

No user-submitted related servers found.

    Related Servers

    • monkeysee

      juliocesar
      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.
      0
      1
      MIT

    • BrowserUse

      YisRime
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables MCP clients to control Chrome/Edge browsers via CDP, including page navigation, element interaction, snapshots, network debugging, script execution, and performance tracing.
      AGPL 3.0

    • Browser MCP

      CypherPotato
      F
      license
      Not graded
      quality
      D
      maintenance
      Enables MCP clients to control a real local browser window for web automation tasks such as clicking, typing, scrolling, and taking screenshots.
      7 npm
      -

    • Real Browser MCP

      ton-to-ton
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables browser automation over MCP using a real Chrome browser with existing profile, supporting real tabs, downloads, cookies, and RPA workflows.
      120 npm
      MIT

    • Playwright MCP Server

      tomscoppock
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents and clients to control a real Chromium browser through MCP tool calls, including navigation, clicking, typing, JavaScript evaluation, screenshots, and DOM snapshots. Supports multiple isolated sessions over authenticated HTTP with no disk writes.
      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.4/5.0

    Scored across 7 tools

    Disambiguation3/5

    run_cdp, execute_js, and run_drission_code all provide code/protocol execution on the current tab, creating overlap that could confuse an agent. get_manual and close_browser are distinct, but the three execution tools lack clear boundary guidance.

    Naming Consistency4/5

    Mostly consistent snake_case verb_noun style (run_cdp, get_manual, close_browser, run_drission_code, execute_js), with 'capture' and 'navigate' as minor single-verb exceptions.

    Tool Count5/5

    Seven tools are well-scoped for a Chrome automation server, covering navigation, JS execution, CDP, network capture, manual lookup, and browser lifecycle without bloat.

    Completeness4/5

    Covers the core lifecycle: launch/close, navigate/tabs, JS/CDP execution, network capture, and a manual. Minor gaps exist around explicit tab management (though navigate and run_drission_code provide switch_tab/tabs), and no dedicated element-click/type tools, but coverage is strong for the stated purpose.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources