chrome-devtools-mcp
★ 54.0k
vs
webmcp-bridge
★ 28
chrome-devtools-mcp vs webmcp-bridge
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.; webmcp-bridge: webmcp-bridge provides a stable local bridge that allows MCP clients to call browser WebMCP tools. It uses native WebMCP when available and falls back to injected adapters for sites without native support, enabling reuse of logged-in browser sessions and human-AI collaboration.
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.
webmcp-bridgeBrowser Automation · ★ 28
Connect a local MCP client to a native WebMCP website
02
Side-by-Side Comparison
Field
chrome-devtools-mcpwebmcp-bridgeCategory
Browser Automation
Browser Automation
Stars
★ 54.0k
★ 28
License
Apache-2.0
MIT
Install Command
npx -y chrome-devtools-mcp@latest
npm install -g @webmcp-bridge/local-mcp
Updated
1d ago
6mo ago
Open Source
Yes
Yes
Tags
Chrome DevTools, AI Assistant, Browser Automation
ai-agent, browser-automation, browser-tools
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.)
webmcp-bridge01Stable local bridge connecting MCP clients to browser WebMCP
02Native WebMCP support with fallback to injected adapters
03Reuse existing authenticated browser sessions
04Support for headless and headed browser modes
05Human-AI collaboration on the same page
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
webmcp-bridge↳Connect a local MCP client to a native WebMCP website
↳Inject fallback adapters for sites without WebMCP
↳Collaborate with AI in the same browser session
05
Best For
chrome-devtools-mcpMost PopularEssentialTrending
webmcp-bridge—
FAQ
FAQ
What is the difference between chrome-devtools-mcp and webmcp-bridge?
Both chrome-devtools-mcp and webmcp-bridge are in the Browser Automation category. chrome-devtools-mcp has 54.0k stars, while webmcp-bridge has 28 stars.
Which is better, chrome-devtools-mcp or webmcp-bridge?
The best choice depends on your use case. Choose chrome-devtools-mcp if Automating browser interactions for testing or data extraction, and webmcp-bridge if Connect a local MCP client to a native WebMCP website.
Is chrome-devtools-mcp free or open source?
Yes, chrome-devtools-mcp is open source on GitHub (Apache-2.0).
Is webmcp-bridge free or open source?
Yes, webmcp-bridge 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.
→