chrome-devtools-mcp vs Cursor CLI
Both in the agentic & browser category. Side-by-side — pick the one that fits your stack tonight.
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.
Cursor's AI coding agent, in your terminal — no editor required.
- rating
- 4★
- tested
- —
- cost
- freemium
- install
- drop-in
- stars
- 0
- updated
- 4d ago
You're already on Claude Code and don't have Cursor — no reason to juggle two subscriptions.
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.
why it matters · Cursor CLI
If you're already paying for Cursor and don't want a second AI subscription for Claude Code, Cursor CLI gets you the 'agent in a terminal' experience on your existing plan. Multi-file edits, a `/debug` for tricky bugs, customizable slash commands. Less mature than Claude Code for autonomous work — fewer skills, weaker planning — but shipping updates every week. Good fallback or second opinion. Free tier exists; heavy use needs the Cursor subscription.