CDPM
Related Servers
Alternatives to CDPM
No user-submitted related servers found.
Related Servers
- AlicenseBqualityBmaintenanceEnables multiple AI agents to each run Google's full Chrome DevTools toolset in an isolated Chrome instance with saved logins, origin allowlists, reconnect recovery, and process cleanup. It also provides visibility into running browsers so stale sessions can be inspected or reaped.3639 npmMIT
- AlicenseNot gradedqualityAmaintenanceBrowser automation for OpenCode using Chrome DevTools and a shared Chromium profile, with per-session tab isolation so concurrent agents don't interfere. Enables browser agents to use existing signed-in sessions with shared cookies and extensions.209 npm1MIT
- FlicenseNot gradedqualityDmaintenanceA multi-agent orchestrator that enables multiple AI agents to share a single Chrome browser instance with tab isolation and shared state. It preserves local browser data like cookies and logins while allowing concurrent agent sessions through the official Playwright MCP.10-
- AlicenseNot gradedqualityAmaintenanceEnables multiple agents to share a single Chrome browser with isolated tabs and shared sessions, allowing coordinated browsing and automation.21 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.3 npmApache 2.0
- AlicenseNot gradedqualityBmaintenanceLets coding agents drive a real headful Chromium over CDP on a remote headless box, giving each project its own persistent profile, isolated login sessions, downloads, and on-demand browser lifecycle. When a site needs a human for sign-in, a captcha, 2FA, or a passkey, the operator opens the same browser from their own machine, completes the step, and hands control back to the agent.MIT
TDQS
Scored across 36 tools
Most tools target clearly distinct browser actions, and descriptions carefully differentiate overlapping areas like snapshot/text/screenshot and type/fill/press_key. Minor overlap exists between browser_status and browser_tabs, and the many input/interaction tools require careful reading, but misselection risk is low.
All tools use consistent snake_case with clear browser_ and slot_ domain prefixes. Although some names are noun-first (browser_snapshot, browser_tabs) and others verb-first, the naming is highly predictable and no chaotic mixing is present.
36 tools is very heavy for a single MCP server and exceeds the typical well-scoped range. While many tools map to distinct browser capabilities, the surface could be consolidated (e.g., input actions, network detail, tab status) to reduce selection overhead.
The set covers browser lifecycle, navigation, reading, interaction, network inspection, dialogs, permissions, downloads, PDF, eval, and multi-agent coordination well. Minor gaps remain around console logs, cookie/storage management, frame handling, and device emulation, but agents can often work around them.