Skip to main content
Glama
JackZhao98

chrome-automation-mcp

by JackZhao98
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to chrome-automation-mcp

No user-submitted related servers found.

    Related Servers

    • Playwright MCP

      AmokOrg
      A
      license
      Not graded
      quality
      D
      maintenance
      A Model Context Protocol (MCP) server that provides browser automation capabilities using Playwright.
      4,633,135 npm
      Apache 2.0

    • SmartBrowserMCP

      Jenish3601
      A
      license
      B
      quality
      D
      maintenance
      A Model Context Protocol server for web automation that enables browser control, element interaction, content extraction, and monitoring using Playwright.
      7
      6 npm
      ISC

    • mcp-playwright

      executeautomation
      A
      license
      B
      quality
      D
      maintenance
      A Model Context Protocol server that provides browser automation capabilities using Playwright. This server enables LLMs to interact with web pages, take screenshots, and execute JavaScript in a real browser environment.
      32
      11,239 npm
      5,644
      MIT

    • Puppeteer MCP Server

      twolven
      A
      license
      Not graded
      quality
      C
      maintenance
      A Model Context Protocol server that provides browser automation capabilities using Playwright, enabling LLMs to interact with web pages, take screenshots, and execute JavaScript in a real browser environment.
      18
      Apache 2.0

    • Playwright MCP Server

      devskido
      A
      license
      B
      quality
      D
      maintenance
      A Model Context Protocol server that provides browser automation capabilities using Playwright, enabling LLMs to interact with web pages, take screenshots, generate test code, scrape web content, and execute JavaScript in a real browser environment.
      32
      11,239 npm
      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

    A3.7/5.0

    Scored across 10 tools

    Disambiguation4/5

    Most tools have clearly distinct purposes (launch, navigate, script execution, storage, session management). Some potential overlap exists between cleanup_sessions and close_all_browsers, and get_login vs set_storage both touch auth data, but descriptions distinguish them adequately.

    Naming Consistency4/5

    Names follow a mostly consistent snake_case verb_noun pattern (launch_browser, run_script, close_browser, list_sessions). Minor deviations like navigate_to (verb only) and get_login (get is odd for an interactive capture tool) slightly break the pattern but remain readable.

    Tool Count5/5

    10 tools is well-scoped for a browser automation server, with each tool earning its place across launch, control, scripting, and cleanup concerns. No redundant or filler tools.

    Completeness4/5

    Covers the full lifecycle: launch, navigate, script execution, storage/auth, session listing, and cleanup/closing. Missing explicit page-interaction primitives (screenshot, click, get content) which agents must reach for scripts to accomplish, but core workflows are covered.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources