Browser Tools MCP
About
An MCP server that lets you monitor browser logs directly from Cursor and other MCP-compatible IDEs. Captures real-time console logs, network requests, and page errors — giving AI agents runtime debugging info while you code.
Our Verdict
Browser Tools MCP brings browser capabilities to the MCP ecosystem. Its GitHub popularity reflects community trust, and the standardized protocol ensures broad compatibility across AI clients.
Pricing
Use Cases
- Integrating browser capabilities into AI agent workflows
- Building custom AI-powered tools with Browser Tools MCP
- Enhancing AI agent functionality with standardized MCP access
Pros
- Browser Tools MCP provides standardized MCP protocol access
- Open source with 7,276 GitHub stars
- Active development and community support
Cons
- Requires MCP-compatible client (Claude, Cursor, etc.)
- Setup complexity varies by client
- Some features may depend on client capabilities
Installation
npx -y @agentdeskai/browser-tools-mcpFrequently Asked Questions
How is Browser Tools different from Browser MCP?
Browser Tools focuses on 'monitoring' rather than 'controlling': it doesn't manipulate the browser, but displays real-time console logs, network requests, and page errors directly in your IDE — giving AI agents debugging info while you code. Browser MCP controls the browser to perform actions. They complement each other.
How do I install Browser Tools?
Run npx -y @agentdeskai/browser-tools-mcp to start. Register it in Claude Code with claude mcp add browser-tools -- npx -y @agentdeskai/browser-tools-mcp, or paste into Cursor's MCP settings. You'll also need to install the browser extension for log capture.
Is Browser Tools free?
Completely free and open source with an active community. Both the MCP server and browser extension are free to use, no API key needed, and all data is processed locally.