Skip to main content
Glama
Sign In
CDPM

CDPM

by IGELHARINE
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to CDPM

No user-submitted related servers found.

    Related Servers

    • one-chrome

      AbinMadathil07
      A
      license
      Not graded
      quality
      C
      maintenance
      Lets several AI clients drive one shared, signed-in Chrome at the same time, giving each session its own background tabs and tab group with per-tab leases so mutations queue while reads overlap. Exposes a full Chrome DevTools-style toolset plus Claude's 31-member browser toolset, along with an HTTP endpoint that turns Messages API tool_use blocks into tool_result blocks.
      MIT

    • devtools-fleet-mcp

      pluginslab
      A
      license
      B
      quality
      B
      maintenance
      Enables 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.
      38
      165 npm
      MIT

    • opencode-browser-mcp

      mirsella
      A
      license
      Not graded
      quality
      A
      maintenance
      Browser 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.
      607 npm
      1
      MIT

    • playwright-mcp-orchestrator

      mediar-ai
      A
      license
      Not graded
      quality
      D
      maintenance
      A 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
      MIT

    • MultiZen

      Petridis03895
      F
      license
      Not graded
      quality
      A
      maintenance
      Exposes a local MCP endpoint that lets AI agents and human operators drive isolated Chromium profiles — each with its own cookies, fingerprint, and proxy — through tools for navigation, clicking, typing, extraction, screenshots, JS evaluation, tabs, and cookie management. Persistent per-profile session state keeps logins and context alive across launches and across AI sessions, so agents can complete real authenticated workflows.
      -

    • MultiZen MCP Server

      sita81522
      A
      license
      Not graded
      quality
      A
      maintenance
      Exposes a localhost MCP endpoint that lets agents launch and drive isolated, persistent browser profiles — navigating, clicking, typing, extracting, screenshotting, evaluating JS, managing tabs and cookies, and sending raw CDP commands. Each profile keeps its own cookies, login state, fingerprint, and proxy across sessions, enabling real authenticated workflows from Cursor, Claude Desktop, or any MCP client.
      MIT
    Deploy Server
    Let your AI agent see the webWeb-to-screenshot MCP for Claude, Cursor and Codex. No cookie banners. Free to start.snap-render.comAd

    TDQS

    B3.4/5.0

    Scored across 36 tools

    Disambiguation4/5

    Most tools have clearly distinct purposes, and descriptions actively distinguish similar pairs such as browser_snapshot vs browser_text, browser_type vs browser_fill, and browser_dialog vs browser_permission. Some overlap remains around read/wait modalities (browser_wait vs slot_inbox wait) and the large surface increases the chance of misselection, but boundaries are generally well documented.

    Naming Consistency5/5

    All tool names use a consistent snake_case convention with clear prefixes: browser_* for browser operations and slot_* for multi-agent/control operations. The pattern is predictable and readable throughout the set.

    Tool Count2/5

    36 tools exceeds the 25+ threshold for a heavy surface and likely burdens agent tool selection, even though many are specialized for browser automation. The domain is complex, so this is over-provisioned rather than an extreme 50+ mismatch, but consolidation could improve usability.

    Completeness4/5

    The surface covers the browser automation lifecycle well: launch/close, tabs, reading/capture, interactions, dialogs, permissions, downloads, uploads, network inspection/blocking, and multi-agent coordination. Minor gaps include explicit cookie/localStorage management and console log capture, though browser_eval and network tools provide workarounds.

    Maintenance

    ActivityNo data
    ResponsivenessSyncing

    Resources