Skip to main content
Glama
joshoq

cc-chrome

by joshoq
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to cc-chrome

No user-submitted related servers found.

    Related Servers

    • chrome-mcp

      Mehmoodqureshi
      A
      license
      B
      quality
      A
      maintenance
      Enables controlling a real Chrome browser from MCP hosts like Claude, with extension-based or CDP fallback, supporting tabs, navigation, interaction, and page reading tools.
      20
      639 npm
      6
      MIT

    • huashu-chrome

      alchaincyf
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables any MCP-compatible AI agent to drive your own Chrome browser with your existing login state, filling forms, clicking elements, fetching data, and handling captchas without API keys or re-authentication.
      178 npm
      231
      MIT

    • chrome-bridge

      mistudio0902-lab
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables MCP clients to directly operate your existing logged-in Chrome profiles, including cookies and extensions, without re-authentication or a headless browser. It provides tools for managing tabs, navigating, reading pages, clicking, typing, and launching profiles.
      5 npm
      MIT

    • WebCore-MCP

      SrijanChakraborty2003
      F
      license
      Not graded
      quality
      C
      maintenance
      Enables a local MCP server to control an authenticated Chrome browser for interacting with Google Search, Gemini, ChatGPT, Claude, and DeepSeek, including web search and image generation without per-provider API keys.
      -
    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 21 tools

    Disambiguation4/5

    Tools are largely distinct, each targeting a specific action (click, type, fill, key, hover, drag, tap, scroll, etc.). Minor overlap exists between snapshot/find/inspect for element discovery and between fill/type for text input, but descriptions clearly differentiate them.

    Naming Consistency3/5

    Most tools follow a chrome_verb_noun pattern (navigate, evaluate, click, type, wait_for, upload_file), but a few use bare nouns (tab, snapshot, launch) which breaks consistency. Mixed conventions but still readable and predictable.

    Tool Count3/5

    21 tools is on the higher end for a server, but the breadth of Chrome automation (navigation, interaction, inspection, debugging, tab management) justifies the count. Slightly heavy but not excessive.

    Completeness4/5

    Covers a comprehensive set of browser automation capabilities: navigation, user input, element inspection, JavaScript evaluation, waiting, console/network monitoring, screenshots, file uploads, and tab management. Missing explicit cookie/storage controls, but these can be handled via evaluate.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources