Chrome DevTools
VerifiedGoogle · Dev Tools
5 agent-callable tools
Last updated September 16, 2026Drive a real Chrome instance from an agent: navigate, inspect the DOM, read console and network activity, and capture performance traces.
This is a first-party server: it is published by Google, so it tracks their own API rather than a community wrapper around it. It is a local server you run over stdio.
Connect it once to a BusinessMCP workspace and every AI you use — Claude, GPT, Gemini, and your coding agents — reaches it through one endpoint, alongside everything else you have connected. That is the difference between a directory entry and a working integration: you authorise once, not once per model.
Just say it in a thread
No configs, no docs. Once connected, these are the kinds of messages your agents act on.
"A chrome devtools tool exposed by the server — and give me the highlights."
"A chrome devtools tool exposed by the server for me, then post a summary in the thread."
"A chrome devtools tool exposed by the server and flag anything that needs my approval."
What teams use it for
- Give an agent read access to your Chrome DevTools data so it answers from the real thing instead of guesswork.
- Let a teammate ask for Chrome DevTools work in plain language rather than clicking through the UI.
- Combine Chrome DevTools with the rest of your stack in one agent thread, without switching tools.
Agent-callable tools
navigate_page
A Chrome DevTools tool exposed by the server.
take_snapshot
A Chrome DevTools tool exposed by the server.
list_console_messages
A Chrome DevTools tool exposed by the server.
list_network_requests
A Chrome DevTools tool exposed by the server.
performance_start_trace
A Chrome DevTools tool exposed by the server.
Your data stays yours
Credentials live in your vault. We route requests — we never store, log, or train on your data.
Works with every AI
Connect once — portable across Claude, GPT, Gemini, and every local agent you run.
Pairs well with
Best Dev Tools MCP servers
GitHub
GitHub
Repos, PRs, issues, and Actions — controllable from any agent thread.
Vercel
Vercel
Deployments, preview URLs, env vars, and logs as agent-callable tools.
Git
modelcontextprotocol
Git repository operations including status, diff, log, branch management, and commit history analysis.
Frequently asked questions
Is there an official Chrome DevTools MCP server?
Yes. Google publishes it as a local server you run yourself. We probed it on 2026-09-16 and it responded.
Do I need an API key?
You run it locally and supply credentials through your own environment, so nothing is pasted into a shared config.
Can I use it with something other than Claude?
Yes. MCP is an open protocol, so any client that speaks it can call this server. Connecting it through BusinessMCP exposes it to every model you have connected at once.
Keep exploring
Give your AI team the Chrome DevTools skill
Free forever plan, no credit card. Connected and working in under five minutes.
Add Chrome DevTools as a custom server