Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type @ followed by the MCP server name and your instructions, e.g., "@CDP-MCP Server set a breakpoint at line 42 of app.js and show me the stack trace when it's hit"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
A system-wide MCP server that wraps the Chrome DevTools Protocol, giving AI agents full access to low-level browser debugging: breakpoints, stack traces, stepping, scope inspection, network interception, and source maps.
Category | Count | Highlights |
Connection | 4 | Connect, disconnect, list/attach targets |
Debugger | 15 | Breakpoints, stepping, call stacks, scope inspection, eval on frame, exception breakpoints, blackboxing |
Runtime | 4 | JS evaluation, object property drilling, console capture |
Network | 9 | Request monitoring, response bodies, Fetch interception (continue/fail/fulfill) |
Source | 3 | Script listing, source retrieval, source map resolution |
Related MCP server: MCP JS Debugger
# Install
npm install
# Build
npm run build
# Launch Chromium with debugging
chromium --remote-debugging-port=9222
# Run (stdio mode for single agent)
node dist/bin/cdp-mcp-server.js --stdio
# Run (HTTP mode for multi-agent)
node dist/bin/cdp-mcp-server.js --http --port 3100{
"mcpServers": {
"cdp-debugger": {
"command": "node",
"args": ["/path/to/cdp-mcp-server/dist/bin/cdp-mcp-server.js", "--stdio"]
}
}
}--stdio Stdio transport (default)
--http HTTP transport
--port <n> HTTP port (default: 3100)
--chrome-port <n> Chrome debug port (default: 9222)
--chrome-path <p> Chrome binary (default: /usr/bin/chromium)
--profile isolated Temp profile (default)
--profile real Use real profile
--attach Only attach, never launch
--launch Always launch new instanceBuilt from scratch — No forks, full control
Browser page debugging — Not Node.js-only like alternatives
Never kills Chrome — Only detaches CDP session on exit
Network interception safety — 30s auto-continue watchdog, emergency cleanup on crash
Dual transport — stdio for single-agent, HTTP for multi-agent
MIT
This server cannot be deployed
Live browser debugging for AI assistants — DOM, console, network via MCP.
Headless browser primitives for AI agents when sites need real JS rendering.
A paid remote MCP for AI agent browser DevTools MCP, built to return verdicts, receipts, usage logs,
Hosted browser for AI agents: screenshots, post-JS DOM, console, WCAG. No install, no API key.