Launch Chrome with remote debugging enabled: google-chrome --remote-debugging-port=9222 --no-first-run --no-default-browser-check
Install and start the Chrome DevTools MCP server: npx @chrome-devtools/mcp --port=9222
Register the MCP server in your agent or MCP client config pointing to its stdio or SSE endpoint
The server exposes CDP domain tools (Network, Runtime, DOM, Debugger) as MCP tools the LLM can call
Use the Runtime.evaluate tool to execute JavaScript in the page context and retrieve return values
Use the Network.enable + Network.responseReceived tools to stream network events to the agent for analysis
Known gotchas
The remote debugging port exposes full browser control with no authentication; never bind --remote-debugging-port to 0.0.0.0 in production or shared environments
CDP sessions are tied to a specific page target ID; if the LLM navigates or opens new tabs, the target ID changes and commands against the old ID will fail
The Chrome DevTools MCP server is a community/experimental project; verify the current npm package name and API surface against the repository before relying on it in production pipelines
Give your agent this knowledge — and 200+ more routes
One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp