For AI agents: the index of this site is https://dejo.run/llms.txt, and every page is also served as markdown (add .md to its address, or send Accept: text/markdown).

dejo

Best browser MCP for Claude Code (2026, measured)

BlogBy Rohit Kashyap

I build Dejo, one of the tools below. I'll say where it loses, and every number has a link to the raw data. We haven't measured Claude in Chrome, agent-browser or Browser MCP, and I say so wherever they come up.

Short answer: there isn't one best browser MCP for Claude Code; there's a best one per job. For debugging a page, Chrome DevTools MCP. For tests and one-off tasks in a clean browser, Playwright MCP or Playwright CLI. For working in the Chrome you're already signed in to, Claude in Chrome. For website tasks you run again and again, Dejo, which learns a task once and then repeats it in one tool call.

if you want to…use
debug a page: console errors, network, performanceChrome DevTools MCP
write or run tests, or need Firefox or WebKitPlaywright MCP or Playwright CLI
have Claude act in your own signed-in Chrome while you watchClaude in Chrome (paid plan) or Browser MCP
repeat the same website task in new sessionsDejo
get past sites that block automated browsersnone did well; Playwright CLI got through 2 of the 6 blocked tasks in our test (six tasks on three sites; both wins on one site)
run a check from cron with no model at allDejo (dejo run ... --json)

What we measured

Two tests, both in Claude Code with Claude Sonnet 5 at medium effort, each run in a brand-new session.

