cdp-tools
MCP server that connects AI assistants to Chrome DevTools Protocol for runtime debugging - set breakpoints, inspect variables, monitor network traffic, and automate browser interactions
claude mcp add --transport stdio indate-cdp-tools-mcp npx -y cdp-tools-mcp@latest
How to use
cdp-tools-mcp is an MCP server that brings Chrome DevTools Protocol-powered debugging and browser automation to AI agents. It enables runtime debugging features such as breakpoints, variable inspection, console and network monitoring, plus browser automation with element discovery and interaction recording. The server also supports multi-agent workflows, allowing nested agents to manage their own browser tabs within the same Chrome instance, and it includes server management capabilities like port monitoring and auto-restart. To use it, start the MCP via npx, then connect your MCP client (e.g., Claude or another MCP client) using the provided command or the config snippet. You can add the server to Claude Desktop configurations or run via stdio transport, after which you’ll be able to issue debugging commands, replay recorded interactions, and manage multiple sessions without port conflicts.
How to install
Prerequisites:
- Node.js and npm installed on your machine
- Internet access to fetch packages from npm
Installation steps:
- Clone the repository (optional if you’re installing from npm): git clone https://github.com/InDate/cdp-tools-mcp.git cd cdp-tools-mcp
- Install dependencies: npm install
- Build the project (if applicable): npm run build
- Start the MCP server: npm start
- Optional: run directly via npx (as shown in the README): npx cdp-tools-mcp@latest
If you’re integrating with Claude, you can also add the server to your Claude config as shown in the Quick Start example.
Additional notes
Tips and notes:
- The MCP supports cross-session and cross-tool coordination. Enable auto-restart if you want servers to recover automatically after failures.
- Configure port monitoring and blocking behavior to control how the LLM reacts to server issues.
- Use the provided config snippet to integrate with Claude Desktop or other MCP clients; this keeps command and args centralized.
- For best results, ensure your environment allows Chrome DevTools Protocol connections and that any required Docker or container capabilities are available if you plan to run Docker-related workflows.
- The repository emphasizes recording and replaying reproduction steps for automated verification, as well as multi-agent tab management for parallel debugging sessions.
Related MCP Servers
obsidian
Obsidian Knowledge-Management MCP (Model Context Protocol) server that enables AI agents and development tools to interact with an Obsidian vault. It provides a comprehensive suite of tools for reading, writing, searching, and managing notes, tags, and frontmatter, acting as a bridge to the Obsidian Local REST API plugin.
flyto-core
The open-source execution engine for AI agents. 412 modules, MCP-native, triggers, queue, versioning, metering.
mcp -langfuse
Model Context Protocol (MCP) Server for Langfuse Prompt Management. This server allows you to access and manage your Langfuse prompts through the Model Context Protocol.
grok-faf
First MCP server for Grok | FAST⚡️AF • URL-based AI context • Vercel-deployed
copilot-memory-store
Local JSON memory store for context engineering with GitHub Copilot and MCP clients. Includes CLI, MCP server, and custom VS Code agent.
warp-sql
🗄️ Model Context Protocol (MCP) server for SQL Server integration with Warp terminal. Execute queries, explore schemas, export data, and analyze performance with natural language commands.