chrome-devtools-mcp
★ 54.0k
vs
real-browser-mcp
★ 57
chrome-devtools-mcp vs real-browser-mcp
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.; real-browser-mcp: Real Browser MCP bridges AI coding agents to your actual Chrome browser. It uses a Chrome extension and an MCP server to let agents see, interact with, and navigate your existing browser with all your sessions and cookies. No need to launch a separate headless browser; it works with your logged-in state.
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.
real-browser-mcpBrowser Automation · ★ 57
Verify code changes by seeing the actual browser result without re-logging
02
Side-by-Side Comparison
Field
chrome-devtools-mcpreal-browser-mcpCategory
Browser Automation
Browser Automation
Stars
★ 54.0k
★ 57
License
Apache-2.0
MIT
Install Command
npx -y chrome-devtools-mcp@latest
npx real-browser-mcp --setup cursor
Updated
1d ago
4d ago
Open Source
Yes
Yes
Tags
Chrome DevTools, AI Assistant, Browser Automation
ai, browser-automation, chrome-extension
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.)
real-browser-mcp01Uses your existing browser (Chrome) with all sessions and cookies
0218 tools for seeing, interacting, navigating, and debugging
03Works with any MCP-compatible AI client (Cursor, Claude, Windsurf, etc.)
04No data leaves your machine; everything stays local via WebSocket
05Supports multiple Chrome profiles by running separate server instances
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
real-browser-mcp↳Verify code changes by seeing the actual browser result without re-logging
↳Interact with web apps that require corporate SSO or complex login flows
↳Automate browser testing and debugging with AI assistance
05
Best For
chrome-devtools-mcpMost PopularEssentialTrending
real-browser-mcp—
FAQ
FAQ
What is the difference between chrome-devtools-mcp and real-browser-mcp?
Both chrome-devtools-mcp and real-browser-mcp are in the Browser Automation category. chrome-devtools-mcp has 54.0k stars, while real-browser-mcp has 57 stars.
Which is better, chrome-devtools-mcp or real-browser-mcp?
The best choice depends on your use case. Choose chrome-devtools-mcp if Automating browser interactions for testing or data extraction, and real-browser-mcp if Verify code changes by seeing the actual browser result without re-logging.
Is chrome-devtools-mcp free or open source?
Yes, chrome-devtools-mcp is open source on GitHub (Apache-2.0).
Is real-browser-mcp free or open source?
Yes, real-browser-mcp 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.
→