chrome-use
Related Servers
Alternatives to chrome-use
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceA local MCP server that lets Claude Code and Codex drive your real, already-logged-in Chrome — reading pages, clicking, typing, filling forms, navigating, managing tabs and taking screenshots — without Playwright. It pairs with a companion extension over a local WebSocket, with an on/off switch and a domain blocklist so the AI acts only where you allow.MIT
- AlicenseNot gradedqualityAmaintenanceA 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 npmISC
- AlicenseNot gradedqualityAmaintenanceA 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 npmISC
- AlicenseNot gradedqualityAmaintenanceA 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 npmISC
- AlicenseNot gradedqualityAmaintenanceA 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 npmISC
- AlicenseNot gradedqualityAmaintenanceA 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 npmISC
TDQS
Scored across 13 tools
Most tools have clearly distinct purposes: navigation, history, inspection, interaction, waiting, and confirmation are separable. The main potential confusion is between fill and type, and between read and snapshot, but the descriptions clarify that fill clears while type does not, and read returns text while snapshot returns an accessibility tree.
All tool names follow a consistent chrome_use_verb pattern with lowercase snake_case verbs. The convention is predictable and readable throughout.
With 13 tools, the set is well-scoped for browser automation: core navigation, history, interaction, waiting, inspection, and confirmation are covered without excessive fragmentation. Each tool earns its place.
The surface covers the main browser-use lifecycle: open, read, snapshot, click, fill, type, press, wait, eval, back/forward/reload, and confirmation handling. Minor gaps include explicit hover, select-option, drag, screenshot, and tab/window management, but most can be worked around with existing tools such as eval or coordinate clicks.