arc-cdp-mcp
Related Servers
Alternatives to arc-cdp-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceEnables browser automation (navigate, screenshot, click, type, etc.) for Claude Code via MCP protocol, with a Chrome extension for configuration.2MIT
- AlicenseAqualityBmaintenanceEnables Claude Code to control your actual logged-in Chrome browser through an MV3 extension, perceiving pages as element tables and performing actions such as navigation, clicks, typing, and assertions via CDP.824 npm14MIT
- AlicenseAqualityCmaintenanceEnables Claude Code to control Google Chrome using local Playwright sessions to navigate, click, fill forms, take screenshots, and read pages, with security guards and an audit log.68 npmMIT
- AlicenseNot gradedqualityBmaintenanceEnables Claude Code to drive your everyday logged-in browser session — opening and closing tabs, navigating, clicking, typing, scrolling, filling forms, uploading files, taking screenshots, and reading page text, console output and network requests. It runs through a local native-messaging bridge, scoping each client session to its own window behind yours.216 npm2MIT
- AlicenseNot gradedqualityAmaintenanceEnables Claude Code to control a real browser for navigation, interaction, screenshots, accessibility snapshots, network and console monitoring, and automated end-to-end testing through MCP tools.106 npmMIT
- AlicenseNot gradedqualityAmaintenanceEnables Claude Code to control a real browser for navigation, interaction, screenshots, accessibility snapshots, and automated end-to-end testing through MCP tools.106 npmMIT
TDQS
Scored across 11 tools
Each tool has a clear, distinct purpose with no overlap: click, type, press, eval, console, network, read_page, tabs, navigate, close_tab, and screenshot cover separate actions. The names unambiguously indicate their functions.
All tools follow a uniform prefix 'arc_' with lowercase and underscores. While some are verbs (click, type, navigate) and some are nouns (console, network, tabs), the consistent format and clear action-oriented names make the set highly coherent.
With 11 tools, the set is well-scoped for browser automation. Each tool serves a necessary function, and the count falls comfortably within the ideal 3-15 range without feeling bloated or sparse.
The toolkit covers the core browser automation lifecycle: navigation, interaction (click, type, press), reading content (read_page, screenshot), debugging (console, network, eval), and tab management (tabs, close_tab). Missing features like refresh/back are minor and do not detract from overall completeness.