chrome-devtools-mcp
★ 54.0k
vs
qa-use
★ 28
chrome-devtools-mcp vs qa-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.; qa-use: qa-use is a CLI tool for browser testing and E2E test management. It allows you to define tests in YAML, run them via command line, and integrate with CI/CD pipelines. It also provides interactive browser control, API access, and AI assistant plugins.
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.
qa-useBrowser Automation · ★ 28
End-to-end testing of web applications
02
Side-by-Side Comparison
Field
chrome-devtools-mcpqa-useCategory
Browser Automation
Browser Automation
Stars
★ 54.0k
★ 28
License
Apache-2.0
MIT
Install Command
npx -y chrome-devtools-mcp@latest
npm install -g @desplega.ai/qa-use
Updated
1d ago
3w ago
Open Source
Yes
Yes
Tags
Chrome DevTools, AI Assistant, Browser Automation
browser-automation, llm-code, mcp
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.)
qa-use01YAML-based test definition with a wide range of actions
02Interactive browser commands for debugging
03Live API access via OpenAPI specification
04CI/CD integration with GitHub Actions
05AI assistant integration via Claude Code plugin and MCP server
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
qa-use↳End-to-end testing of web applications
↳Automated browser testing in CI/CD pipelines
↳AI-assisted test generation and verification
05
Best For
chrome-devtools-mcpMost PopularEssentialTrending
qa-use—
FAQ
FAQ
What is the difference between chrome-devtools-mcp and qa-use?
Both chrome-devtools-mcp and qa-use are in the Browser Automation category. chrome-devtools-mcp has 54.0k stars, while qa-use has 28 stars.
Which is better, chrome-devtools-mcp or qa-use?
The best choice depends on your use case. Choose chrome-devtools-mcp if Automating browser interactions for testing or data extraction, and qa-use if End-to-end testing of web applications.
Is chrome-devtools-mcp free or open source?
Yes, chrome-devtools-mcp is open source on GitHub (Apache-2.0).
Is qa-use free or open source?
Yes, qa-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.
→