chrome-devtools-mcp
| Version | 2026.144.1443 |
| Repo | superproject |
Chrome DevTools MCP server exposes browser-automation tools over Streamable HTTP on port 9224 Installs the chrome-devtools-mcp Node.js server (npm) and the Python mcp-proxy bridge (pixi). A supervisord service runs mcp-proxy, which bridges the stdio MCP server to Streamable HTTP on port 9224 and points chrome-devtools-mcp at Chrome’s DevTools Protocol on 127.0.0.1:9222. Both binaries are on disk at build time; once Chrome is reachable the live endpoint answers MCP pings and advertises the browser-automation tool catalog (navigate_page, take_screenshot, …).
Services
Section titled “Services”chrome-devtools-mcp
Acceptance plan
Section titled “Acceptance plan”This candy’s plan: — the runnable spec charly check executes against a live deployment. check: steps are idempotent probes; run: steps change state.
| Intent | Step |
|---|---|
check |
the chrome-devtools-mcp server binary is installed under the npm global prefix |
check |
the mcp-proxy stdio-to-HTTP bridge binary is installed in the pixi env |
check |
the MCP endpoint answers a protocol ping on port 9224 |
check |
the advertised tool catalog includes the core browser-automation tools |
agent-check |
navigation and screenshot calls drive a live Chrome session via the DevTools Protocol |
check |
service=chrome-devtools-mcp |
check |
addr=127.0.0.1:${HOST_PORT:9224} |