Skip to main content
Glama
leeguooooo

chrome-use

by leeguooooo
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Rust
Local

Related Servers

Alternatives to chrome-use

No user-submitted related servers found.

    Related Servers

    • byob

      henrykang07945
      A
      license
      Not graded
      quality
      A
      maintenance
      A local MCP server that lets AI coding assistants drive the user's own already-signed-in Chrome, so agents can read logged-in pages, click, fill forms, navigate, screenshot, inspect network traffic and storage, and run multi-step browser workflows without a separate headless browser or remote debugging port. All communication stays on the user's machine and agent-opened tabs are grouped so they never steal focus.
      1 npm
      ISC

    • byob

      Panagiotisu0227
      A
      license
      Not graded
      quality
      A
      maintenance
      A local MCP server that lets AI coding tools drive the real Chrome browser you already have open, so agents can read logged-in pages, click, fill forms, take screenshots, and inspect tabs, cookies, and network traffic. All communication stays on your machine, with no debugging port or manual cookie copying required.
      1 npm
      ISC

    • byob

      melissa89018
      A
      license
      Not graded
      quality
      A
      maintenance
      A local MCP server that lets AI coding tools drive your real, already-logged-in Chrome — navigating, reading, clicking, filling forms, screenshotting, inspecting network traffic and cookies. Because it runs through a browser extension instead of a debugging port, it works on authenticated pages and passes bot detection without extra setup.
      1 npm
      ISC

    • byob

      robertmoon6914
      A
      license
      Not graded
      quality
      A
      maintenance
      A local MCP server that enables AI coding tools to drive the user's real, already-logged-in Chrome browser — reading pages, clicking, typing, navigating tabs, screenshots, and cookie, network, and storage access — without opening a remote-debugging port.
      1 npm
      ISC

    • byob

      Pavelj43
      A
      license
      Not graded
      quality
      A
      maintenance
      A local MCP server that lets AI coding tools drive the user's actual, already-logged-in Chrome browser — snapshotting pages, clicking, typing, navigating, reading content, taking screenshots, and inspecting cookies, network traffic, and console output. Browser automation happens through a Chrome extension using Native Messaging, so no remote-debugging port is exposed and all communication stays on the local machine.
      1 npm
      ISC

    • Pagerunner

      Enreign
      F
      license
      Not graded
      quality
      C
      maintenance
      A Chrome browser automation MCP server. Connect Claude (or any MCP client) to a real Chrome session — using your existing profiles with their cookies, saved passwords, and history.
      3
      -
    Deploy Server
    Context Every Agent Can ShareAgents share what they learn, hand off work, and keep it when you switch models. Start with 5 GB free.fulcradynamics.comAd

    TDQS

    A3.5/5.0

    Scored across 12 tools

    Disambiguation4/5

    Most tools are clearly distinct: open/read/snapshot/back/forward/reload each have a unique role, and click/fill/type/press target different interaction primitives. The only mild overlap is chrome_use_fill vs chrome_use_type (both insert text; fill clears first and handles rich editors), which descriptions clarify but an agent could still misselect in edge cases.

    Naming Consistency5/5

    Every tool uses the identical chrome_use_<verb> pattern with short, action-oriented verbs (back, open, read, click, fill, type, press, eval, wait, forward, reload). No mixing of camelCase, casing, or verb styles across the set.

    Tool Count5/5

    12 tools is squarely within the well-scoped range and each tool maps to a real browser-automation need (navigation, reading, element location, input, waiting). There is no obvious filler; the surface is compact yet covers the core loop of navigate-snapshot-act-wait.

    Completeness4/5

    The core automation lifecycle is covered: navigation, content reading, accessibility snapshotting, clicking/filling/typing/pressing, JS eval, and rich wait conditions. Gaps remain for tab/window management (list/new/close tabs), scrolling, dropdown selection, and screenshots, though most can be worked around via chrome_use_eval.

    Maintenance

    ActivityActive
    ResponsivenessResponsive

    Resources