browser-harness vs chrome-devtools-mcp
Both in the agentic & browser category. Side-by-side — pick the one that fits your stack tonight.
The fastest way to let Claude drive your browser. Self-healing, works on any site.
- rating
- 5★
- tested
- ✓ loya-tested
- cost
- free
- install
- drop-in
- stars
- 4,697
- updated
- 5d ago
You don't need your agent to control a real browser.
Give your agent the same debug tools you use in Chrome's inspector.
- rating
- 4★
- tested
- ✓ loya-tested
- cost
- free
- install
- drop-in
- stars
- 36,664
- updated
- 4d ago
You never hit 'Inspect' in Chrome and don't care what's happening under the hood.
why it matters · browser-harness
Need Claude to log into something, scrape a page behind a paywall, fill out a form, or click through a real app? browser-harness spins up a real Chrome that Claude can control — screenshots, clicks, typing, iframes, popups, and it restarts itself if anything breaks. If you want your agent to actually do things on the web instead of just talking about them, this is the one. Free, open source.
why it matters · chrome-devtools-mcp
The Chrome DevTools panel — the thing you see when you right-click and hit Inspect — has network tabs, console logs, performance profilers, and memory tools. This plug exposes all of that to Claude. Your agent can watch network requests, read console errors, run Lighthouse audits, and take performance traces — then fix the bug directly. Built by the Google Chrome team. Pair it with Playwright for actions + DevTools for observation.