home / mcp / browsertools mcp server
browser-tools-mcp
Configuration
View docs{
"mcpServers": {
"oenius-browser-tools-mcp": {
"command": "npx",
"args": [
"@agentdeskai/[email protected]"
]
}
}
}BrowserTools MCP provides a local MCP server that connects a Chrome extension to MCP-compatible AI clients, enabling browser monitoring, logging, and automated audits such as accessibility, performance, and SEO analysis. It runs entirely on your machine, storing logs locally and avoiding any third-party data transmission.
Set up the local MCP server and connect it with your MCP client to start monitoring and auditing your browser activity. After starting the server, open your browser’s developer tools and enable the BrowserTools extension. Logs, screenshots, and current DOM context will be available to your MCP client for analysis and tool usage.
Prerequisites you need before installation are Node.js and npm. Ensure Node.js is installed and available in your system path.
Install or run the local BrowserTools MCP server with the following command.
npx @agentdeskai/[email protected]The system consists of three core parts: a Chrome extension to capture browser data, a Node.js middleware server, and an MCP server that exposes standardized tools for AI clients. All logs are stored locally on your machine and are not sent to external services.
Key capabilities include monitoring console output, capturing network activity, taking screenshots, analyzing DOM elements, and performing audits for accessibility, performance, SEO, and web best practices. You can run individual audits or a sequence of audits through dedicated modes.
To keep your MCP client in sync, you may also update your MCP client template or IDE with the compatible BrowserTools MCP client version (1.2.0). You can download the latest Chrome extension corresponding to the 1.2.0 release and load it into Chrome.
Auditing and debugging tools are designed to run in sequence when you activate specific modes. The main audits include Accessibility, Performance, SEO, and Best Practices. There are specialized audits for Next.js applications and modes to run all audits or all debuggers in a predefined order.
The following audit types are supported: Accessibility, Performance, SEO, Best Practices, NextJS Audit, Audit Mode, NextJS Audits, and Debugger Mode. Each tool analyzes pages for compliance, speed, metadata, and development best practices, then reports structured results to your MCP client.
Examples of how you might describe or request audits in natural language are provided in the usage notes, such as asking for accessibility checks or sequencing multiple audits. Use your MCP client to trigger these audits and interpret the structured results returned by the server.
WCAG-focused checks for color contrast, alt text, keyboard navigation, ARIA attributes, and other accessibility factors.
Lighthouse-based analysis of render-blocking resources, DOM size, image optimization, and other performance factors.
Evaluation of metadata, headings, link structure, and other on-page SEO aspects with recommended improvements.
General web development best practices checks to improve reliability and security.
Prompts and checks tailored to Next.js applications to boost SEO and correctness.
Runs all audits in a predefined sequence, optionally including a Next.js audit when Next.js is detected.
Specialized audits for Next.js projects, covering app router and page router setups.
Executes a sequence of debugging tools to aid in diagnosing browser-related issues.