home / mcp / browsertools mcp server

BrowserTools MCP Server

Provides an MCP server that captures browser data via a Chrome extension for AI tools to analyze locally.

Installation

Add the following to your MCP client configuration file.

Configuration

{
  "mcpServers": {
    "weotzi-browser-tools-mcp": {
      "command": "npx",
      "args": [
        "@agentdeskai/[email protected]"
      ]
    }
  }
}

BrowserTools MCP provides a local MCP server that lets your AI tools interact with your browser data through a Chrome extension. It captures logs, screenshots, and DOM interactions on your machine and exposes standardized tools for MCP clients to perform audits, debugging, and analysis without sending data to external services.

How to use

You connect an MCP client to the BrowserTools MCP Server to monitor browser activity and run audits on the current page. With the server running locally, compatible MCP clients can trigger accessibility, performance, SEO, and best practices checks, as well as debugging and audit modes. Logs, screenshots, and current element data stay on your machine and are never sent to third parties.

To start, ensure you have a browser tab open and the BrowserTools extension enabled. From your MCP client, you can issue prompts like “Run an accessibility audit,” “Check page performance,” or “Enter audit mode.” The system will return structured results you can present in your IDE or editor. Use the Audit tools to identify issues quickly and apply suggested improvements directly to your workflow.

How to install

Prerequisites you need before installation: Node.js (and npm) must be installed on your system.

Install the MCP client component and start the local server using the commands below.

npx @agentdeskai/[email protected]
```

```
npx @agentdeskai/[email protected]

Configuration and usage notes

The server is designed to work with MCP-compatible clients such as Cursor or other editors. After starting the local server, open your browser and ensure the BrowserTools Chrome extension is active. Logs, screenshots, and the current element data will flow through the local node server to your MCP client.

Notes and troubleshooting

If you encounter connectivity issues between the extension, server, and MCP client, verify that you started the server with the correct version and that the extension is enabled in the browser. Restart the server if you changing configuration or updating to a new version.

Tools available for audits

The following audits are provided to evaluate and improve your pages. Each audit returns structured results that your MCP client can parse.

Security and data handling

All logs and captured data are stored locally on your machine. No logs are sent to external services or APIs unless your MCP client explicitly requests them through its own integration.

Examples of work with audits and modes

Use Accessibility Audit to check WCAG conformance, Performance Audit to identify slow resources, SEO Audit to review metadata and link structure, Best Practices Audit to catch common pitfalls, and NextJS Audit for NextJS-specific SEO improvements.

Enable Audit Mode to run all audits in a predefined sequence. Enable Debugger Mode to run debugging tools in order. These modes help you quickly validate page quality and behavior without leaving your IDE.

Glossary of actions you can request from MCP

Run an accessibility audit, run a performance audit, run an SEO audit, run a best practices audit, run a NextJS audit, enter audit mode, enter debugger mode.

Available tools

runAccessibilityAudit

Runs accessibility checks to identify WCAG issues such as color contrast, missing alt text, keyboard traps, ARIA attributes, and other accessibility problems.

runPerformanceAudit

Performs a Lighthouse-driven assessment to find render-blocking resources, large DOM size, image inefficiencies, and other performance bottlenecks.

runSEOAudit

Evaluates on-page SEO factors like metadata, headings, and link structure, and suggests improvements for better search visibility.

runBestPracticesAudit

Checks for general web development best practices to improve reliability and user experience.

runNextJSAudit

Injects a Next.js specific audit workflow to address SEO and performance considerations for Next.js apps.

runAuditMode

Executes all audits in a predefined sequence, with an additional Next.js audit if Next.js is detected.

runDebuggerMode

Runs a sequence of debugging tools to help you reason about and resolve issues efficiently.