Chrome DevTools (local) logo

Chrome DevTools (local)

Beta

Google's Chrome DevTools server attaches to a local Chrome for performance traces, network inspection and DOM queries.

  • Developer Tools
  • Local
Runs
On the developer's Mac
Launched with
npx
Platform
macOS
Publisher
Google

How it works

Every agent request passes through Ferentin policy before it reaches Chrome DevTools (local).

It runs on the developer's Mac and talks to the AI client over stdio, so no network gateway sees it. Developers launch it with npx -y chrome-devtools-mcp.

Ferentin's endpoint agent finds Chrome DevTools (local) in the MCP configuration of AI clients on managed Macs. An administrator adds it once from the local MCP catalog for every managed Mac that launches it this way. Each of its tools starts unvetted until it is approved. Ferentin records every tool call.

  1. AI agentAsks for something
  2. Ferentin policies
  3. Chrome DevTools (local) MCP serverRuns on the developer's Mac
  4. Governed resultChecked, logged, returned

About Chrome DevTools (local)

Google's Chrome DevTools server attaches to a local Chrome for performance traces, network inspection and DOM queries.

Frequently asked about Chrome DevTools (local)

How do I connect Chrome DevTools (local) to Ferentin?
Enroll your Macs with the Ferentin endpoint agent, then add Chrome DevTools (local) from the local MCP catalog in the Ferentin admin console. Every managed Mac that launches it the way the catalog names it is covered, and each of its tools starts unvetted until you approve it.
Is the Chrome DevTools (local) integration generally available?
The Chrome DevTools (local) integration is currently beta on Ferentin.