chrome-devtools-mcp
★ 54.0k
vs
openbrowser
★ 16
chrome-devtools-mcp vs openbrowser
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.; openbrowser: OpenBrowser provides robust browser infrastructure for AI agents, featuring isolated Chrome sessions, persistent profiles, and proxy routing. It enables multiple agents to share real Chrome browsers efficiently with remote API control and human login handoff capabilities.
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.
openbrowserBrowser Automation · ★ 16
Remote browser automation for distributed agents.
02
Side-by-Side Comparison
Field
chrome-devtools-mcpopenbrowserCategory
Browser Automation
Browser Automation
Stars
★ 54.0k
★ 16
License
Apache-2.0
MIT
Install Command
npx -y chrome-devtools-mcp@latest
git clone https://github.com/floomhq/openbrowser.git && cd openbrowser && python3 -m venv .venv && . .venv/bin/activate && pip install -e . && playwright install chromium && cp .env.example .env && cp config/identities.example.json config/identities.local.json
Updated
1d ago
3mo ago
Open Source
Yes
Yes
Tags
Chrome DevTools, AI Assistant, Browser Automation
Browser Automation, AI Agents, Chrome CDP
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.)
openbrowser01Browser pool with isolated Chrome slots.
02Persistent profiles for named identities.
03Proxy routing for identity-specific traffic.
04Remote API for browser control.
05Human authentication handoff.
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
openbrowser↳Remote browser automation for distributed agents.
↳Managing logged-in workflows with persistent identities.
↳Multi-agent collaboration without session conflicts.
↳Human-in-the-loop authentication for complex challenges.
↳Debugging and auditing browser automation.
05
Best For
chrome-devtools-mcpMost PopularEssentialTrending
openbrowser—
FAQ
FAQ
What is the difference between chrome-devtools-mcp and openbrowser?
Both chrome-devtools-mcp and openbrowser are in the Browser Automation category. chrome-devtools-mcp has 54.0k stars, while openbrowser has 16 stars.
Which is better, chrome-devtools-mcp or openbrowser?
The best choice depends on your use case. Choose chrome-devtools-mcp if Automating browser interactions for testing or data extraction, and openbrowser if Remote browser automation for distributed agents..
Is chrome-devtools-mcp free or open source?
Yes, chrome-devtools-mcp is open source on GitHub (Apache-2.0).
Is openbrowser free or open source?
Yes, openbrowser 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.
→