AgentDeskAI/browser-tools-mcp
Monitor browser logs directly from Cursor and other MCP compatible IDEs.
BrowserTools MCP connects AI code editors with live browser data through the Model Context Protocol. Capture console logs, monitor network traffic, take screenshots, and run accessibility audits from inside Cursor, Cline, or any MCP-compatible IDE without switching tabs.
Best for
Our Review
BrowserTools MCP gave AI code editors direct visibility into browser console logs, network traffic, and page elements without leaving the IDE. Built by AgentDeskAI, it served 7,100+ developers with a Chrome extension and local MCP server pipeline. Note: the project maintainers have marked this as no longer active, but it remains a valuable reference for browser-aware MCP tooling in 2026.
What BrowserTools MCP Does
- •Console log capture Streams JavaScript console output, errors, and warnings directly into your code editor for real-time debugging context.
- •Network traffic monitoring Records XHR requests and responses from web pages so AI agents understand API behavior without manual inspection.
- •DOM element analysis Sends the currently selected DOM element to MCP clients, giving AI editors precise context about page structure.
- •Screenshot capture Automatically captures and sends browser screenshots to your IDE via WebSocket, eliminating manual copy-paste workflows.
- •Accessibility audits Runs WCAG-compliant accessibility checks covering color contrast, missing alt text, keyboard navigation traps, and ARIA attributes.
- •Performance audits Analyzes page performance using Lighthouse data to identify render-blocking resources, excessive DOM size, and unoptimized images.
- •SEO audits Evaluates on-page SEO factors including metadata, headings, and link structure with suggestions for improvement.
- •Intelligent log truncation Automatically removes cookies and sensitive headers, truncates duplicate objects, and manages token limits to stay within LLM context windows.
Getting Started
BrowserTools MCP requires three components: the Chrome extension (available from the v1.2.0 release), a local Node server running npx @agentdeskai/browser-tools-server@latest, and the MCP server config npx @agentdeskai/browser-tools-mcp@latest in your IDE. Works with Cursor, Cline, Zed, and Claude Desktop. All logs stay local on your machine -- nothing is sent to third-party services.
Limitations
The project is no longer actively maintained by AgentDeskAI, so expect no new features or bug fixes. Requires the Chrome extension -- no Firefox or Safari support. Only works with MCP-compatible IDEs, not standalone usage. Windows users may experience connectivity issues despite v1.2.0 improvements. No official Docker or serverless deployment option exists for team sharing.
Our Verdict
BrowserTools MCP was one of the first projects to bridge browser data with AI code editors via the Model Context Protocol. It earned 7,100+ GitHub stars by giving Cursor and Cline users real-time visibility into console output, network calls, and page elements. The project is now marked inactive by its maintainers, so evaluate alternatives if you need ongoing support.
For Developers, BrowserTools MCP provided immediate value during debugging sessions. Instead of switching between Chrome DevTools and your IDE, the MCP server fed console logs and network traffic directly into agent context. The audit suite -- covering accessibility, performance, and SEO -- let AI editors run Lighthouse analysis without leaving your editor.
For Vibe Builders building web apps with AI editors, the screenshot auto-paste feature saved friction during UI iteration cycles. You could describe a layout problem to your AI agent, and it would see the actual page state. The intelligent log sanitization (removing cookies, sensitive headers, and deduplicating objects) meant you did not accidentally leak credentials into LLM prompts.
Basic Users will find the three-component setup (Chrome extension plus Node server plus MCP config) more complex than a single-install extension. The installation requires terminal commands and IDE configuration files.
Skip if you need an actively maintained project. BrowserTools MCP maintainers have marked it inactive. For current browser-aware MCP alternatives, check browsermcp.io or the Firecrawl MCP server for web scraping needs.
Frequently Asked Questions
Is BrowserTools MCP still actively maintained?
No. The project maintainers at AgentDeskAI have marked BrowserTools MCP as no longer active. The last release was v1.2.0 in March 2025, with the final code push in March 2026. The repository remains available with 7,100+ stars, and the existing installation still functions, but expect no new features, bug fixes, or updates.
How do you install BrowserTools MCP in Cursor?
Install three components: the Chrome extension from the v1.2.0 GitHub release zip, the browser-tools-server via npx @agentdeskai/browser-tools-server@latest in a terminal window, and npx @agentdeskai/browser-tools-mcp@latest added to your Cursor MCP configuration. Open Chrome DevTools and the BrowserTools panel to verify the connection.
What AI editors work with BrowserTools MCP?
BrowserTools MCP supports any MCP-compatible client including Cursor, Cline, Zed, and Claude Desktop. The MCP server implements Anthropic Model Context Protocol, so any IDE that can run an MCP server can connect to the browser tools pipeline for real-time browser data.
Does BrowserTools MCP send data to external servers?
No. All browser logs, console output, and network traffic stay local on your machine. The Node.js server runs as local middleware between the Chrome extension and your MCP client. Cookies and sensitive headers are stripped before data reaches any LLM, ensuring no credentials leak to third-party services.
What audits does BrowserTools MCP support?
BrowserTools MCP includes five audit types: accessibility (WCAG compliance checks), performance (Lighthouse analysis), SEO (on-page optimization), best practices (web development standards), and NextJS-specific audits. The Audit Mode feature runs all checks in sequence, while Debugger Mode runs debugging tools together for comprehensive page analysis.
What is browser-tools-mcp?
BrowserTools MCP connects AI code editors with live browser data through the Model Context Protocol. Capture console logs, monitor network traffic, take screenshots, and run accessibility audits from inside Cursor, Cline, or any MCP-compatible IDE without switching tabs.
How do I install browser-tools-mcp?
Visit the GitHub repository at https://github.com/AgentDeskAI/browser-tools-mcp for installation instructions.
What license does browser-tools-mcp use?
browser-tools-mcp uses the MIT license.
What are alternatives to browser-tools-mcp?
Search My AI Guide for similar tools in this category.
Great for: Pro Vibe Builders
Skip if: You need something more beginner-friendly or guided
Open source & community-verified
MIT licensed — free to use in any project, no strings attached. 7,193 developers have starred this, meaning the community has reviewed and trusted it.
Reviewed by My AI Guide for relevance, quality, and active maintenance before listing.