cdp-bridge
Related Servers
Alternatives to cdp-bridge
No user-submitted related servers found.
Related Servers
AlicenseNot gradedqualityCmaintenanceConnects AI agents to a real Chrome browser through a hosted MCP endpoint, enabling them to search action manuals and operate logged-in websites via direct API calls or UI automation.1,632Apache 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
- AlicenseNot gradedqualityDmaintenanceEnables AI agents to control your existing Chrome browser via MCP, using your logged-in sessions for automation on authenticated sites. Provides high-level browser tools plus raw CDP and Chrome API access.MIT
- AlicenseNot gradedqualityAmaintenanceConnects MCP-compatible AI agents to an anti-detection browser backend, enabling web navigation, interaction, search, extraction, downloads, and session reuse across multi-tab workflows.581 npmMIT
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to drive a local Chromium browser through MCP, with persistent sessions, one-click registration across supported AI apps, and CDP/Playwright-based control.MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to drive a live, persistent self-hosted Chromium session over MCP, running browser actions via Playwright/CDP, capturing page snapshots, screenshots and videos, and managing uploads and downloads in the same tabs and signed-in accounts a human user can take over at any time.Apache 2.0
TDQS
Scored across 12 tools
Each tool has a distinct role, and the descriptions explicitly differentiate the tricky pairs (browser_switch_tab vs browser_focus_tab, browser_scan vs browser_observe). Remaining overlap: browser_execute_js and browser_batch both accept raw CDP commands, which could cause misselection for advanced operations.
Every tool follows the same browser_<verb>_<noun> pattern (browser_get_tabs, browser_save_image, browser_wait), with only minor noun-less variants like browser_scan and browser_act that still fit the convention. Fully predictable naming.
12 tools is well within the sweet spot for a browser automation bridge. Each tool covers a distinct capability layer (perception, action, navigation, tab management, capture, escape hatches) and none feel redundant.
Core observe/act/navigate/wait/screenshot/tab workflows are fully covered, including ref-staleness handling and raw CDP escape hatches. Minor gaps: no tab create/close, and no keyboard press, scroll, or hover actions beyond click/fill, though these are workable via browser_execute_js.