chrome-devtools-mcp
★ 54.0k
vs
mcp-browser-use
★ 62
chrome-devtools-mcp vs mcp-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.; mcp-browser-use: MCP Browser Use Server integrates the `browser-use` automation engine with Model Context Protocol (MCP) compatible clients like Claude Desktop. It enables AI agents to orchestrate browser sessions, navigate websites, interact with forms, and extract content through natural-language instructions.
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.
mcp-browser-useBrowser Automation · ★ 62
Automated web scraping and data extraction.
02
Side-by-Side Comparison
Field
Category
Browser Automation
Browser Automation
Stars
★ 54.0k
★ 62
License
Apache-2.0
MIT
Install Command
npx -y chrome-devtools-mcp@latest
git clone https://github.com/JovaniPink/mcp-browser-use.git && cd mcp-browser-use && uv sync
Updated
1d ago
1w ago
Open Source
Yes
Yes
Tags
Chrome DevTools, AI Assistant, Browser Automation
browser automation, web scraping, AI agent
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.)
01Automated browsing with natural language instructions.
02Enhanced agent lifecycle management with custom error handling and prompt capabilities.
03Centralized browser configuration via environment variables for persistent profiles and proxies.
04Seamless integration with FastMCP for tool registration and session cleanup.
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
↳Automated web scraping and data extraction.
↳Automating repetitive online tasks and workflows.
↳Interactive web research and content summarization driven by LLMs.
↳Testing web applications by simulating user interactions.
↳Monitoring website changes and triggering actions.
05
Best For
Most PopularEssentialTrending
—
FAQ
FAQ
What is the difference between chrome-devtools-mcp and mcp-browser-use?
Both chrome-devtools-mcp and mcp-browser-use are in the Browser Automation category. chrome-devtools-mcp has 54.0k stars, while mcp-browser-use has 62 stars.
Which is better, chrome-devtools-mcp or mcp-browser-use?
The best choice depends on your use case. Choose chrome-devtools-mcp if Automating browser interactions for testing or data extraction, and mcp-browser-use if Automated web scraping and data extraction..
Is chrome-devtools-mcp free or open source?
Yes, chrome-devtools-mcp is open source on GitHub (Apache-2.0).
Is mcp-browser-use free or open source?
Yes, mcp-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.
→