Publishes Chrome DevTools MCP and official debugging Skills for browser inspection, runtime evidence, and coding-agent workflows.
The ChromeDevTools organization publishes tools around Chrome’s developer diagnostics, including chrome-devtools-mcp. The project connects coding agents to browser inspection and automation rather than supplying a general-purpose language model.
Chrome DevTools provides inspection of a running Chrome page; the MCP project exposes diagnostic tools to an agent. Network requests, performance traces, and runtime state answer different questions. The browser remains the source of measurements, while the agent combines those observations into hypotheses that can be checked.
Its repository includes the server, client setup, official Skills, and troubleshooting. Follow the configuration and enabled capabilities of the installed release; a server tool, a CLI path, and a usage Skill are related interfaces rather than separate publishers.
Choose diagnostics when the question is why a page failed or slowed down. Compare general browser automation when the task mainly requires navigation and form interaction.
Let a coding agent inspect live Chrome with console, network, performance, and page tools. Use the evidence to diagnose a particular failure rather than treating a screenshot as the whole investigation.
Compare Microsoft for Playwright MCP automation, Vercel Labs for terminal browser control, Browser MCP for extension access to existing Chrome, BrowserOS for a browser with external-agent MCP. Choose by the browser environment and task result you need.
A failed save can originate in the request, server response, or page handling. Collecting those observations together helps distinguish evidence from a plausible explanation.
