cdp-mcp
Related Servers
Alternatives to cdp-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceMCP server that lets AI agents drive the locally installed Chrome or Edge, opening pages, taking compact accessibility-tree snapshots with @e references, and clicking, typing, scrolling, or capturing screenshots. It also exposes multi-account and cross-channel tab switching, tab sync rules, and ad-block/perf statistics.MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to drive a real Chrome instance over the Chrome DevTools Protocol — opening and navigating tabs, reading compact YAML page outlines with refs, clicking, typing, scrolling, screenshotting, and evaluating scripts — with no browser extension or installed dependencies. It also audits pages for horizontal overflow and WCAG AA contrast, available both as an MCP tool and as a CI-friendly CLI.15 npmMIT
- AlicenseNot gradedqualityBmaintenancesingle-binary MCP server that gives AI agents a browser. 66 tools for navigation, form filling, data extraction, screenshots, and DOM diffing — built on pure Chrome DevTools Protocol.14MIT
- 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
- AlicenseAqualityBmaintenanceA lightweight 30KB MCP browser automation server that uses raw Chrome DevTools Protocol to enable AI agents to browse the web, take screenshots, interact with elements, and capture live page events like console logs and network requests.41108 npm20MIT
- 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
TDQS
Scored across 3 tools
take_screenshot and interact_and_screenshot overlap since the latter is essentially a superset that also produces a screenshot, so an agent may be unsure whether to use the simpler tool or always reach for the interactive one. inspect_element is clearly distinct, and the descriptions do help clarify the intent boundary.
All names are snake_case and start with an action verb (take_, interact_, inspect_), which is mostly consistent. interact_and_screenshot deviates slightly by embedding a conjunction and a compound verb phrase rather than a clean verb_noun form.
Three tightly scoped tools is on the lean side but each earns its place for a focused CDP screenshot/inspection server. It stays well under the point where a small surface would feel arbitrary or padding-driven.
The surface covers capture, interaction, and element inspection, but notable gaps remain: no explicit navigation/URL loading tool, no wait-for-selector or network-idle readiness control, and no way to retrieve console/network diagnostics or script evaluation. Agents will hit dead ends for common flows like waiting for dynamic content before capturing.