mcp-cui-chrome
Related Servers
Alternatives to mcp-cui-chrome
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityAmaintenanceEnables AI assistants to drive the user's real, already-logged-in Chrome browser locally, so they can read and navigate pages, click, type, fill forms, take screenshots, and inspect cookies, tabs, console, and network traffic without headless browsers or remote-debugging ports.1 npmISC
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to locally drive the user's own logged-in Chrome browser, including clicking, typing, reading pages, taking screenshots, running JavaScript, recording GIFs, and coordinating parallel agents across Chrome profiles and tab groups.21MIT
- AlicenseNot gradedqualityAmaintenanceLets AI agents drive the user's real Chromium browser, including opening and controlling tabs, taking screenshots, capturing network traffic, recording screen activity, and handing control back for logins or payments while using the user's existing sessions, logins, and extensions.666MIT
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to control a Chrome browser through natural language, supporting navigation, interaction, tab management, and data extraction.MIT
- AlicenseBqualityDmaintenanceEnables AI agents to fully control Google Chrome: navigate, click, fill forms, inspect DevTools, and manage tabs with parallel execution and session isolation.249 npmMIT
- AlicenseBqualityDmaintenanceEnables AI agents to directly control your real Chrome browser with full context including login sessions, cookies, and open tabs. It provides tools for page scanning, JavaScript execution, CDP control, screenshots, and physical mouse/keyboard input for authentic browser automation.20244MIT
TDQS
Scored across 13 tools
Each tool maps to a clearly distinct browser action (navigate, click, type, press, hover, drag, scroll, screenshot), and descriptions explicitly cross-reference siblings (e.g. snapshot vs reload, tabs vs navigate). Minor overlap remains between browser_navigate and browser_tabs for opening tabs, and between browser_snapshot and browser_screenshot, but the descriptions differentiate them well enough.
All 13 tools use the same browser_ prefix with snake_case, and the suffix is either a verb (navigate, click, type, press, hover, drag, scroll, reload) or a clearly paired noun (tabs, snapshot, screenshot, close). The pattern is predictable and readable throughout.
13 tools is well within the ideal 3–15 range and every tool corresponds to a real, non-redundant browser control primitive. Nothing feels padded or missing at the count level.
The surface covers the full browsing lifecycle: navigation, history, tabs, DOM reading, all common input/pointer interactions, screenshots, and session cleanup. Gaps exist for file upload, JS evaluation/console or network inspection, and explicit wait-for-condition, but core agent workflows are workable.