The first test ran the same tasks ten times. Three multi-step tasks on well-known sites (count a GitHub repo's open issues; read an author's birth date on a quotes site; read a book's price after choosing a category), each run ten times, 90 sessions in total, with @playwright/mcp@0.0.80 and chrome-devtools-mcp@1.8.0. It was recorded on 5 September 2026, under the project's old name, and moved into the Dejo repository on 14 October 2026.

Read this table with one caveat. It was recorded before the 20 October fix to Dejo's test profile. The benchmark notes say: "Results recorded before 20 Oct 2026 ran Dejo in the developer's own browser profile." So on github.com Dejo saw the signed-in page, while Playwright MCP saw the signed-out one. The 19-task test further down doesn't have this problem.

30 sessions per toolright answerstool callstokenscosttime
Playwright MCP301998.7M$3.69960 s
Chrome DevTools MCP301497.1M$3.76684 s
Dejo30964.6M$1.65533 s

The first run tells a different story: Dejo averaged 9.7 calls and 415K tokens, the most of the three, because it does the task and saves it. Playwright MCP's first run averaged 242K and Chrome DevTools MCP's 226K. From the fourth run on, Dejo was two calls per session. Before that it wasn't always: on the books site, runs 2 and 3 took 7 and 10 calls. Raw data: benchmark-journeys10.json.

The second test used 19 tasks on lesser-known sites, the kind a model can't answer from memory: a college course catalog, the Debian package pages, the RFC Editor, a museum collection and others, with every right answer written down first. Recorded 21 to 23 October 2026, each run with its own empty profile:

per taskright answerstokens, averagetokens, median
Playwright MCP17 of 19409K257K
Playwright CLI18 of 19559K496K
Dejo, first run19 of 19251K216K
Dejo, every run after19 of 1989K82K

Chrome DevTools MCP and Claude in Chrome were not in this test. Raw data: benchmark-real-2026-10-21.json and the Dejo 23 October files.

Chrome DevTools MCP

Google's Chrome DevTools team makes it. It drives a Chrome and reads what DevTools reads: console messages, network requests, and performance traces with insights. The README now installs it in Claude Code as a plugin: /plugin marketplace add ChromeDevTools/chrome-devtools-mcp, then /plugin install chrome-devtools-mcp@chrome-devtools-plugins.

In our ten-run test it used fewer tokens than Playwright MCP (7.1M against 8.7M) and was quicker (684 against 960 seconds). In dollars it cost a little more ($3.76 against $3.69). It didn't remember anything between sessions: from the fourth run on it averaged 5 calls and 235K tokens per session, much like its first run. It's also the most upvoted browser answer in a big r/ClaudeAI thread about useful MCP servers ("chrome-devtools MCP with --autoConnect").

Pick it if you're debugging your own web app. More in Chrome DevTools MCP vs Playwright MCP.

Playwright MCP

Microsoft's MCP server. claude mcp add playwright npx @playwright/mcp@latest. It runs Chromium, Firefox or WebKit, headless if you like, and can emulate a phone with --device.

In our tests it was right 17 of 19 times on the hard sites and 30 of 30 on the easy ones. It used the most tokens in the ten-run test, and its run 10 cost no less than its run 1 (828K against 726K tokens, three sessions each). The current version, 0.0.84, lists 25 tools (22,121 bytes of definitions in every session) and, in my hand-driven run on 4 November, saved page snapshots to files instead of putting them in each click's reply, which should make it lighter than the 0.0.80 we benchmarked. We haven't measured that in Claude Code yet.

Pick it for tests and for anything that needs a clean browser or another engine.

Playwright CLI

The same Playwright actions as shell commands, plus a skill file: npm install -g @playwright/cli@latest, then playwright-cli install --skills. Its README says it's "the best fit" for coding agents because it doesn't load tool schemas or page outlines into the model.

In our 19-task test it used more tokens than Playwright MCP on 16 tasks and fewer on the 3 longest. It got one more answer right, and it was the only tool that got through any of the six blocked tasks (six tasks on three sites). It got through two of them, both on one site, at 1.2M and 1.7M tokens. The details are in Playwright MCP vs Playwright CLI vs memory.

Pick it if your agent is good with a shell, or you hit blocked sites.

Claude in Chrome

Anthropic's extension. Start Claude Code with claude --chrome, and Claude works in new tabs of your own Chrome, Edge or other Chromium browser, with all your sign-ins. From its docs: it runs "in a visible Chrome window", it "pauses and asks you to handle it manually" at a login page or captcha, it can record GIFs, it needs a Pro, Max, Ultra, Team or Enterprise plan, and it doesn't work with an API key, through Bedrock, Google Cloud or Foundry, or in WSL. The docs also say that turning it on by default "increases context usage".

We haven't measured it. In a Reddit thread comparing it with Playwright MCP, one user called it "still too slow for any real agentic browsing"; that's one opinion from December 2025.

Pick it when the task lives in your own signed-in browser and you're there. More in Playwright MCP vs Claude in Chrome.

Dejo

Ours. pip install dejo-mcp, playwright install chromium, then claude mcp add --scope user dejo -- dejo-mcp. Five tools (4,260 bytes of definitions). The first time, Claude does the task step by step and Dejo saves the steps with a check on each. After that, one dejo_run call repeats it in plain code with no model calls inside Dejo; when a site changes, only the step that broke is repaired. Since 0.4.0 it can also emulate a phone, record a video or trace, and drive a running Chrome over CDP.

Here's a real repeat from 4 November, in a fresh server process (no Claude session, the call sent from a script):

done: "price of the first Travel book" on books.toscrape.com (profile default), 4 steps replayed in 427 ms, no page reading.
price = £45.17

Where it's weak: the first run costs about the same as Playwright MCP's on a typical site (median 216K against 257K), and more on easy sites (415K against 242K in the ten-run test, which ran before the profile fix). A one-page lookup gains nothing. It drives Chrome or Chromium only. It was stopped on all six blocked tasks, like Playwright MCP.

Pick it for tasks you'll run again: a report every Monday, a price check every morning, a phone check after every deploy.

Not measured by us

Things a single run hides

Most "best browser MCP" lists test each tool once, if at all. Three things only show up when you go further:

  1. For Playwright MCP and Chrome DevTools MCP, run 10 cost as much as run 1 or more. Only Dejo got cheaper, and on one site it took until run 4. If you do a task daily, that's the number that matters.
  2. Sign-in: Claude in Chrome and Browser MCP use your browser's sessions; Playwright MCP, Chrome DevTools MCP and Dejo keep their own profile, so you sign in once in their window. I compared these in Can Claude log in to websites?.
  3. A changed site breaks a saved route. Dejo repairs the one step that moved; the others work the page out again from scratch, which costs a full run. See self-healing browser automation.

How we tested

Both Claude Code benchmarks are scripted, with raw JSON in the Dejo repository: benchmark_agents.py --journeys --runs 10 for the ten-run test and benchmark_learning.py --bench real for the 19 tasks. Tokens include cache reads and writes as Claude Code reports them; cost is Claude Code's list-price figure. Each session could use only the browser tool under test. The tool sizes and the replay above come from runs I did by hand on 4 November 2026 with Dejo 0.4.0 and Playwright MCP 0.0.84, no model involved.

What we didn't test: Claude in Chrome, agent-browser and Browser MCP at all; Chrome DevTools MCP on the 19 hard tasks; current tool versions inside Claude Code; other models. The full numbers are on the benchmark page.

Related reading: Dejo vs browser-use, Dejo vs Stagehand and Dejo vs agent-browser.

FAQ

What is the best browser MCP for Claude Code?

It depends on the job. Chrome DevTools MCP for debugging a page (console, network, performance traces). Playwright MCP or Playwright CLI for tests and one-off tasks in a clean browser. Claude in Chrome for work in your own signed-in Chrome. Dejo for website tasks you repeat, because it replays them in one call.

Can Claude Code control a web browser?

Yes. Claude Code has no browser of its own, but any browser MCP server or CLI gives it one. Add one with `claude mcp add`, or start Claude Code with `--chrome` to use Anthropic's Claude in Chrome extension.

Is there a Chrome MCP server?

Several. Chrome DevTools MCP is Google's official one. Claude in Chrome and Browser MCP work through an extension in your own Chrome. Playwright MCP, Dejo and agent-browser drive Chrome or Chromium too, and can attach to a running Chrome.

What are the best free MCP servers for Claude Code?

For the browser: Playwright MCP, Playwright CLI and Chrome DevTools MCP (all Apache 2.0) and Dejo (MIT) are free and open source. Claude in Chrome needs a paid Anthropic plan. With all of them you still pay for the model's tokens.

Which is better, Playwright MCP or Playwright CLI?

In our test of 19 real-site tasks in Claude Code, Playwright MCP averaged 409K tokens and 17 right answers, the CLI 559K and 18 right. The CLI was cheaper only on the three longest tasks. Microsoft recommends the CLI for coding agents.