BrowserTools MCP for Cursor: Setup & Config

What you can do with BrowserTools in Cursor

Browser evidence and Lighthouse audits in one MCP workflow, with an explicit inactive-project caveat.

• Run accessibility, performance, and SEO checks from an AI editor.
• Sequence auditing or debugging operations through dedicated modes.

Before you start: BrowserTools in Cursor

• Chrome with the BrowserTools extension
• A compatible MCP client
• Node.js tooling
• A separate browser-tools-server process
• The BrowserToolsMCP DevTools panel open

Run npx @agentdeskai/browser-tools-server@latest separately. The MCP package belongs in the client configuration. The project is no longer active.

BrowserTools Cursor configuration

1. Choose Cursor configuration scope

   For BrowserTools MCP, open Project: .cursor/mcp.json User: ~/.cursor/mcp.json. Merge into mcpServers at project or user scope.

2. Add BrowserTools MCP to Cursor

   Use the browser-tools-mcp entry below in mcpServers. Keep BrowserTools MCP's documented stdio connection fields and your other Cursor entries.

3. Check BrowserTools MCP in Cursor

   BrowserTools MCP: Enable in Cursor’s MCP settings; inspect tools.

{
  "mcpServers": {
    "browser-tools-mcp": {
      "command": "npx",
      "args": [
        "@agentdeskai/browser-tools-mcp@latest"
      ],
      "env": {}
    }
  }
}

BrowserTools tools available to Cursor

BrowserTools's stored tool list documents 7 tools; compare it with Cursor's connected tool list, because the stored list is not a live check.

runAccessibilityAudit

Find runAccessibilityAudit under BrowserTools in Cursor's MCP settings; inspect its arguments when the agent requests a call.

Check the page for accessibility problems, including WCAG-related issues.

runPerformanceAudit

Find runPerformanceAudit under BrowserTools in Cursor's MCP settings; inspect its arguments when the agent requests a call.

runSEOAudit

Find runSEOAudit under BrowserTools in Cursor's MCP settings; inspect its arguments when the agent requests a call.

runBestPracticesAudit

Find runBestPracticesAudit under BrowserTools in Cursor's MCP settings; inspect its arguments when the agent requests a call.

runAuditMode

Find runAuditMode under BrowserTools in Cursor's MCP settings; inspect its arguments when the agent requests a call.

Run auditing tools in sequence, adding a NextJS check when detected.

runNextJSAudit

Find runNextJSAudit under BrowserTools in Cursor's MCP settings; inspect its arguments when the agent requests a call.

Provide NextJS-focused SEO and development guidance.

runDebuggerMode

Find runDebuggerMode under BrowserTools in Cursor's MCP settings; inspect its arguments when the agent requests a call.

Execute the debugging tools in their prescribed order.

BrowserTools: full stored tool descriptions

Troubleshooting BrowserTools in Cursor

• Cursor must find npx @agentdeskai/browser-tools-mcp@latest (Node.js/npm) for BrowserTools MCP. Enable the project/user entry in MCP settings and inspect its tools.
• BrowserTools MCP uses stdio here: Cursor must keep the configured process running; protocol output belongs on stdout and diagnostics on stderr.
• Known limitation: The project explicitly states that it is no longer active.
• Known limitation: Requires an extension and two distinct server components.
• General Cursor troubleshooting lives in the /clients/cursor guide.

Frequently asked questions