chrome-devtools-mcp
★ 54.0k
vs
neobrowser
★ 100
chrome-devtools-mcp vs neobrowser
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.; neobrowser: NeoBrowser enables AI models to control a real Chrome browser using existing logged-in sessions, effectively bypassing bot detection and login walls. It offers advanced stealth features and human-like interaction, ensuring genuine user behavior for robust web automation.
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.
neobrowserBrowser Automation · ★ 100
Automating web workflows that require authenticated sessions.
02
Side-by-Side Comparison
Field
Category
Browser Automation
Browser Automation
Stars
★ 54.0k
★ 100
License
Apache-2.0
MIT
Install Command
npx -y chrome-devtools-mcp@latest
curl -fsSL https://raw.githubusercontent.com/pitiflautico/neobrowser/main/install.sh | sh
Updated
1d ago
1mo ago
Open Source
Yes
Yes
Tags
Chrome DevTools, AI Assistant, Browser Automation
Browser Automation, Chrome Control, AI Agent Tool
03
Features
01Get 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.)
01Real-session browsing with existing Chrome profiles.
02Genuinely stealth-hardened to pass bot detection (e.g., bot.sannysoft).
03Bot-wall aware, detecting CAPTCHAs, login walls, and rate limits.
04Multi-source search (text, images, videos) that routes around walled sources.
05A rich set of 43 tools for comprehensive web interaction.
04
Use Cases
↳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
↳Automating web workflows that require authenticated sessions.
↳Performing data extraction from websites with strong bot detection.
↳Enabling AI agents to interact with web services as a human user.
↳Testing web applications under realistic conditions with persistent user profiles.
↳Overcoming interactive web challenges by detecting and reporting them to the AI.
05
Best For
Most PopularEssentialTrending
—
FAQ
FAQ
What is the difference between chrome-devtools-mcp and neobrowser?
Both chrome-devtools-mcp and neobrowser are in the Browser Automation category. chrome-devtools-mcp has 54.0k stars, while neobrowser has 100 stars.
Which is better, chrome-devtools-mcp or neobrowser?
The best choice depends on your use case. Choose chrome-devtools-mcp if Automating browser interactions for testing or data extraction, and neobrowser if Automating web workflows that require authenticated sessions..
Is chrome-devtools-mcp free or open source?
Yes, chrome-devtools-mcp is open source on GitHub (Apache-2.0).
Is neobrowser free or open source?
Yes, neobrowser is open source on GitHub (MIT).
Cloud Infrastructure
AdDeploy on DigitalOcean
Host your MCP servers, Docker containers, and AI agents with $200 free credit over 60 days.
→