chrome-devtools-mcp
★ 54.0k
vs
open-codex-browser-use
★ 390
chrome-devtools-mcp vs open-codex-browser-use
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.; open-codex-browser-use: open-browser-use is a browser automation layer that is neutral across agent runtimes. It pairs a browser extension with a CLI, and can be integrated via JavaScript, Python, Go SDKs or CLI. It is an open-source alternative to Codex.app's Chrome Browser Use capability.
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.
open-codex-browser-useBrowser Automation · ★ 390
Automate browser tasks via agent
02
Side-by-Side Comparison
Field
chrome-devtools-mcpopen-codex-browser-useCategory
Browser Automation
Browser Automation
Stars
★ 54.0k
★ 390
License
Apache-2.0
MIT
Install Command
npx -y chrome-devtools-mcp@latest
brew tap iFurySt/open-browser-use && brew install open-browser-use
Updated
1d ago
1w ago
Open Source
Yes
Yes
Tags
Chrome DevTools, AI Assistant, Browser Automation
ai-agent, ai-agents, browser-automation
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.)
open-codex-browser-use01Browser automation layer
02Agent runtime neutral
03Multi-language SDKs (JS, Python, Go)
04CLI and browser extension
05MCP server support
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
open-codex-browser-use↳Automate browser tasks via agent
↳Retrieve and summarize web content
↳Integrate with code assistants like Codex and Claude Code
05
Best For
chrome-devtools-mcpMost PopularEssentialTrending
open-codex-browser-use—
FAQ
FAQ
What is the difference between chrome-devtools-mcp and open-codex-browser-use?
Both chrome-devtools-mcp and open-codex-browser-use are in the Browser Automation category. chrome-devtools-mcp has 54.0k stars, while open-codex-browser-use has 390 stars.
Which is better, chrome-devtools-mcp or open-codex-browser-use?
The best choice depends on your use case. Choose chrome-devtools-mcp if Automating browser interactions for testing or data extraction, and open-codex-browser-use if Automate browser tasks via agent.
Is chrome-devtools-mcp free or open source?
Yes, chrome-devtools-mcp is open source on GitHub (Apache-2.0).
Is open-codex-browser-use free or open source?
Yes, open-codex-browser-use 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.
→