Browser Tools MCP Server
Chrome browser data capture and analysis tools for AI-powered MCP applications.
Data last scanned today · Reviewed today
Overview
Browser Tools MCP Server facilitates integration between AI models and your Chrome browser via a companion Chrome extension. It provides features like automated screenshot pasting into Cursor, Lighthouse-based SEO and accessibility auditing, and debugging mode sequences to improve AI reasoning. The system utilizes a three-part setup requiring a specific Chrome extension and two separate local Node.js servers to bridge browser logs with your IDE. Recent updates include improved networking, host auto-discovery, and Windows connectivity fixes.
Our verdict
This server carries a high risk level with a security score of 47/100, primarily due to it being an unmaintained community project where the README explicitly states it is no longer active. Authentication and read-only mode security have not been reviewed, and the project has not received updates for over 128 days. Given these factors, developers should avoid using this server in favor of active, officially supported alternatives.
- Supports performance, accessibility, and SEO analysis via Lighthouse
- Provides automated screenshot pasting functionality for Cursor
- Zero direct dependencies reduce potential supply-chain surface area
- Project README explicitly labels the repository as no longer active
- Last commit occurred over 128 days ago
- Authentication methods remain unreviewed for security
Tools
| Tool | Description | Risk |
|---|---|---|
| runAccessibilityAudit | Ensures the page meets accessibility standards like WCAG. | low |
| runPerformanceAudit | Identifies performance bottlenecks and loading issues. | low |
| runSEOAudit | Evaluates how well the page is optimized for search engines. | low |
| runBestPracticesAudit | Checks for general best practices in web development. | low |
| runAuditMode | Runs all audits in a particular sequence. | low |
| runNextJSAudit | Checks for best practices and SEO improvements for NextJS applications | low |
| runDebuggerMode | Runs all debugging tools in a particular sequence | low |
Compatibility
| Client | Local | Docker | Remote | Read-only |
|---|---|---|---|---|
| ChatGPT | ||||
| Claude Desktop | ||||
| Cursor | ||||
| VS Code | ||||
| Windsurf |
Frequently asked questions
›What components are required to run this MCP server?
You must install the BrowserTools Chrome extension, the MCP server (@agentdeskai/browser-tools-mcp) in your IDE, and the local Node.js middleware server (browser-tools-server) in a terminal.
›How do I ensure the audit tools function correctly?
You must have an active browser tab, the BrowserTools extension enabled, and your Chrome DevTools panel open.
›How do I troubleshoot connectivity or performance issues?
Try closing all instances of Chrome, restarting the local browser-tools-server node process, and ensuring only one instance of the Chrome DevTools panel is open.
›How does the headless browser manage resources during audits?
The Puppeteer-driven headless browser instance remains active for 60 seconds after your last audit call to handle consecutive requests efficiently.
›Does this tool support specific framework optimizations?
Yes, it includes a dedicated NextJS audit mode that injects a specific prompt to identify and improve SEO for NextJS applications.
Alternatives
Changelog
- Fix
- Fix
- Improvedv1.0.0
2025-02-14
Badge
Maintain this server? Add the live badge to your README.