chrome-devtools-mcp
★ 54.0k
vs
cloakbrowser-mcp
★ 169
chrome-devtools-mcp vs cloakbrowser-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.; cloakbrowser-mcp: cloakbrowser-mcp is a Model Context Protocol (MCP) server that enables browser automation using the Playwright MCP framework with the CloakBrowser Chromium binary. It provides Playwright-compatible tools through a thin bridge for npm and Docker users over stdio or Streamable HTTP.
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.
cloakbrowser-mcpBrowser Automation · ★ 169
Automating web interactions for AI agents
02
Side-by-Side Comparison
Field
Category
Browser Automation
Browser Automation
Stars
★ 54.0k
★ 169
License
Apache-2.0
MIT
Install Command
npx -y chrome-devtools-mcp@latest
docker pull swimmwatch/cloakbrowser-mcp:latest && docker run --rm --init -i swimmwatch/cloakbrowser-mcp:latest
Updated
1d ago
1d ago
Open Source
Yes
Yes
Tags
Chrome DevTools, AI Assistant, Browser Automation
Model Context Protocol, Browser Automation, Playwright
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.)
01Runs Playwright MCP with CloakBrowser Chromium
02Provides Playwright-compatible browser automation tools
03Supports npm and Docker deployment
04Thin bridge architecture for minimal overhead
05Flexible transport via stdio or Streamable HTTP
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 web interactions for AI agents
↳Web scraping and data extraction with a robust browser
↳Integrating browser control into Model Context Protocol applications
↳Developing automated testing suites for web applications
05
Best For
Most PopularEssentialTrending
—
FAQ
FAQ
What is the difference between chrome-devtools-mcp and cloakbrowser-mcp?
Both chrome-devtools-mcp and cloakbrowser-mcp are in the Browser Automation category. chrome-devtools-mcp has 54.0k stars, while cloakbrowser-mcp has 169 stars.
Which is better, chrome-devtools-mcp or cloakbrowser-mcp?
The best choice depends on your use case. Choose chrome-devtools-mcp if Automating browser interactions for testing or data extraction, and cloakbrowser-mcp if Automating web interactions for AI agents.
Is chrome-devtools-mcp free or open source?
Yes, chrome-devtools-mcp is open source on GitHub (Apache-2.0).
Is cloakbrowser-mcp free or open source?
Yes, cloakbrowser-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.
→