MCP Cdp

Name: MCP Cdp
Author: dockndevai

by dockndevaiversion 0.2.3i★ –iRuns on your computer

Registry nameio.github.dockndevai/mcp-cdp

Install

Overview

Description from the maker (original English)

Safe-by-default MCP that drives an Electron/Chrome app over CDP: DOM, console, network, input.

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

User voiceiNo reviews yetReviews open together with accounts in a later step
Our basic checksi1 of 1 passedChecked from public information; code not scanned yet
UsageiNot measured yet★ –

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

Connection: Runs on your computer
Transport: stdio
Category: Web & browsers

Install

Pick the AI app you use, then copy the settings.

Before you install

Basic checks: 1 of 1 passed
Runs on your computer with your user’s permissions (files, network, apps).
You fill in yourself: CDP_PORT, CDP_HOST, CDP_MODE, CDP_ALLOW_EVAL, CDP_TARGET_ALLOWLIST, CDP_DRY_RUN

You need

npmNode.js installed (for the npx command)

Which app do you use?

ClaudeClaude CodeCursorVS CodeChatGPT

Pick your app above. We remember it, so next time the button says “Install in …”.

Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json

{
  "mcpServers": {
    "cdp": {
      "command": "npx",
      "args": [
        "-y",
        "@dockndevai/mcp-cdp"
      ],
      "env": {
        "CDP_PORT": "your-value",
        "CDP_HOST": "your-value",
        "CDP_MODE": "your-value",
        "CDP_ALLOW_EVAL": "your-value",
        "CDP_TARGET_ALLOWLIST": "your-value",
        "CDP_DRY_RUN": "your-value"
      }
    }
  }
}

Run this in your terminal

claude mcp add cdp --env CDP_PORT=your-value --env CDP_HOST=your-value --env CDP_MODE=your-value --env CDP_ALLOW_EVAL=your-value --env CDP_TARGET_ALLOWLIST=your-value --env CDP_DRY_RUN=your-value -- npx -y @dockndevai/mcp-cdp

