BrowserTools MCP
Console, network, screenshots and Lighthouse audits from your open Chrome session to the agent via a DevTools extension
- 7,339 ★ on the repository
- Last commit
- MIT
Broad access
Why this level
- Reads data from a logged-in browser session, including request bodies and storage
- Requires an extension with DevTools access
Install
- Works in
In your terminal, with SkillFoxx CLI
npx skillfoxx add mcp/browsertools-mcpDetects the agents on your machine, shows the access level and pins the version.
Other ways to install
Access and checks
How we reviewBroad accessThe tool can change data, run commands or handle secrets.
- Reads data from a logged-in browser session, including request bodies and storage
- Requires an extension with DevTools access
This is third-party code. Review the repository files before installing.
What it does
The server and a Chrome extension pass the agent what happens in a tab with DevTools open: console logs, errors, network requests with bodies, the selected element and storage. The agent can take screenshots, reload the tab and run Lighthouse-based accessibility, performance, SEO and best-practice audits. Unlike automation servers it uses your regular session where you are already logged in. Large payloads are exposed as MCP resources, and auth headers and tokens are scrubbed before they leave the browser.
Who it is for. For frontend developers debugging an app in the browser together with an agent.
Good fit when
- You want the agent to see console errors and failed requests on a live page
- Debugging needs a logged-in session that is hard to reproduce
- You need a quick accessibility or performance audit of a page
Not a fit when
- You need to write and run automated tests in a clean browser
- You use Firefox: support is unverified
Example request
Check the console errors on the open page and see which API requests failedMCP
- Transport
- stdio
- Authentication
- not required
Environment variables
CHROME_PATH- Path to the Chromium-based browser used for audits
Limitations
Requires Node 22.19 or newer and an extension loaded manually in developer mode. Network capture starts only once DevTools is open. Audits launch a separate Chromium and take up to a minute. Version 1.2.x has a critical vulnerability; upgrade to 2.0.
How to disable. Remove the browser-tools block from the MCP config and remove the extension at chrome://extensions.
FAQ
How is it different from Playwright MCP?
Playwright MCP drives a separate automated browser, while this server reads your current Chrome session with its logins.
Do I need to start a second server?
Not in version 2.0; the MCP server runs the connector itself.
Discussion
No questions or reviews yet.
Related
MCP serversAn MCP server plus a Chrome extension: pick a DOM element by Option-click and the agent gets its text, styles and selector
Connects an agent to a running Next.js 16+ dev server: errors, routes, logs and docs for your installed version
A CLI that lets an agent inspect a running React app: component tree, props, state, hooks and render profiling
Tilda MCP with bulk editing via CDP
tilda-mcp-cdp
An MCP server for Tilda: reads via the official API and writes via a logged-in Chrome over CDP, including a full Zero Block element editor
A set of skills for web quality audits: performance, Core Web Vitals, accessibility, SEO and best practices from Lighthouse
Shadcn UI MCP Server
Shadcn UI v4 MCP Server
An MCP server that gives the agent shadcn/ui component source, demos and blocks for React, Svelte, Vue and React Native
Comparison with similar tools
Entries that share the main search query, and how they differ.
| Entry | Official | Authentication | Repository stars | Main difference |
|---|---|---|---|---|
| BrowserTools MCP (this entry) | no | not required | 7,339 | |
| Agentation | no | 5,157 | annotation toolbar for React pages | |
| Expect | no | 3,561 | a skill that tests your agent's code in a real browser | |
| Ui.Vision RPA | yes | not required | 2,092 | an MCP bridge and browser extension for RPA |
README in short
The README opens with a note about the 2.0 rewrite and the 1.x vulnerability. Setup is an npx MCP config plus manually loading the extension. It has a tool table and covers multiple tabs, resources for large data and pagination parameters. Security measures, launch flags and known limits get their own sections. MIT licensed.