Side-by-side comparison of two Model Context Protocol servers — install paths, tools, quality signals, and directory engagement so you can pick the right one for Claude, Cursor, and other MCP clients.
In-browser debug bridge that injects into your running web app, so an agent can read the DOM, console logs and network requests, and click/fill/inspect the page. Runs inside the page (not an external CDP driver), so it works in any browser and inside Cypress/Playwright runs.
Browser MCP is a Model Context Provider (MCP) server that allows AI applications to control your browser
Quality signal
49/100 (Fair)
41/100 (Fair)
Install path
npx · high
Remote · high
Engagement
1 0 0 4
3 0 0 6,929
Tools
In-browser injection supporting any browser and frameworkIntercepts console, fetch, and XHR requestsExposes tools over MCP protocol via WebSocketAdapters for Vite, Next.js, Nuxt, SvelteKit, Remix, Webpack, Cypress, PlaywrightReal-time bidirectional control and inspection inside the page context
Local execution for low-latency browser automationUses existing browser profile to maintain logged-in sessionsStealth mode to avoid bot detection and CAPTCHAsPrivacy by keeping all browser activity on the local device
