Chrome DevTools MCP
Ranked 3 of 21 MCP servers by recommenders
Lets AI coding agents inspect, debug and test pages in Chrome, including already open sessions. Common caveat: it can flood the agent's context with large amounts of page data, using many tokens.
Lets AI coding agents inspect, debug and test pages in Chrome, including already open sessions. Common caveat: it can flood the agent's context with large amounts of page data, using many tokens.
58 people gave an opinion
- recommend it
- 36
- criticize it
- 22
- approval share
- 62%
Recommended in 9 of 13 months
- November 2025: recommended
- December 2025: recommended
- January 2026: recommended
- February 2026: recommended
- March 2026: recommended
- April 2026: recommended
- May 2026: not recommended
- June 2026: not recommended
- July 2026: recommended
- August 2026: not recommended
- September 2026: recommended
- October 2026: recommended
- November 2026: not recommended (month in progress)
Why it doesn’t carry the badge
- 36 people recommend itNeeds 10 or more, met.
- 1.6 recommenders for every criticNeeds 2 to 1 or better, not met.
- Recommended in 9 of 13 monthsNeeds 4 or more, met.
The same three rules apply to every product, and the badge can’t be bought. How the badge works
What people say about it
The reasons people give, with the number of comments that give each one. Open a reason to read what they said.
Why people recommend it
Each mark is one comment
Lets AI agents see and debug pages
“I rely heavily on chrome dev tool mcp and inbuilt diagnostics so ai can "see" how the page is laid out without actually seeing it.”
Comment from 21 Feb 2026 in “Ask HN: How do you employ LLMs for UI development?” “the LLM can inspect the behaviour using the chrome dev tools MCP and check its work much more effectively”
Comment from 7 Nov 2025 in “Dead Framework Theory” “it's chrome devtools. I get Claude Code to test in the browser, which makes a huge difference”
Comment from 18 Dec 2025 in “Skills for organizations, partners, the ecosystem” - Comment from 2 Dec 2025 in “Apple Releases Open Weights Video Model”
- Comment from 19 Feb 2026 in “Ask HN: How do you employ LLMs for UI development?”
Connects to existing browser sessions
“providing a direct bridge to active DevTools sessions is something a standard headless CLI can't replicate easily”
Comment from 16 Mar 2026 in “Let your Coding Agent debug the browser session with Chrome DevTools MCP” “The big upside of the MCP is that it connects to already open browser windows.”
Comment from 16 Mar 2026 in “Let your Coding Agent debug the browser session with Chrome DevTools MCP” “It goes to work by itself, uses your Chrome logged in session cookies, etc.”
Comment from 15 Mar 2026 in “Let your Coding Agent debug the browser session with Chrome DevTools MCP” - Comment from 16 Mar 2026 in “Let your Coding Agent debug the browser session with Chrome DevTools MCP”
- Comment from 15 Mar 2026 in “Let your Coding Agent debug the browser session with Chrome DevTools MCP”
Strong for web testing and development
“I've been using Chrome DevTools MCP a lot for this purpose and have been very happy with it.”
Comment from 14 Mar 2026 in “MCP Is Dead; Long Live MCP” “Chrome's DevTools MCP has been excellent in my experience for web development and testing.”
Comment from 20 Dec 2025 in “Claude in Chrome” “Chrome Devtools is similarly an extremely high value MCP for me.”
Comment from 16 Nov 2025 in “What if you don't need MCP at all?” - Comment from 30 Sep 2026 in “You said no MCP”
- Comment from 16 Mar 2026 in “Let your Coding Agent debug the browser session with Chrome DevTools MCP”
More reliable and capable than alternatives
“It's more reliable and token efficient than other devtools protocol MCPs i've tried.”
Comment from 15 Mar 2026 in “Let your Coding Agent debug the browser session with Chrome DevTools MCP” “I heard it's less detectable than playwright, and more robust against design changes”
Comment from 16 Mar 2026 in “Let your Coding Agent debug the browser session with Chrome DevTools MCP” “Lighter than Playwright, the loop is shorter, and easy to jam into Electron too.”
Comment from 24 Mar 2026 in “Show HN: ProofShot – Give AI coding agents eyes to verify the UI they build” - Comment from 15 Mar 2026 in “Let your Coding Agent debug the browser session with Chrome DevTools MCP”
- Comment from 3 Jul 2026 in “The Safari MCP server for web developers”
What people warn about
Each mark is one comment
Heavy token use and context bloat
“My main issue with Playwright (and chrome-devtools) is that they pollute the context with a massive amount of stuff.”
Comment from 3 Feb 2026 in “Two kinds of AI users are emerging. The gap between them is astonishing” “A single DOM snapshot can burn thousands of tokens through MCP's protocol envelope”
Comment from 16 Mar 2026 in “Let your Coding Agent debug the browser session with Chrome DevTools MCP” “MCP tool definitions load at session start and stay resident for the whole session”
Comment from 16 Mar 2026 in “Let your Coding Agent debug the browser session with Chrome DevTools MCP” - Comment from 21 Feb 2026 in “OpenBrowser-AI MCP”
- Comment from 15 Mar 2026 in “Let your Coding Agent debug the browser session with Chrome DevTools MCP”
Runs arbitrary JavaScript, security risk
“the specific risk is credentials in the browser context + any SEND capability reachable from the same entry points”
Comment from 16 Mar 2026 in “Let your Coding Agent debug the browser session with Chrome DevTools MCP” “three out of four expose evaluate_script or eval commands that let the agent run arbitrary JS”
Comment from 16 Mar 2026 in “The Webpage Has Instructions. The Agent Has Your Credentials” “less discriminating and is only as secure as a browser sandbox with full JS access”
Comment from 28 Aug 2026 in “AI Agent Has Root” Takes over browser, fails simple tasks
“It takes over your entire browser to center a div... and then fails to do so?”
Comment from 16 Mar 2026 in “Let your Coding Agent debug the browser session with Chrome DevTools MCP” “in their demo video where they center an element it ends up off-center”
Comment from 15 Mar 2026 in “Let your Coding Agent debug the browser session with Chrome DevTools MCP” Trouble connecting to open sessions
“It doesn't seem to work, tried the -u flag with the default address and it just couldn't connect to the existing chrome instance.”
Comment from 16 Mar 2026 in “Let your Coding Agent debug the browser session with Chrome DevTools MCP” “session sharing is a no-go for me as I need to run requests in parallel”
Comment from 24 Mar 2026 in “Show HN: ProofShot – Give AI coding agents eyes to verify the UI they build”
Other MCP servers people recommend
The four most recommended other MCP servers, with the same counts for each, so you can compare like for like. The tick on each bar marks the 2 to 1 line the badge needs.
| Product | Recommend | Criticize | Approval | Months | Owned | Badge |
|---|---|---|---|---|---|---|
| Playwright MCP | 40 | 22 | 65% | 11 | — | — |
| Context7 | 40 | 7 | 85% | 10 | — | Approved |
| Chrome DevTools MCPThis page | 36 | 22 | 62% | 9 | — | — |
| Serena MCP | 18 | 3 | 86% | 9 | — | Approved |
| Context Mode | 16 | 1 | 94% | 6 | — | Approved |
What people said
40 of the 64 comments that mention it, newest first. Each links to the original comment.
“the model/harness/tool combo of 3.8 flash extended/agy/chrome dev tools MCP is shockingly good”
“Best mcp I've seen is the chrome devtools one”
“less discriminating and is only as secure as a browser sandbox with full JS access”
“MCP is faster and more capable.”
“would highly recommend using the Chrome Devtools MCP to be able to attach the network requests”
“session sharing is a no-go for me as I need to run requests in parallel”
“you also should take a look at https://developer.chrome.com/blog/chrome-devtools-mcp”
“Lighter than Playwright, the loop is shorter, and easy to jam into Electron too.”
“It doesn't seem to work, tried the -u flag with the default address and it just couldn't connect to the existing chrome instance.”
“I heard it's less detectable than playwright, and more robust against design changes”
“The big upside of the MCP is that it connects to already open browser windows.”
“It takes over your entire browser to center a div... and then fails to do so?”
“Its easier to connect to existing sessions in your main browser.”
“three out of four expose evaluate_script or eval commands that let the agent run arbitrary JS”
“MCP tool definitions load at session start and stay resident for the whole session”
“I’m used to this excellent MCP server.”
“the specific risk is credentials in the browser context + any SEND capability reachable from the same entry points”
“A single DOM snapshot can burn thousands of tokens through MCP's protocol envelope”
“providing a direct bridge to active DevTools sessions is something a standard headless CLI can't replicate easily”
“It goes to work by itself, uses your Chrome logged in session cookies, etc.”
“in their demo video where they center an element it ends up off-center”
“it certainly has a more comprehensive feature set”
“this is a mega token guzzler in case you’re paying for your own tokens”
“It's more reliable and token efficient than other devtools protocol MCPs i've tried.”
“The session reuse angle is what makes this actually useful”
“I've been using Chrome DevTools MCP a lot for this purpose and have been very happy with it.”
“Each call dumps the entire page accessibility tree into the context window.”
“I rely heavily on chrome dev tool mcp and inbuilt diagnostics so ai can "see" how the page is laid out without actually seeing it.”
“I rely heavily on chrome dev tool mcp and inbuilt diagnostics so ai can "see" how the page is laid out”
“it can take screenshots and compare to expected design”
“Playwright MCP or Chrome DevTools MCP or agent-browser CLI or something similar”
“My main issue with Playwright (and chrome-devtools) is that they pollute the context with a massive amount of stuff.”
“nowadays you use something like mcp-browser-use, chrome-devtools-mcp with your llm of choice and write skills for that”
“I've used chrome devtools mcp successfully to do all kinds of advanced in browser tasks”
“Chrome's DevTools MCP has been excellent in my experience for web development and testing.”
“it's chrome devtools. I get Claude Code to test in the browser, which makes a huge difference”
“it's pretty easy to prompt them to fix something they can see”
“Chrome Devtools is similarly an extremely high value MCP for me.”
“Google approached this the right way. No, not with "ai mode", that sucks. With the Chrome dev tools MCP.”
“the LLM can inspect the behaviour using the chrome dev tools MCP and check its work much more effectively”
Counts come from 1,795,640 Hacker News comments, November 2025 to November 2026. How we count. Report a mistake.