Chrome DevTools · 2026-11-11 · notable
Chrome DevTools MCP 1.13.0 — logpoints and network mocks for coding agents
In short
Chrome DevTools MCP 1.13.0 lets AI coding agents set logpoints in a live page and mock its network requests. The mocks can block a request, serve a local file or fetch from another URL. The release also ships a long list of fixes.
Chrome DevTools · 2026-11-11 · 2 sources checked
Chrome DevTools MCP 1.13.0 lets an agent add logging to a running page and fake its network responses, without editing the site's code.
What is it?
Chrome DevTools MCP 1.13.0 adds logpoints and network mocks to Google's official MCP server for Chrome. A logpoint prints a value at a chosen line of a page's script. A network mock changes what a page gets back when it makes a request. Both are tools a coding agent can call against a live browser.
How does it work?
The new set_logpoints tool is built on the DevTools BreakpointManager. It takes the full list of logpoints for one page, replaces the old list, and the logged values show up in list_console_messages. Logpoints stay through reloads and navigations. Network mocking adds mock_network and remove_network_mock: a mock matches a URL pattern and resource type, then aborts the request, answers with a local file, or fetches a replacement GET/HEAD URL on the server side. The mock tools stay hidden unless the server starts with --categoryNetworkMocks.
Why does it matter?
Agents that debug front-end bugs used to have two bad options: edit the code to add console.log calls, or guess. With logpoints the agent can watch values in the real page and remove the logging with one call. Network mocks let it test error states, slow or missing APIs, and staging back ends without changing the server.
Who is it for?
Coding-agent users, frontend developers, browser-automation teams
Try it
npx -y chrome-devtools-mcp@latest --categoryNetworkMocks