chrome
Related Servers
Alternatives to chrome
No user-submitted related servers found.
Related Servers
- AlicenseBqualityBmaintenanceEnables an AI agent to control a real browser through a local WebSocket bridge and extension, including navigating, reading the DOM, clicking, typing, filling forms, scrolling, dragging, taking screenshots, and managing tabs, cookies, and network activity.23MIT
- AlicenseNot gradedqualityCmaintenanceEnables local opencode agents to control a live Chrome browser via MCP tools, including tab management, JavaScript execution, clicking, form filling, page reading, screenshots, and console log retrieval.3MIT
- AlicenseNot gradedqualityBmaintenanceEnables coding agents to control the user's real Chrome or Firefox tabs, with their existing logins, to read pages, click, type, fill forms, take screenshots, inspect network traffic and run JavaScript. It works through a paired browser extension over a local WebSocket connection, so automation happens in the browser the user is actually looking at, including shadow DOM, cross-origin iframes, dialogs and single-page apps.MIT
- AlicenseNot gradedqualityAmaintenanceLets AI coding tools drive the user's already-signed-in Chrome browser — reading and snapshotting pages, clicking, typing, uploading files, screenshotting, and inspecting tabs, cookies, console, and network traffic. It works through a local Chrome extension bridge, so no remote debugging port is opened and the real, authenticated browser session is used.1 npmISC
- AlicenseNot gradedqualityBmaintenanceEnables any coding agent to use the user's existing Chrome profiles and logins to open tabs, read pages, fill forms, click through flows, and take screenshots.21 npmMIT
- AlicenseBqualityBmaintenanceEnables AI agents to control headless and VS Code-integrated browsers for navigation, snapshots, clicking, typing, screenshots, and live tab streaming.25MIT
TDQS
Scored across 24 tools
Most tools target clearly distinct concerns (navigation, interaction, inspection, storage, emulation), so an agent can pick correctly. Minor overlaps exist: opening a tab via tabs vs navigate(newTab=true), typing-with-Enter via type vs press, and visual tools screenshot/highlight. These are adequately differentiated in the descriptions.
Consistent snake_case throughout with no camelCase mixing, and a semi-predictable convention where interaction tools are verbs (click, type, drag, scroll) and inspection tools are nouns (status, tabs, console, network, cookies). The verb/noun mix and a few compound names (fill_form, upload_file, wait_for) keep it from being a strict single pattern.
24 tools is on the heavy side of the ideal range, but for a full browser-control surface covering navigation, input, DOM/a11y inspection, network, storage and emulation, each tool maps to a genuine capability. No obvious redundant tool inflates the count.
Coverage is broad and coherent across the browser lifecycle: navigation, tab management, DOM/snapshot/screenshot, input primitives, form fill, uploads, dialogs, console, network, cookies, emulation and debugger control. Gaps like explicit storage APIs and download handling exist but are workable via evaluate.