chrome-devtools-mcp
★ 54.0k
vs
invisible_playwright_mcp
★ 876
chrome-devtools-mcp vs invisible_playwright_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.; invisible_playwright_mcp: This project provides an AI browser agent designed to bypass anti-bot systems, making it invisible to detection. It can be used either as a plugin for various AI assistants or as a standalone web UI for complex web automation tasks.
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.
invisible_playwright_mcpBrowser Automation · ★ 876
Automating dynamic web content retrieval
02
Side-by-Side Comparison
Field
Category
Browser Automation
Browser Automation
Stars
★ 54.0k
★ 876
License
Apache-2.0
MIT
Install Command
npx -y chrome-devtools-mcp@latest
curl -LsSf https://astral.sh/uv/install.sh | sh && source $HOME/.local/bin/env && uvx invisible-playwright-mcp
Updated
1d ago
2d ago
Open Source
Yes
Yes
Tags
Chrome DevTools, AI Assistant, Browser Automation
Browser Automation, Anti-Bot, 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.)
01Invisible to anti-bot systems
02Human-like web interaction (drives page like a person)
03Multiple usage modes (assistant plugin or standalone web UI)
04Extensive configuration options (proxy, model, profile, seed)
05LLM integration via OpenRouter
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 dynamic web content retrieval
↳Navigating complex websites and filling forms
↳Real-time price comparison and monitoring
↳General browser-based task automation
05
Best For
Most PopularEssentialTrending
—
FAQ
FAQ
What is the difference between chrome-devtools-mcp and invisible_playwright_mcp?
Both chrome-devtools-mcp and invisible_playwright_mcp are in the Browser Automation category. chrome-devtools-mcp has 54.0k stars, while invisible_playwright_mcp has 876 stars.
Which is better, chrome-devtools-mcp or invisible_playwright_mcp?
The best choice depends on your use case. Choose chrome-devtools-mcp if Automating browser interactions for testing or data extraction, and invisible_playwright_mcp if Automating dynamic web content retrieval.
Is chrome-devtools-mcp free or open source?
Yes, chrome-devtools-mcp is open source on GitHub (Apache-2.0).
Is invisible_playwright_mcp free or open source?
Yes, invisible_playwright_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.
→