@mcp-b/chrome-devtools-mcp is the DevTools bridge for coding-agent workflows. It lets an MCP client control Chrome through the Chrome DevTools Protocol and adds WebMCP integration so the same agent can discover and call tools registered on the page.
When to use this package
- You need browser automation, console inspection, traces, screenshots, or DOM access.
- You want an MCP server that can both debug Chrome and discover WebMCP tools.
- You are integrating with coding agents that already speak MCP over stdio.
When not to use this package
- You only need to forward site tools into a desktop client. Use
@mcp-b/webmcp-local-relay. - You are building a Chrome extension rather than a DevTools-based bridge. Use
@mcp-b/extension-toolsfor extension-side APIs.
Where it sits in the package graph
This package is adjacent to the browser runtime packages. It does not replace them. Instead, it reaches into a live browser session and can interact with pages that expose WebMCP tools.First step
Add the server to your MCP client config, then connect it to a Chrome instance. The reference page covers setup, tool groups, configuration, and the WebMCP integration surface.Related pages
Reference
Configuration, tool groups, DevTools behavior, and WebMCP integration details.
Use DevTools MCP
Run the bridge in practical debugging workflows.
Transports and bridges
Compare DevTools-based access to relay and transport-based access.
@mcp-b/global overview
Runtime setup for pages whose tools are discovered through DevTools.