PlugWiki
browser-tools-mcp logo

BrowserTools MCP Server: Setup for Cursor, Claude and Other Apps

CommunityLocal
Getnpm@agentdeskai/browser-tools-mcpagentdeskai/browser-tools-mcp

Lets Cursor, Claude Code and other assistants see your real Chrome tab: console errors, network calls, screenshots and Lighthouse audits.

BrowserTools connects your assistant to the Chrome tab you are looking at, through a Chrome extension you load from the repo and a DevTools panel. It reads the console, network traffic and screenshots from your real, logged-in session, then runs Lighthouse audits on request.

The README says it captures whatever the browser sees, and that version 1.x had serious security problems and is unsupported. Use version 2 only, and keep sensitive tabs closed while you debug.

Good for

  • Web developers who want an assistant to debug the page they already have open and logged in
  • Cursor and Claude Code users who are tired of copying console errors by hand
  • Anyone who wants Lighthouse speed, accessibility and SEO audits from chat

Works in

12 should work

Tap an app to see how to set it up and any known problems.

Install browser-tools MCP

Claude Code

  1. 1

    Copy this prompt.

    Add the browser-tools MCP server to Claude Code. Run this command:
    
    claude mcp add browser-tools -- npx -y @agentdeskai/browser-tools-mcp
    
    Then check that it loaded and tell me if I need to sign in or restart.
  2. 2

    Paste it into Claude Code. It shows the change and asks before running it.

Requires Node.js.

Read-only mode: There is no read-only switch. Start the server with --only to expose just the tools you want, or --exclude to hide some, such as the page-reload and clear-logs tools.

Install it with the command above. It also needs the Chrome extension: download or clone the repo, open chrome://extensions, turn on Developer mode, choose Load unpacked and pick the chrome-extension folder. Then open Chrome DevTools (F12) on the page you want to inspect, because capture only starts once DevTools is open. It needs Node 22.19 or newer. If something is missing, run the package with --doctor to see which piece. On Windows, if your app cannot find npx, use cmd with the arguments /c and npx, as the README says.

Built from the package data we hold. Not yet tested by us.

Tools

  • Shows errors and crashes from the browser console

    Returns error-level console output and uncaught exceptions from the tab you are inspecting. You can filter by keyword and page through results.

    Try: “Check the console for errors on this page.”

    Read · getConsoleErrors

  • Shows everything printed to the browser console

    Returns console output, filterable by keyword, with paging.

    Try: “Show console logs mentioning "hydration".”

    Read · getConsoleLogs

  • Shows failed requests

    Returns only failed requests and 4xx or 5xx responses.

    Try: “Which API calls failed when I clicked Pay?”

    Read · getNetworkErrors

  • Shows the page's web requests

    Returns XHR and fetch requests with status, timing and bodies. Filter by URL or body keywords.

    Try: “List the requests to /api/ and their response times.”

    Read · getNetworkLogs

  • Takes a screenshot of the page you are on

    Returns the screenshot as an image and saves it to a local folder.

    Try: “Take a screenshot and tell me what looks broken.”

    Write · takeScreenshot

  • Reads the element you picked in DevTools

    Returns the element currently selected in the Elements panel.

    Try: “Look at the element I have selected and tell me why it is misaligned.”

    Read · getSelectedElement

  • Tells you which page the browser is on

    Returns the page the browser is currently on.

    Try: “What page am I on?”

    Read · getPageInfo

  • Checks the browser extension is connected

    Reports whether the extension is connected and how much has been captured.

    Try: “Is the browser extension connected?”

    Read · getConnectionStatus

  • Lists tabs that have DevTools open

    Lists the tabs being tracked, each with a tab ID you can pass to other tools.

    Try: “Which tabs are you watching?”

    Read · listBrowserTabs

  • Reads localStorage, sessionStorage and cookies

    Returns browser storage. The README says values are withheld unless explicitly requested.

    Try: “Show the keys in localStorage for this page.”

    Read · getBrowserStorage

  • Reloads the page you are inspecting

    Reloads the tab so you can capture a full page load.

    Try: “Reload the page and check the network calls again.”

    Write · refreshBrowser

  • Clears captured console and network history

    Clears the telemetry captured so far, for a clean reproduction of a bug.

    Try: “Clear the logs, then I will reproduce the bug.”

    Delete · wipeLogs

Read from the source code

Permissions

medium risk · 5 things to watch · 2 advisories

Medium risk

The assistant can see everything in the tab you are debugging, including page data from your logged-in session. Close tabs that show private data while you use it, and hide tools you do not need with the --exclude flag.

What it can do

  • Read your data
  • Create and change things
  • Delete things
  • Read-only mode

Watch out for

  • It sees what your logged-in browser sees

    Console output, requests, responses and screenshots can contain private data. The README says credentials are scrubbed, headers are off by default and storage values are withheld unless requested. github.com

  • Version 1.x has critical flaws

    The README says 1.x allowed remote code execution and unauthenticated access to captured data, and will not be patched. Use 2.0 or newer. github.com

  • It can reload pages and clear history

    Reload and clear-logs tools change the page state and wipe captured data. Hide them with --exclude if you do not want that. github.com

  • Screenshots are saved to your disk

    Screenshots are written to a local folder, which you can set with --screenshot-dir. github.com

  • Local only by default

    The README says the connector only binds to 127.0.0.1 and refuses non-loopback addresses. github.com

Security advisories

Technical details
Turning on read-onlyNo read-only mode is documented. Use the --only flag to expose just the read tools you want, or --exclude to hide some.
Talks toLocal only (127.0.0.1, port 3025 by default). Websites you audit with Lighthouse
Sign-in and keysNo account or API key. The local connector uses a per-run token, and the README says the extension fetches it over loopback.
Scopes
  • Chrome extension permissions; cookie access is an optional permission you grant in the panel

Questions

Is BrowserTools official?

No. It is made by AgentDesk AI, not by Google or Chrome. It is a Chrome extension plus an MCP server.

Does it need a Chrome extension?

Yes. Load the extension from the repo's chrome-extension folder using Developer mode in Chrome, then open DevTools on the page. The install box notes show the steps.

Which Node version does it need?

The README says Node 22.19 or newer. If you use nvm or asdf, make sure your editor uses the same version.

Is it safe to use with logged-in sites?

Mostly local. The README says it binds to your own machine, scrubs credentials and withholds storage values by default. Still, the assistant can read what the tab shows, so keep sensitive tabs closed.

Why is it different from Playwright or Chrome DevTools MCP?

It attaches to the Chrome session you already use, so you stay logged in. The README says other tools drive a fresh automated browser and cannot use your default profile since Chrome 136.

Why are there tools on this page marked unreleased?

They are in the main branch README but not in the 2.0.4 release. They include tab listing, background navigation and soft click and type.

Should I use version 1?

No. The README says 1.x has known critical vulnerabilities and will not be patched.

Information

updated Nov 2, 2026

Publisher
Community
Package
@agentdeskai/browser-tools-mcp
Registry
npm
Version
2.0.4
License
MIT
Last commit
Oct 28, 2026
Open issues
0

WebsiteGitHubnpmChangelogIssues

Sources

Docs, issue trackers and discussions this page is built from. Issues, quotes and findings above link to their own source.

Show all 2
  1. BrowserTools README · github.com
  2. BrowserTools README at v2.0.4 · github.com

Facts from the official MCP registry, GitHub, npm, PyPI and the Docker catalog. Updated Nov 2, 2026.