browser-tools-mcp
BrowserTools MCP is a Chrome extension and Node server that lets AI coding assistants (like Cursor) monitor browser activity, run audits, and capture screenshots directly from your IDE. However, the project is explicitly marked as no longer active in its README.
Key facts
Objective fields from the source. Values we can't verify are shown as “Unknown” rather than guessed.
| Field | Value |
|---|---|
| Repository | AgentDeskAI/browser-tools-mcp |
| Owner | AgentDeskAI |
| Primary language | JavaScript |
| License | MIT — OSI-approved |
| Stars | 7.3k |
| Forks | 525 |
| Open issues | 33 |
| Latest release | v1.2.0 (2025-03-10) |
| Last updated | 2026-03-18 |
| Source | https://github.com/AgentDeskAI/browser-tools-mcp |
What browser-tools-mcp is
A three-part architecture (Chrome extension, Node middleware server, MCP server) that exposes browser monitoring, accessibility/SEO/performance audits via Lighthouse and Puppeteer, and console/DOM capture to MCP-compatible clients. Latest release v1.2.0 is recent (March 2025) but project status is dormant.
Get the browser-tools-mcp source
Clone the repository and explore it locally.
git clone https://github.com/AgentDeskAI/browser-tools-mcp.gitcd browser-tools-mcp# follow the project's README for install & configurationNeed it deployed, integrated, or customized instead? DEV.co ships production installs.
Best use cases
Implementation considerations
- Install three separate components: Chrome extension, local Node server (browser-tools-server), and MCP server (browser-tools-mcp) in IDE.
- Requires Chrome DevTools panel interaction and proper IDE configuration for MCP; troubleshooting may involve restarting browser and server.
- Headless Puppeteer instance stays active for 60 seconds after last audit, so consecutive audits are optimized but background resource footprint exists.
- No clear migration or support path given explicit project inactivity notice; fork or alternative should be identified before production deployment.
- Windows connectivity issues were reported and fixed in v1.2.0; verify compatibility with your development environment before rollout.
When to avoid it — and what to weigh
- You need active maintenance or community support — README explicitly states 'THIS PROJECT IS NO LONGER ACTIVE PLEASE USE A DIFFERENT SOLUTION FOR THIS.' No indication of replacement or migration path.
- You require enterprise-grade stability or SLA — Project shows 33 open issues and no active roadmap updates beyond the v1.2.0 release; risk of unresolved bugs in production.
- You cannot manage a three-component setup — Requires separate installation of Chrome extension, Node server, and MCP server plugin with manual configuration—complex for teams with limited DevOps capacity.
- You use browsers or IDEs outside Chrome + Cursor ecosystem — Limited to Chrome extensions and MCP-compatible IDEs (Cursor, Claude Desktop, Cline, Zed); not applicable to Firefox, Safari, or non-MCP editors.
License & commercial use
MIT License (MIT). Permissive open-source license allowing commercial use, modification, and distribution with attribution and no warranty. No restrictions on proprietary use.
MIT permits commercial deployment without explicit permission. However, given the project's stated inactivity status, use at your own risk in production. Recommend forking or adopting a maintained alternative before committing commercial revenue to this tool.
DEV.co evaluation signals
Editorial assessment — not user reviews. Directional, with an explicit confidence level.
| Signal | Assessment |
|---|---|
| Maintenance | Stale |
| Documentation | Adequate |
| License clarity | Clear |
| Deployment complexity | High |
| DEV.co fit | Possible |
| Assessment confidence | High |
Chrome extension captures console logs, network activity, DOM, and screenshots; ensure sensitive credentials, tokens, or PII are not logged in console or stored in DOM during audits. Local Node server acts as middleware—verify it does not persist audit data insecurely. No mention of code signing, CSP, or security audit for extension. Headless Puppeteer instance executes in local environment; risk depends on malicious page input, though limited scope.
Alternatives to consider
Claude for VS Code / Cline
Native MCP support in Cursor alternatives; simpler single-client integration without separate server component. Supported by Anthropic directly.
Lighthouse CI (open-source or npm package)
Standalone, actively maintained performance/accessibility audit tool; no IDE integration but scriptable in CI/CD and no browser extension required.
Puppeteer + custom MCP wrapper
Build your own audit server on Puppeteer without third-party extension; more control, active Puppeteer maintenance, full customization for your IDE.
Build on browser-tools-mcp with DEV.co software developers
This project is no longer active. Before using in production, review alternatives like Cline, Lighthouse CI, or a custom Puppeteer wrapper. Contact our team to discuss maintained solutions for AI-assisted web development.
Talk to DEV.coRelated open-source tools
Surfaced by semantic similarity across the DEV.co open-source index.
Related on DEV.co
Explore the category and the services that help you build with it.
browser-tools-mcp FAQ
Is this project still maintained?
What IDEs are supported?
Can I use this in production?
What is captured from the browser?
Custom software development services
From first prototype to production, DEV.co delivers software development services around tools like browser-tools-mcp. Our software development agency staffs experienced software developers and web developers for custom software development, web development, integrations, and ongoing support across mcp servers and beyond.
Ready to Evaluate BrowserTools MCP?
This project is no longer active. Before using in production, review alternatives like Cline, Lighthouse CI, or a custom Puppeteer wrapper. Contact our team to discuss maintained solutions for AI-assisted web development.