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,619Apache 2.0- AlicenseNot gradedqualityBmaintenanceEnables 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.201 npmMIT
- AlicenseNot gradedqualityAmaintenanceEnables 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.63 npmMIT
- 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.4 npmApache 2.0
TDQS
Scored across 10 tools
Tools have largely distinct purposes, but some overlap exists between browser_switch_tab and browser_focus_tab, and between browser_execute_js and browser_batch. The descriptions help disambiguate, so no major confusion.
All tools share the 'browser_' prefix, which is good. The verb part mostly follows verb_noun pattern (e.g., focus_tab, get_tabs), but browser_screenshot and browser_batch break that pattern slightly. Overall consistent.
With 10 tools, the server is well-scoped for browser automation. Each tool serves a clear purpose, and the count is neither too few (which would feel incomplete) nor too many (which would be overwhelming).
The tools cover core browser operations: navigation, tab management, screenshots, JS execution, and DOM scanning. Missing explicit form filling or network interception, but the batch tool allows arbitrary CDP commands, so agents can fill gaps. Minor but not significant.