Dowser vs Playwright MCP: your browser or a lab browser?
2 September 2026 · 6 min read · by Akhil Gorantala
Playwright MCP is Microsoft's open-source MCP server around the Playwright engine, and it deserves its popularity. If you are choosing between it and Dowser, you are really choosing between two different jobs, and it is worth being precise about which one you have.
What Playwright MCP actually is
It launches a fresh browser the agent fully controls, and exposes tools for navigation, accessibility-tree snapshots, clicks, form filling and screenshots. Fresh browser is the key phrase: no cookies, no sessions, no extensions, no you. That is exactly right for tests and repeatable jobs, where a clean environment is a feature.
Where it hurts
- Token burn. The model acts by reading page snapshots, and real-world pages produce huge ones. Comparisons of Playwright's own tooling put a typical MCP-driven task around 114,000 tokens versus about 27,000 for a CLI approach to the same task. That is per task, every time.
- No logins. The lab browser starts logged out of everything. Anything behind your Gmail, your dashboards, your carts means scripting credentials into automation, which is exactly where most people stop.
- Latency. Every action waits on a model round-trip to interpret the snapshot.
What Dowser does differently
Dowser lives in the browser you already use, as an extension paired with a local MCP server. Your assistant asks for "the add to cart button" and a local ranker resolves it against the page's accessibility tree and DOM in a few milliseconds, with no model call and no page content leaving your machine. Your logins are just there, because it is your browser. You watch every action happen with a visible cursor, and moving your mouse pauses it instantly.
Side by side
| Per action | Playwright MCP | Dowser |
|---|---|---|
| Browser | Fresh lab browser it launches | The one you already use |
| Logins and sessions | None, starts clean | Yours, already there |
| Element finding | Model reads a page snapshot | Local ranker, no model call |
| Latency per action | A model round-trip | Single-digit milliseconds |
| Token cost per action | A page snapshot in context | One short tool call |
| Engines | Chromium, Firefox, WebKit | Chromium-based only |
| Best at | CI, tests, repeatable jobs | Day-to-day tasks in your chair |
| Price | Free, open source | $29 once, 5-day trial |
The token math, worked through
Take the linked comparison's numbers at face value: roughly 114,000 tokens for a typical MCP-snapshot task. If your assistant touches the browser ten times a working day, that is over a million tokens a day spent on page snapshots, before any of the work you actually wanted the model to do. At typical frontier-model prices that is real money per month, but the quieter cost is context: those snapshots sit in the conversation window, crowding out your code and your instructions, which is why long browser-heavy sessions with snapshot tools get worse as they go. A Dowser action is a sentence-sized tool call; a hundred of them cost less context than one snapshot.
Setting them up
Playwright MCP: claude mcp add playwright -- npx @playwright/mcp@latest (or the equivalent in Cursor and friends), and it downloads its browser on first run.
Dowser: paste one line into your assistant: Set up the Dowser browser extension for me: fetch https://dowser.click/install.md and follow the steps in it, then confirm Dowser is connected. You press Add to Chrome once; the 5-day trial starts on its own.
Pick Playwright MCP when
- You are writing automated tests or CI jobs that must be reproducible.
- The task should run in a clean environment, isolated from your real sessions.
- You need cross-engine coverage (Chromium, Firefox, WebKit).
Pick Dowser when
- The task lives in your day-to-day browser: your accounts, your tabs, your state.
- You care about speed and token cost, because you do this many times a day.
- You want the assistant you already use (Claude Code, Cursor, Codex, Gemini CLI) to do it, not a separate script.
Questions people ask
Can Playwright MCP use my existing Chrome profile? It can be pointed at a persistent profile, but that is fighting its design: the tool is built around clean, reproducible sessions, and mixing in your live profile gives up exactly the isolation it is good at.
Does Dowser replace my Playwright tests? No. Dowser has no test runner, no assertions and no CI story; it is for an assistant doing live tasks in your browser, not for a suite you run on every commit.
Is the token gap smaller with a cheaper model? The dollars shrink, the latency and the context crowding do not: the snapshot still has to be produced, shipped and read on every action, whatever model reads it.
Plenty of people run both: Playwright MCP in CI, Dowser in the chair. They are free and $29 once, respectively, so the experiment is cheap either way.
Keep Playwright MCP for CI and give the browser you actually sit in a faster pair of hands: Dowser is free for 5 days, then $29 once. Get Dowser.