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

Playwright MCP vs Claude in Chrome: which to use

BlogBy Rohit Kashyap

I build Dejo, a third browser tool for agents, so keep that in mind. I measured Playwright MCP and Dejo myself. I have not measured Claude in Chrome; what I say about it comes from Anthropic's docs, read on 4 November 2026 and checked again on 10 November.

Short answer: Claude in Chrome is for working in your own browser, signed in, while you watch. Playwright MCP is for a browser of its own: tests, CI, headless runs, other browser engines. If the same task comes back every day, neither remembers it. Each new session reads the pages again.

if you want…use
Claude to act in the Chrome you're already signed in toClaude in Chrome
a clean browser for tests, headless or in CIPlaywright MCP
Firefox or WebKit (Safari's engine)Playwright MCP
an API key, Bedrock or Google Cloud setup, or WSLPlaywright MCP (Claude in Chrome doesn't run there, per its docs)
a GIF of what happenedClaude in Chrome has it built in
the same task again tomorrow for one tool callDejo, which can also drive your running Chrome over CDP

How they differ

Claude in ChromePlaywright MCP
made byAnthropicMicrosoft
whose browseryour Chrome, Edge or another Chromium browser, in new tabsits own browser; or yours with --extension or --cdp-endpoint
start itclaude --chrome, or /chrome → Enabled by defaultclaude mcp add playwright npx @playwright/mcp@latest
your sign-insalready theresign in once in its window (the profile persists), or --storage-state
headlessno, "browser actions run in a visible Chrome window"yes, --headless
browser enginesChromium-based onlyChromium, Firefox, WebKit
phone emulationnot mentioned in its docs--device "iPhone 15" or --mobile
recordingsGIFsvideo and traces with --caps devtools (adds 13 tools)
costneeds a Pro, Max, Ultra, Team or Enterprise planfree (Apache 2.0); you pay for the model
doesn't work withAPI keys, claude setup-token, Amazon Bedrock, Google Cloud, Microsoft Foundry, WSLnothing on this list
remembers a task between sessionsnono

The Claude in Chrome column is from its Claude Code docs page. The Playwright MCP column is from npx @playwright/mcp@0.0.84 --help and its README (the persistent profile), and the licence from the Playwright MCP entry in Dejo's docs/CAPABILITIES.md, which records each tool's LICENSE file.

Two lines from Anthropic's page are worth knowing before you choose. "When Claude encounters a login page or CAPTCHA, it pauses and asks you to handle it manually." And: "Enabling Chrome by default increases context usage since the browser tools and their instructions are always loaded."

What we measured for Playwright MCP

In our benchmark, 19 tasks on lesser-known websites, each in a brand-new Claude Code session (Claude Sonnet 5, medium effort, @playwright/mcp@0.0.80), Playwright MCP got 17 answers right and averaged 409K tokens, 40 seconds and $0.23 per task at list price. The median was 257K, because a few hard sites cost a lot: one college catalog task took 1,355K tokens and 23 tool calls.

In an earlier test, the same three tasks run ten times each in fresh Claude Code sessions, Playwright MCP's run 10 cost no less than its run 1 (828K tokens against 726K, three sessions each). From the fourth run on it averaged 6.4 calls and 283K tokens per session. Nothing it learned carried over, and Claude in Chrome works the same way: each session starts with no memory of the last. That test's results file was first committed on 14 October 2026, before the 20 October fix to Dejo's test profile (until then Dejo ran in the developer's own browser profile, per the benchmark notes). That affects Dejo's numbers in it, not Playwright MCP's. Raw data: benchmark-real-2026-10-21.json and benchmark-journeys10.json.

On 4 November I also drove the current Playwright MCP, 0.0.84, by hand through one short task on books.toscrape.com. The server lists 25 tools (22,121 bytes of definitions, loaded into every session). A click returned 432 to 511 bytes and saved the page outline to a file; the outlines for the three pages were 31,876, 21,318 and 10,174 bytes. More on this in Playwright MCP vs Playwright CLI vs memory.

What people say about each

From a Reddit thread that asks exactly this question (r/ClaudeCode, December 2025): one person found Claude in Chrome "still too slow for any real agentic browsing". Another said Playwright "was quite token heavy sometimes" and that Claude lost track of which tabs it had already opened. When someone asked whether Playwright is lighter than the extension, the reply was "no, its worse". These are opinions from one thread, not measurements, and both tools have changed since.

In another thread about using a logged-in Chrome, one reply makes a point that matters for any tool driving your own browser: "having a debug port open will trigger protection on many sites. So extension it is."

The part both of them leave out

Both tools treat every session as the first. If you ask Claude every morning to open the same dashboard and read the same number, it reads the same pages and makes the same choices every morning, and you pay for it every time.

That's the problem Dejo is built for. The first time, the agent does the task step by step, and Dejo saves the steps with a check on each. After that, one dejo_run call repeats it with no page reading and no model calls inside Dejo. In the 19-task benchmark, Dejo's first run averaged 251K tokens and every run after 89K.

Since 0.4.0, Dejo can also do this in a browser you already have running, which is the thing people like about Claude in Chrome. Set DEJO_CDP_URL=http://127.0.0.1:9222 and start Chrome with --remote-debugging-port=9222. I tried it on 4 November: a task learned earlier in Dejo's own browser replayed in a separate running Chromium in one call.

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

Dejo opened its own tab, used it, closed it and left the browser running with only the tab it had before.

Two honest catches. A debug port is exactly what that Reddit reply warns about: some sites react to it, and the extension route doesn't have that problem. And a Chrome with a debug port open can be driven by any program on your machine, so I'd use a separate Chrome profile for it, not the one with your bank.

Which one I'd pick

Dejo's weak spots, so you can rule it out fast: it drives Chrome or Chromium only, its first run on a task is not cheaper than Playwright MCP's on a typical site (median 216K against 257K tokens), and it doesn't help with a task you'll never repeat.

If signing in is the main question, I compared all three in Can Claude log in to websites?. The full numbers are on the benchmark page.

How we tested

Playwright MCP and Dejo in Claude Code: the 19-task benchmark recorded 21 to 23 October 2026 and the earlier 90-session test (recorded on 5 September 2026 under the project's old name, and moved into the Dejo repository on 14 October 2026), both with Claude Sonnet 5 at medium effort, scripts and raw JSON in the Dejo repository. Hand-driven runs on 4 November 2026: Playwright MCP 0.0.84 and Dejo 0.4.0 on a Linux cloud machine, a small Python client and no model, read-only on public practice pages.

Not tested by us: Claude in Chrome at all (it needs a paid plan and a desktop Chrome), and how many tokens it uses. If you have numbers from your own runs, I'd like to see them.

Related reading: can Claude log in to websites, Dejo vs Browser MCP and an AI agent with multiple signed-in user roles.

FAQ

Is Playwright MCP better than Claude in Chrome?

They do different jobs. Playwright MCP runs its own browser (Chromium, Firefox or WebKit, headless if you want), which suits tests and CI. Claude in Chrome works in your everyday Chrome with your sign-ins, in a visible window, which suits tasks on sites you're already logged in to.

Can Claude in Chrome use MCP?

Claude Code talks to the extension through an MCP server named claude-in-chrome; you see its tools under /mcp. You start it with `claude --chrome`. It needs a direct Anthropic plan and signing in with /login; an API key turns it off.

Can Claude Code use Playwright MCP?

Yes. `claude mcp add playwright npx @playwright/mcp@latest` adds it. It's free and open source; the model's tokens are what cost money.

Should you use Claude in Chrome?

Use it when the task needs your own signed-in browser and you're there to watch. Skip it for headless runs, CI, WSL, API-key setups, or Bedrock, Google Cloud and Foundry users, where its docs say it doesn't work.

Which one uses fewer tokens?

We measured Playwright MCP (about 409K tokens per task on 19 real-site tasks in Claude Code) but not Claude in Chrome. Its docs warn that keeping it enabled by default increases context use. Neither remembers a task between sessions.