MCP.Market

Devcdp MCP server

by Dayananda-D·io.github.Dayananda-D/devcdp·v5.0.1·2 stars
No reviews yet

Chrome DevTools for AI assistants: console, network, DOM, source maps, breakpoints, live variables.

A85/100grade A
Write a reviewInstall
What users say
No reviews yet
Be the first
Safety scan
A85/100

full report

Adoption
Growing

2 stars45 downloads/wk

Reviews

Write one

Nobody has reviewed Devcdp yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Devcdp tools

No tool declarations could be read from the package source. They show once the server is installed.

Public scan report

scanner v0.1.10 · 2026-10-02 · same rubric, same numbers if you re-run it

1 medium
  • Code scan38 source files scanned20/25
  • –Live reliabilityno gateway calls yet and no remote to proben/a
  • –Tool poisoningtools not inspected (local package is not executed); not countedn/a
  • Auth qualitylocal package, no credentials required12/15
  • Maintenancelast push 6 days ago15/15
  • Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10

Findings (1)

  • mediumeval / new Function usedexec.eval
    src/cdp/connection.js: …do rather than hiding it. */ async eval(expression, opts = {}) { const { …
Overall 85/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How Devcdp compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
85/100
higher than 70% of 48,273 servers
GitHub stars
2
more than 75% of 28,534 servers
Downloads a week
45
more than 39% of 11,915 servers with a package

Install Devcdp in Claude Code, Cursor or VS Code

Runs npx -y devcdp on your machine. Read the scan report first; the gateway never runs local packages.

claude mcp add devcdp -- npx -y devcdp
Add to Cursor

What the publisher says

From the Devcdp repository's README, as published. We do not edit it. Read it on GitHub

DevCDP

Real Chrome DevTools access for an AI assistant, over MCP. Your assistant reads the console, watches the network, queries the DOM, resolves source maps, sets breakpoints and inspects live variables — so it can tell you why something broke instead of guessing from a pasted error.

Works with any assistant that speaks MCP, and with any web app: nothing about a particular framework, product or company is built in.

74 tools — see docs/TOOLS.md for the full reference, generated from the server itself, and docs/PERFORMANCE.md for measured token costs and how to lower them.

What it does

Four things it is careful about

It never fakes success. A breakpoint that cannot bind says bound: false and explains why. A body Chrome has discarded says so. A capture from a pause that has already resumed is marked stale. Every failure is {ok: false, code, message, hint} with the next action named.

It tells you where its knowledge ends. Chrome cannot replay console history to a debugger that attaches later, so attaching reports exactly that rather than presenting an empty buffer as "no errors".

It cannot be stranded. Every call into the page is bounded on our side — Runtime.evaluate's own timeout is enforced by the renderer, which is useless when the renderer is what is stuck. A page wedged in an infinite loop fails in seconds with the recovery path named, and DevCDP will abort the runaway script and retry by itself.

It never leaves your app frozen. Breakpoints capture what you need and then resume on their own. A pause held deliberately is still released after maxPauseMs, and everything is cleaned up on disconnect.

Install

Requirements: Node 18+, Chrome, and an MCP-capable assistant.

Pick whichever fits your client. All of them run the same server on your machine; nothing is hosted.

Any MCP client, from npm. Add to the client's MCP config:

{ "mcpServers": { "devcdp": { "command": "npx", "args": ["-y", "devcdp"] } } }

On native Windows some clients need "command": "cmd", "args": ["/c", "npx", "-y", "devcdp"].

Claude Code, as a plugin (server plus a skill that tells Claude when to reach for which tool):

/plugin marketplace add Dayananda-D/DevCDP
/plugin install devcdp@devcdp

Cursor: , or add the JSON above to ~/.cursor/mcp.json.

Gemini CLI, as an extension that also carries the usage guidance:

gemini extensions install https://github.com/Dayananda-D/DevCDP

opencode: opencode mcp add, or in opencode.json:

{ "mcp": { "devcdp": { "type": "local", "command": ["npx", "-y", "devcdp"], "enabled": true } } }

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

Devcdp: common questions

Is Devcdp MCP server safe?
Yes, by our scan: it is graded A (85/100). Read the Devcdp safety report
How do I install Devcdp?
It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
Does Devcdp need an API key?
No secret keys are declared. It reads 2 settings from the environment.
Is Devcdp maintained?
The last commit was 38 days ago (2026-09-25). The latest release is v5.0.1.
What can I use instead of Devcdp?
Servers from other publishers that do the same job: Firefox DevTools MCP server, Chrome DevTools MCP server and Chrome DevTools MCP server. Compare all Devcdp alternatives.
How does Devcdp compare with other MCP servers?
safety score 85/100 (higher than 70% of 48,273 servers); github stars 2 (more than 75% of 28,534 servers); downloads a week 45 (more than 39% of 11,915 servers with a package). Full comparison.

Alternatives to Devcdp

Same job from other publishers: the closest match first, then the best rated.

All Devcdp alternatives →