chrome-pilot-mcp
Related Servers
Alternatives to chrome-pilot-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceConnects local stdio MCP servers to an existing Chrome 144+ session, preserving the user's signed-in sessions, cookies, tabs, and extension environment without launching a second browser. It provides tab control, semantic snapshots, screenshots, pointer, keyboard, form selection, scrolling, navigation, and waiting tools.MIT
- AlicenseNot gradedqualityAmaintenanceConnects to your running Chrome browser, enabling AI agents to automate it via Playwright API with existing logins and extensions.1,511 npm3,904MIT
- AlicenseAqualityAmaintenanceControls a running Chrome/Chromium browser via the Chrome DevTools Protocol, enabling navigation, JavaScript evaluation, tab management, and raw CDP commands through MCP tools.5MIT
- AlicenseNot gradedqualityDmaintenanceEnables browser automation over MCP using a real Chrome browser with existing profile, supporting real tabs, downloads, cookies, and RPA workflows.83 npmMIT
- AlicenseNot gradedqualityBmaintenanceEnables coding agents to control and inspect a live Chrome browser via MCP, providing Chrome DevTools capabilities for automation, debugging, and performance analysis.1,010,088 npmApache 2.0
- AlicenseNot gradedqualityCmaintenanceEnables MCP clients to control and interact with the user's real Chrome browser session, leveraging existing logins, cookies, and extensions for AI-driven automation.5MIT
TDQS
Scored across 19 tools
Each tool has a clear, dedicated purpose: lifecycle (connect/disconnect/status), tab management (list/select/close), navigation (navigate/back/forward/reload), interaction (click/type/scroll/press_key), page inspection (screenshot/dump_dom/evaluate), and form helpers (fill_form/select_option). No two tools target the same action; even type and fill_form are distinguished by single vs. multi-field.
All tools are lowercase snake_case with a uniform chrome_ prefix. The second part nearly always follows a verb or verb_noun pattern (e.g., list_tabs, select_tab, click, navigate). This makes the tool set predictable and easy to navigate.
At 19 tools, the server is on the heavier side. While each tool is justifiable, several shortcuts (fill_form, select_option) could be composed from more primitive tools, and the count feels more like a comprehensive library than a minimal set. This is borderline appropriate for a browser automation tool.
Core browser operations are covered: tab lifecycle, navigation, input, screenshots, DOM access, and JS evaluation. However, there is no direct way to create a new tab or wait for conditions, which falls short of full browser automation coverage. These gaps are workable via evaluate, so minor.