browser-tools-mcp MCP Server
AgentDeskAI/browser-tools-mcp
[](https://agentrank-ai.com/tool/AgentDeskAI--browser-tools-mcp/?utm_source=badge&utm_medium=readme&utm_campaign=agentrank_badge) Are you the maintainer of AgentDeskAI/browser-tools-mcp? Claim this listing →
Monitor browser logs directly from Cursor and other MCP compatible IDEs.
Add AgentRank to Claude Code Discover and compare tools like AgentDeskAI/browser-tools-mcp — your AI finds the right one automatically
Get API Access → claude mcp add agentrank -- npx -y agentrank-mcp-server Overview
AgentDeskAI/browser-tools-mcp is a TypeScript tool licensed under MIT. Monitor browser logs directly from Cursor and other MCP compatible IDEs. Topics: ai, anthropic, cursor, mcp, mcp-server.
Ranked #3264 out of 24842 indexed tools.
Has 7,327 GitHub stars.
Ecosystem
TypeScript MIT
aianthropiccursormcpmcp-server
Score Breakdown
Stars 15% 7,327
7,327 stars → well-known project
Freshness 25% 2mo ago
Last commit 2mo ago → moderate activity
Issue Health 25% 98%
167/171 issues closed → responsive maintainer
Contributors 10% 7
7 contributors → small team
Dependents 25% 0
No dependents → no downstream usage
npm Downloads N/A
PyPI Downloads N/A
Forks 534
Description Good
License MIT
Weights: Freshness 20% · Issue Health 20% · Dependents 22% · Stars 10% · Contributors 8% · How we score →
How to Improve
Description low impact
Freshness high impact
Dependents medium impact
Matched Queries
From the README
# BrowserTools MCP Give your AI coding agent eyes on the browser. BrowserTools MCP streams console output, network activity, screenshots and Lighthouse audits from **your real Chrome session** — the one already logged into your app — to any MCP-compatible client: Cursor, Claude Code, Windsurf, Cline, Zed, Gemini CLI, and others. > **Version 2.0 is a rewrite.** One process instead of three, no unauthenticated > local server, credentials scrubbed before they leave the browser, and a real > test suite. If you are coming from 1.x, read [MIGRATION.md](MIGRATION.md) — > **and upgrade, because 1.2.x has a critical vulnerability.** See > [SECURITY.md](SECURITY.md). --- ## Why this instead of a CDP-based server Tools like Chrome DevTools MCP and Playwright MCP drive a *fresh, automated* browser. That is the right choice for writing tests. It is the wrong choice for debugging the app you are actually looking at, because since Chrome 136 the browser refuses remote debugging on your default pRead full README on GitHub →
Get the weekly AgentRank digest
Top movers, new tools, ecosystem insights — straight to your inbox.