devtools-mcp

by stefanli

28 stars
450 downloads
Not rated
GitHub

About

A MCP server that provides Chrome DevTools Protocol access to LLMs

Details

Author
stefanli
GitHub stars
28
Downloads
450
Categories
Other

- Execute any CDP command through the cdp_command tool
- Automatic binary data handling with file path references
- Seamless integration with LLM-based clients
- Supports all Chrome DevTools Protocol methods

Start Chrome with remote debugging on port 9222, install dependencies with npm install, then add the server as a local MCP server (e.g., with Claude Code using claude mcp add). The server exposes a single cdp_command tool that accepts a CDP method and optional parameters, and automatically saves binary output (screenshots, PDFs) to the ./cdp-output/ directory.

devtools-mcp

A MCP server that provides Chrome DevTools Protocol access to LLMs.

- Execute any CDP command through the cdp_command tool
- Automatic binary data handling - large responses (screenshots, PDFs) are saved to files

Setup

1. Start Chrome with remote debugging:

/Applications/Google\ Chrome.app/Contents/MacOS/Google\ Chrome \
  --remote-debugging-port=9222 \
  --remote-debugging-address=127.0.0.1 \
  --user-data-dir=/tmp/chrome-debug \
  --no-first-run \
  --disable-default-apps

2. Install dependencies:

npm install

3. Add as local MCP server. E.g. with Claude Code:

claude mcp add devtools-server -- npx tsx ~/projects/devtools-mcp/src/index.ts

Usage

The server exposes a single cdp_command tool that accepts:

- method: Any CDP command (e.g., "Page.navigate", "Runtime.evaluate")
- params: JSON string of command parameters (optional)

Binary data (screenshots, etc.) is automatically saved to ./cdp-output/ with file path references returned instead of raw data.

No reviews yet — be the first

Sign in to leave a review

Use Google, GitHub, or an email account so ratings stay tied to real people.

Email sign in

No reviews posted yet.