# Chrome DevTools MCP v1.12.0: what's new, verdict & setup Canonical: https://theagenticweekly.com/tools/chrome-devtools-mcp · Released: 2026-10-22 · Last verified: 2026-10-25 · Evidence: Tested (smoke test, 2026-10-25, no language model involved) · Vendor: Chrome DevTools team (Google) · Official site: https://github.com/ChromeDevTools/chrome-devtools-mcp > Chrome DevTools for coding agents. ## Verdict **Chrome DevTools for coding agents.** Good for: - Debugging and performance work in a real Chrome Skip if: - You want cross-browser test automation Tested. Tested 2026-10-25 (America/Chicago). Chrome DevTools MCP 1.12.0 exposed 32 tools and opened a page in headless Chrome in 136.6 ms median; our first navigate_page call was rejected for a missing pageId. Test environment: Linux x86_64 virtual machine (Debian 13), 8 vCPU, 15 GiB RAM, no GPU; no vendor account, login or API key. No language model was involved in this test, so it says nothing about any model, vendor-hosted or local. Not tested: Remote (HTTP) transport, authentication and concurrent clients: only local stdio with one client was measured; Large payloads: calls used tiny inputs, so these latencies are protocol and process overhead, not throughput; Anything about answer quality: no model was involved in the latency numbers; These are single smoke-test runs; it is not a benchmark. The machine was shared with other jobs; Performance traces, network and console inspection, emulation: only page creation was timed. These are smoke tests, not a benchmark. Full log: /tests/chrome-devtools-mcp. Test scope: - Kind and date: smoke test, 2026-10-25 (America/Chicago). Not a benchmark. - What we ran: Chrome DevTools MCP 1.12.0 exposed 32 tools and opened a page in headless Chrome in 136.6 ms median; our first navigate_page call was rejected for a missing pageId. - Model used: None; no language model was involved - Environment: Linux x86_64 virtual machine (Debian 13), 8 vCPU, 15 GiB RAM, no GPU; no vendor account, login or API key - Not tested: Remote (HTTP) transport, authentication and concurrent clients: only local stdio with one client was measured; Large payloads: calls used tiny inputs, so these latencies are protocol and process overhead, not throughput; Anything about answer quality: no model was involved in the latency numbers; These are single smoke-test runs; it is not a benchmark. The machine was shared with other jobs; Performance traces, network and console inspection, emulation: only page creation was timed. Full test log (commands, versions, raw output): [Chrome DevTools MCP chrome_devtools 1.12.0: our test log](https://theagenticweekly.com/tests/chrome-devtools-mcp) Pricing: Official page, dated. Open-source server; the service it connects to may have its own costs. (checked 2026-10-25) ## Best for - [Best AI tool for MCP servers](https://theagenticweekly.com/best/mcp-servers) (#-): Chrome DevTools for coding agents. ## Key facts Chrome DevTools MCP exposes DevTools to coding agents. It is Apache-2.0 licensed and v1.12.0 was released Oct 22, 2026. - License: Apache-2.0 (per GitHub) - Platforms: Node.js with Chrome - Pricing model: Free and open source - Free tier: Free - Paid plans: None listed - GitHub: ChromeDevTools/chrome-devtools-mcp: 54,146 stars on 2026-10-25, last push 2026-10-25 - Latest release we saw: v1.12.0, 2026-10-22 - How to start: Follow the README to register the server with your MCP client. - v1.12.0 (2026-10-22): the newest release listed on the official page or repository when we read it on 2026-10-25. ## How to set it up: Get started with Chrome DevTools MCP These steps come from the vendor's own pages as read on 2026-10-25. We ran Chrome DevTools MCP on 2026-10-25; the test log lists what was and was not covered. 1. **Get access.** Follow the README to register the server with your MCP client. 2. **Check the limits and costs first.** Free. Open-source server; the service it connects to may have its own costs. ## Pros and cons Pros: - Apache-2.0 - Active releases Cons: - Chrome-focused - Our test was one small task on a local 3B model; it does not show behaviour with hosted models or larger jobs ## Alternatives - [Playwright MCP](https://theagenticweekly.com/tools/playwright-mcp): Microsoft's MCP server that lets agents drive a browser with Playwright. - [Browser Use](https://theagenticweekly.com/tools/browser-use): Open-source library that lets AI agents drive a browser, with a pay-as-you-go cloud browser starting at $0.02 an hour. - [GitHub MCP Server](https://theagenticweekly.com/tools/github-mcp-server): GitHub's official MCP server for repos, issues and pull requests. - [Figma MCP server](https://theagenticweekly.com/tools/figma-mcp): Figma's own MCP server that gives coding agents access to design files. - [Firecrawl](https://theagenticweekly.com/tools/firecrawl): Web data API: search, scrape and crawl for AI agents. - [MCP reference servers](https://theagenticweekly.com/tools/mcp-servers): The MCP project's collection of reference servers. - [Context7](https://theagenticweekly.com/tools/context7): Up-to-date, version-specific library docs served to coding agents. - [MCP Inspector](https://theagenticweekly.com/tools/mcp-inspector): Official tool for exploring and testing MCP servers, with a web UI and a CLI. - [Supabase MCP](https://theagenticweekly.com/tools/supabase-mcp): Connect Supabase projects to AI assistants. - [Sentry MCP](https://theagenticweekly.com/tools/sentry-mcp): Sentry's agentic tooling and MCP server for errors and traces. - [Notion MCP Server](https://theagenticweekly.com/tools/notion-mcp): Official Notion MCP server for reading and editing workspace content. ## FAQ ### What is Chrome DevTools MCP? Chrome DevTools MCP exposes DevTools to coding agents. It is Apache-2.0 licensed and v1.12.0 was released Oct 22, 2026. ### Is Chrome DevTools MCP free? Free. Open-source server; the service it connects to may have its own costs. Checked 2026-10-25; prices change, so confirm on the vendor's page. ### What license is Chrome DevTools MCP under? Its license: Apache-2.0 (per GitHub). Read from the project's own pages on 2026-10-25. ## Sources - [Chrome DevTools MCP repository (GitHub)](https://github.com/ChromeDevTools/chrome-devtools-mcp) (fetched 2026-10-25) ## How to cite Agentic Weekly, "Chrome DevTools MCP v1.12.0: what's new, verdict & setup", last updated 2026-10-25, https://theagenticweekly.com/tools/chrome-devtools-mcp Keep the Reported or Tested label when you quote the verdict.