Oya vs Chrome DevTools MCP: debugging local pages or running agent workflows.
Both connect Claude Code, Codex, Cursor and other MCP clients to a real browser. Compare whether you need Chrome DevTools inspection during development or isolated, repeatable browser automation with credential and audit controls.
Criteria from the comparison below.
Separate frontend debugging from signed-in automation.
Chrome DevTools MCP is built to let a coding agent inspect your own app through DevTools. Oya is built to let agents complete web tasks in a dedicated tab, keep credentials sealed and replay finished workflows with no model.
Review data exposure, telemetry and repeatability.
Check what browser data reaches the MCP client, whether telemetry or external performance APIs are active by default, and how you will rerun a finished workflow in production.
Check the published differences.
The table below uses the linked vendor pages and their stated review date. “Not stated” means the pages reviewed did not say; it does not establish that a capability is absent.
| Oya | Chrome DevTools MCP | |
|---|---|---|
| How coding agents connect | One-click Connect adds oya-browser to Claude Code, Codex, Cursor or VS Code over MCP; cloud MCP also available | npx -y chrome-devtools-mcp@latest over MCP (Node LTS + Google Chrome stable); also ships chrome-devtools CLI and agent skills |
| Browser and runtime model | Desktop app (macOS, Windows), Oya Cloud, or self-hosted; agents drive real Chromium tabs | Puppeteer connected to Chrome DevTools with console, network, Lighthouse and performance trace inspection |
| Separate agent tab and live takeover | Each agent session gets its own tab while you keep yours; watch live, take over and hand back | Not stated |
| Replays a finished task with no model | Yes: playbooks, and the agent repairs only a step that moved | Not stated |
| Reusable Playwright code you own | Yes: every playbook is a readable Playwright module that runs on any Chromium browser over CDP | Not stated |
| Passwords and TOTP hidden from the model | Passwords and TOTP seeds are sealed and never shown to the model | Not stated |
| Published security and telemetry notes | Project host allowlists refuse off-list hosts; desktop app runs locally with optional cloud sync | README warns full browser and DevTools content is exposed to MCP clients; usage statistics on by default (--no-usage-statistics) and trace URLs may call Google CrUX (--no-performance-crux) |
| Cloud fleet and self-hosted edition | Oya Cloud and self-hosted community (free up to 5 browsers) or enterprise edition (Docker, ECS, GCP, Kubernetes) | Not stated |
| Audit trail of agent and person actions | Append-only and hash-chained; every read of ePHI audited; kept six years in HIPAA mode | Not stated |
| HIPAA compliance and signed BAA | Yes: HIPAA mode on Oya Cloud (BAA on request) or self-hosted in your own cloud | Not stated |
| Price and licence | Free desktop app (500 agent steps/mo); Oya Cloud 1 free browser hour, then $500/mo for 100 hours; source-available community edition | Free, open source (Apache-2.0) |
Choose Oya when
- Your agent signs in to real web apps and needs sealed passwords, TOTP handling and a separate tab you can take over.
- You want finished agent runs saved as Playwright playbooks that replay deterministically with no model.
- You need cloud execution, self-hosting, an append-only audit trail or HIPAA compliance with a BAA on Oya Cloud or the enterprise edition.
Choose Chrome DevTools MCP when
- Your coding agent is debugging a web app and needs Chrome DevTools console, network, Lighthouse or performance traces.
- You want an Apache-2.0 npm server (npx -y chrome-devtools-mcp@latest) wired straight into your existing Chrome stable install.
- You are working on non-sensitive local or staging sites where DevTools exposure and opt-out telemetry flags fit your policy.
Use each tool for the job it was built for.
Oya does not route browsers through Chrome DevTools MCP. Teams often keep Chrome DevTools MCP for local frontend profiling and use Oya when coding agents or production workflows need isolated tabs, sealed logins, replayable playbooks or regulated deployments.
Test the fit with your own work.
Use the comparison to shortlist an approach, then evaluate it against a representative workflow.
Sources
What this page says about other companies comes from their own public pages, read on 2026-11-20. Vendors change their pages; check the source before you rely on a cell.
Start with the browser task you were about to do yourself.
Download Oya BrowserQuestions
When should I use Oya instead of Chrome DevTools MCP?
Use Chrome DevTools MCP when your coding agent needs DevTools inspection such as console logs, network requests, Lighthouse audits or performance traces. Use Oya when the agent needs to work signed in across real websites with sealed passwords, live human takeover, repeatable Playwright playbooks, or cloud and self-hosted execution.
What privacy and telemetry notes does Chrome DevTools MCP publish?
Its README notes that full browser and DevTools content is exposed to MCP clients and advises against sharing sensitive or personal information. Usage statistics are enabled by default (disable with --no-usage-statistics), and performance tools may send trace URLs to the Google CrUX API unless --no-performance-crux is set.
Does Oya work with Puppeteer or Playwright?
Yes. Every Oya browser gives a CDP URL that Puppeteer or Playwright can connect to, and every finished Oya task saves as a readable Playwright playbook you own.
Can I use Oya locally for free?
Yes. The Oya desktop app for macOS and Windows is free with 500 agent steps a month, and one-click Connect adds oya-browser to Claude Code, Codex, Cursor or VS Code with no Oya account required.
Is Oya HIPAA compliant?
On Oya Cloud and the enterprise edition, yes: Oya is HIPAA compliant and we sign Business Associate Agreements (BAAs). The desktop app and community edition are not covered by the HIPAA offering.