Fill in the empty values before running it.

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "cdp": {
      "command": "npx",
      "args": [
        "-y",
        "@dockndevai/mcp-cdp"
      ],
      "env": {
        "CDP_PORT": "your-value",
        "CDP_HOST": "your-value",
        "CDP_MODE": "your-value",
        "CDP_ALLOW_EVAL": "your-value",
        "CDP_TARGET_ALLOWLIST": "your-value",
        "CDP_DRY_RUN": "your-value"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "cdp": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@dockndevai/mcp-cdp"
      ],
      "env": {
        "CDP_PORT": "your-value",
        "CDP_HOST": "your-value",
        "CDP_MODE": "your-value",
        "CDP_ALLOW_EVAL": "your-value",
        "CDP_TARGET_ALLOWLIST": "your-value",
        "CDP_DRY_RUN": "your-value"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.

Your choice stays on this device in a cookie; no account needed.

Values you fill in

CDP_PORT env
The --remote-debugging-port your app/browser exposes (default 9222).
CDP_HOST env
Host serving the DevTools endpoint (default 127.0.0.1; non-loopback needs CDP_ALLOW_REMOTE).
CDP_MODE env
Access mode: read-only | read-write | admin. Starts read-only; interactions need read-write.
CDP_ALLOW_EVAL env
Set true to allow the evaluate tool (arbitrary JS) — admin mode only. Default false.
CDP_TARGET_ALLOWLIST env
Comma-separated URL patterns; interactions are confined to matching targets. Empty = all.
CDP_DRY_RUN env
Set true to log interactions without dispatching them to the browser.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

Runs on your computer; the tool list appears in your AI app after you install it.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026

✓ Pass
Maker matches the repo
The registry name was verified with the GitHub account dockndevai, which owns the repo
… Not checked yet
Still maintained
We have not read this repo from GitHub yet
… Not checked yet
Has a licence
We have not read this repo from GitHub yet
– Not applicable
Endpoint responds
This one runs on your computer; there is no internet endpoint
– Not applicable
Sign-in with OAuth
Runs on your computer and uses local settings instead
… Not checked yet
No hidden instructions in tool descriptions
Runs on your computer; we can only read tool lists from internet endpoints

Compared with others in Web & browsersi

More stars than 0% of the other 880 servers in this category
Published to the registry more recently than 73% of the other 880 servers in this category
Basic checks equal to or better than 100% of the other 880 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is MCP Cdp safe?

It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

The registry does not list a required key, though some servers ask you to sign in on first use.

Does it run on my computer or in the cloud?

It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).

Is it still maintained?

The GitHub repo last changed –, and the latest version (0.2.3) reached the registry 12 days ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.

What can I use instead?

In the same category: Browser Use, Chrome DevTools MCP, MCP Server Browser

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

Browser Use

by browser-use

Lets AI do web tasks for you, such as filling forms, searching and extracting data, in the maker’s cloud browsers or on your computer.

Computer or cloud★ 120,087MITUpdated 17 days ago

Install

Chrome DevTools MCP

by ChromeDevTools

Lets AI use Chrome’s developer tools to inspect pages, find what makes them slow and spot errors. Made by the Chrome DevTools team.

Runs on your computer★ 54,821Apache-2.0Updated 16 days ago

Install

MCP Server Browser

by bytedance

MCP server for browser use access

Runs on your computer★ 39,550Apache-2.0Updated 14 months ago

Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

mcp-cdp

A safe-by-default Model Context Protocol server that drives an Electron or Chrome/Chromium app over the Chrome DevTools Protocol (CDP) — instead of pixel-level GUI automation. Point it at the app's --remote-debugging-port and an agent gets the DOM, console, network requests, real input (click / type / navigate), and — gated — JavaScript evaluation.

Why this beats computer-use for a desktop/web app:

The DOM, not a screenshot. The agent reads exact rendered HTML and can query any element — far more information, and it sees things that aren't on screen.
Console + network. When a test fails, the uncaught exception or the failed request is right there — no guessing from an image.
No collisions. Each agent attaches to its own debugging port, so parallel agents (e.g. one per git worktree) never fight over one desktop.
Cross-OS. CDP works identically on macOS, Linux and Windows — the same flow runs on a headless VPS.

Part of the dockndevai MCP server suite — one governance model across all of them.

What it gives an agent

Starts read-only (see Safe by default); higher-capability tools are only registered when you raise the mode.

Tool	For	Needs mode
`list_targets`	list pages / webviews / Electron windows (id, type, title, url)	read-only
`dom_snapshot`	rendered HTML of the page or a selector's subtree	read-only
`query_dom`	outer HTML of every element matching a CSS selector	read-only
`console_logs`	recent console output + uncaught exceptions	read-only
`network_requests`	recent requests (method, url, status, mime; headers never captured)	read-only
`screenshot`	a PNG of the viewport	read-only
`click`	click the first element matching a selector	read-write
`type_text`	type into the page (focus a selector first)	read-write
`press_key`	Enter / Tab / Escape / Backspace / Delete / Arrows	read-write
`navigate`	navigate a target to a URL (confirmed)	read-write
`evaluate`	run a JavaScript expression in the page	admin + `CDP_ALLOW_EVAL`

Install

npx -y @dockndevai/mcp-cdp

Expose a debugging port

Start your app (or a worktree's dev build) with an explicit port — one per agent:

Electron app: your-app --remote-debugging-port=9222, or in main-process code app.commandLine.appendSwitch('remote-debugging-port', '9222') before app.whenReady().
Plain Chrome/Chromium: chrome --headless=new --remote-debugging-port=9222 --user-data-dir=/tmp/p1 .

Check it's up: curl http://127.0.0.1:9222/json/version.

Configure

"mcpServers": { "cdp": { "command": "npx", "args": ["-y", "@dockndevai/mcp-cdp"], "env": { "CDP_PORT": "9222", "CDP_MODE": "read-only" } } } }

See docs/CLIENTS.md for Claude Code / Cursor / Codex / VS Code / Windsurf, and .env.example for every variable.

Safe by default

Enforced by src/security.ts. The browser process is the real boundary — this keeps an agent inside the targets and actions you intend:

`CDP_MODE` — read-only (default) → read-write → admin. Tools above the mode aren't registered, so in read-only the agent cannot click, type or navigate at all.
`CDP_TARGET_ALLOWLIST` — confine interactions to targets whose URL matches your patterns (empty = all). Reads (inspection) are always allowed.
`CDP_PROTECTED_TARGETS` — targets that can be inspected but never interacted with. Defaults protect sign-in pages (accounts.google.com, login.microsoftonline.com, …) and browser internals (chrome://, devtools://, extensions).
`CDP_ALLOW_EVAL` — evaluate is arbitrary code execution in the renderer: admin mode plus this flag, refused on protected targets, with a human confirmation.
`CDP_DRY_RUN` — interactions log their intent and return without dispatching.
Secrets — request/response headers are never captured (cookies/auth), and sensitive URL query values are redacted. evaluate and navigate also prompt a human via MCP elicitation.
Loopback only — the endpoint must be 127.0.0.1 unless CDP_ALLOW_REMOTE=true.

Optional AI risk guard. Set CDP_GUARD_MODE=monitor|enforce to have the evaluate tool consult a local laya-guard daemon (pipx install laya-guard && laya-guard) that classifies the JS expression allow/confirm/block before it runs. It runs *after* the eval gate and can only tighten, never grant; fails closed.

There is a bundled skill, cdp-safe-operations, that teaches an agent how to expose a port, read the DOM/console/network instead of screenshots, the safety rules, and the "why did this fail?" workflow. See also SECURITY.md.

Developing

npm install

npm run build

list the tools:

echo '{"jsonrpc":"2.0","id":1,"method":"tools/list","params":{}}' | CDP_PORT=9222 node dist/index.js npm test

Licence

MIT

MCP Cdp

Overview

PopNx MCP’s three pillars

What you can do with it

Install

Before you install

Values you fill in

What it can do

Basic checksi

Maker matches the repo

Still maintained

Has a licence

Endpoint responds

Sign-in with OAuth

No hidden instructions in tool descriptions

Compared with others in Web & browsersi

Common questions

Alternatives

Browser Use

Chrome DevTools MCP

MCP Server Browser

README from the maker

mcp-cdp

What it gives an agent

Install

Expose a debugging port

Configure

Safe by default

Developing

list the tools:

Licence