chrome-devtools-mcp
★ 54.0k
vs
oya-browser
★ 351
chrome-devtools-mcp vs oya-browser
chrome-devtools-mcp: chrome-devtools-mcp enables AI coding assistants like Gemini, Claude, and Copilot to interact with a live Chrome browser via the Model-Context-Protocol (MCP). It grants AI full access to Chrome DevTools for reliable automation, deep debugging, and detailed performance insights.; oya-browser: Oya Browser is a unique web automation solution where the automation engine is built directly into the browser, rather than relying on external debugging protocols, making agents appear more human and less prone to bot detection. It enables AI agents to interact with websites, remember logins, record and replay complex tasks, and offers robust self-hosting options for scalable deployments.
01
TL;DR
chrome-devtools-mcpBrowser Automation · ★ 54.0k
When to choose:
- You want an agent to record a Chrome performance trace and get insights from it; the README lists performance_start_trace, performance_stop_trace and performance_analyze_insight.
- You need to inspect network requests, console messages and screenshots of a page while debugging it.
- You want the agent to attach to a Chrome you already have running, using --browser-url, --ws-endpoint or --autoConnect (Chrome 144+).
When to skip:
- You need Firefox or Safari: the project is built on Chrome DevTools and targets Chrome.
- You want a general-purpose automation or test runner across browsers; Playwright MCP is the closer fit.
- You cannot run Node.js 20.19 or newer, which the README lists as a requirement.
oya-browserBrowser Automation · ★ 351
**Automating Repetitive Web Workflows**: Record and replay complex tasks like form filling, data entry, and multi-step processes on various websites without constant model intervention.
02
Side-by-Side Comparison
Field
chrome-devtools-mcpoya-browserCategory
Browser Automation
Browser Automation
Stars
★ 54.0k
★ 351
License
Apache-2.0
NOASSERTION
Install Command
npx -y chrome-devtools-mcp@latest
npm i @oya-ai/browser
Updated
1d ago
1d ago
Open Source
Yes
Yes
Tags
Chrome DevTools, AI Assistant, Browser Automation
Browser Automation, AI Agents, Web Scraping
03
Features
chrome-devtools-mcp01Get performance insights using Chrome DevTools
02Advanced browser debugging (network, screenshots, console)
03Reliable automation using Puppeteer
04Input automation (click, drag, fill, etc.)
05Navigation automation (new page, navigate, wait for, etc.)
oya-browser01**Built-in Automation**: Automation runs inside the browser process, avoiding common bot detection vectors.
02**Persistent Sessions**: Sign in once, and all subsequent browser instances maintain the logged-in session, including cookies and localStorage.
03**Task Replay (Playbooks)**: Record web interactions once and replay them reliably without requiring a model for subsequent runs, even with new inputs.
04**AI Agent Friendly**: Designed for seamless integration with AI agents as a skill, via SDK, or over MCP, allowing agents to control the browser directly.
05**Anti-Bot Stealth**: Achieves 0% CreepJS headless score and passes Bot.Sannysoft tests, making automated actions less likely to be flagged.
04
Use Cases
chrome-devtools-mcp↳Automating browser interactions for testing or data extraction
↳Debugging web applications by analyzing network requests and console messages
↳Analyzing website performance by recording traces and extracting insights
oya-browser↳**Automating Repetitive Web Workflows**: Record and replay complex tasks like form filling, data entry, and multi-step processes on various websites without constant model intervention.
↳**AI Agent Web Interaction**: Empowering AI agents (e.g., OpenClaw, Claude Code) to browse the web, retrieve information, and perform actions as a human user would.
↳**High-Stealth Web Scraping**: Performing web data extraction from sites with robust anti-bot measures, ensuring reliable access and reducing detection risks.
↳**Managed Browser Environments**: Providing pre-signed-in browser sessions for various tasks, eliminating the need to script complex login flows like Google SSO or Okta.
05
Best For
chrome-devtools-mcpMost PopularEssentialTrending
oya-browser—
FAQ
FAQ
What is the difference between chrome-devtools-mcp and oya-browser?
Both chrome-devtools-mcp and oya-browser are in the Browser Automation category. chrome-devtools-mcp has 54.0k stars, while oya-browser has 351 stars.
Which is better, chrome-devtools-mcp or oya-browser?
The best choice depends on your use case. Choose chrome-devtools-mcp if Automating browser interactions for testing or data extraction, and oya-browser if **Automating Repetitive Web Workflows**: Record and replay complex tasks like form filling, data entry, and multi-step processes on various websites without constant model intervention..
Is chrome-devtools-mcp free or open source?
Yes, chrome-devtools-mcp is open source on GitHub (Apache-2.0).
Is oya-browser free or open source?
Yes, oya-browser is open source on GitHub (NOASSERTION).
Cloud Infrastructure
AdDeploy on DigitalOcean
Host your MCP servers, Docker containers, and AI agents with $200 free credit over 60 days.
→