chrome-devtools-mcp
★ 54.0k
vs
flowlens-mcp-server
★ 108
chrome-devtools-mcp vs flowlens-mcp-server
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.; flowlens-mcp-server: FlowLens MCP server allows coding agents to access full browser context from recorded flows. It enables in-depth debugging and regression testing without reproducing issues. Users can record browser flows with the Chrome extension and share them with their agent.
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.
flowlens-mcp-serverBrowser Automation · ★ 108
Report bugs with full context
02
Side-by-Side Comparison
Field
Category
Browser Automation
Browser Automation
Stars
★ 54.0k
★ 108
License
Apache-2.0
Apache-2.0
Install Command
npx -y chrome-devtools-mcp@latest
pipx install flowlens-mcp-server
Updated
1d ago
5mo ago
Open Source
Yes
Yes
Tags
Chrome DevTools, AI Assistant, Browser Automation
ai-agents, bug-reporter, chrome-extension
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.)
01Record and share browser flows with AI coding agents
02Full browser context (network, console, storage, DOM, screen recording)
03Debug without reproducing issues
04Generate Playwright test scripts from recorded flows
05Share flows with teammates for collaborative debugging
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
↳Report bugs with full context
↳Regression testing and auto test generation
↳Collaborate on flows via shareable links
05
Best For
Most PopularEssentialTrending
—
FAQ
FAQ
What is the difference between chrome-devtools-mcp and flowlens-mcp-server?
Both chrome-devtools-mcp and flowlens-mcp-server are in the Browser Automation category. chrome-devtools-mcp has 54.0k stars, while flowlens-mcp-server has 108 stars.
Which is better, chrome-devtools-mcp or flowlens-mcp-server?
The best choice depends on your use case. Choose chrome-devtools-mcp if Automating browser interactions for testing or data extraction, and flowlens-mcp-server if Report bugs with full context.
Is chrome-devtools-mcp free or open source?
Yes, chrome-devtools-mcp is open source on GitHub (Apache-2.0).
Is flowlens-mcp-server free or open source?
Yes, flowlens-mcp-server is open source on GitHub (Apache-2.0).
Cloud Infrastructure
AdDeploy on DigitalOcean
Host your MCP servers, Docker containers, and AI agents with $200 free credit over 60 days.
→