CDP-MCP Server
Wraps Chrome DevTools Protocol to provide AI agents with low-level browser debugging tools including breakpoints, stack traces, stepping, network interception, and source maps.
README
CDP-MCP Server
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.
35 MCP Tools
| 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 |
Quick Start
# 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
MCP Client Config
{
"mcpServers": {
"cdp-debugger": {
"command": "node",
"args": ["/path/to/cdp-mcp-server/dist/bin/cdp-mcp-server.js", "--stdio"]
}
}
}
CLI Options
--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 instance
Architecture
- Built 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
License
MIT
Recommended Servers
playwright-mcp
A Model Context Protocol server that enables LLMs to interact with web pages through structured accessibility snapshots without requiring vision models or screenshots.
Magic Component Platform (MCP)
An AI-powered tool that generates modern UI components from natural language descriptions, integrating with popular IDEs to streamline UI development workflow.
Audiense Insights MCP Server
Enables interaction with Audiense Insights accounts via the Model Context Protocol, facilitating the extraction and analysis of marketing insights and audience data including demographics, behavior, and influencer engagement.
VeyraX MCP
Single MCP tool to connect all your favorite tools: Gmail, Calendar and 40 more.
graphlit-mcp-server
The Model Context Protocol (MCP) Server enables integration between MCP clients and the Graphlit service. Ingest anything from Slack to Gmail to podcast feeds, in addition to web crawling, into a Graphlit project - and then retrieve relevant contents from the MCP client.
Kagi MCP Server
An MCP server that integrates Kagi search capabilities with Claude AI, enabling Claude to perform real-time web searches when answering questions that require up-to-date information.
E2B
Using MCP to run code via e2b.
Neon Database
MCP server for interacting with Neon Management API and databases
Exa Search
A Model Context Protocol (MCP) server lets AI assistants like Claude use the Exa AI Search API for web searches. This setup allows AI models to get real-time web information in a safe and controlled way.
Qdrant Server
This repository is an example of how to create a MCP server for Qdrant, a vector search engine.