Browser Use
by browser-use
Lets AI do web tasks for you, such as filling forms, searching and extracting data, in the maker’s cloud browsers or on your computer.
Computer or cloud★ 120,087MITUpdated 15 days ago
Chrome DevTools MCP
Overview
Written by PopNx MCP from the maker’s information
Lets AI use Chrome’s developer tools to inspect pages, find what makes them slow and spot errors. Made by the Chrome DevTools team.
Description from the maker (original English)
MCP server for Chrome DevTools
PopNx MCP’s three pillars
These three are never merged into one score: opinions, measurements and popularity are different things.
- User voiceiNo reviews yetReviews open together with accounts in a later step
- Our basic checksi3 of 3 passedChecked from public information; code not scanned yet
- UsageiWidely used★ 54,821
What you can do with it
Good for: Web makers who want AI to find why a site is slow or broken
Try asking your AI
- Open my homepage and tell me what makes it load slowly
- What errors does this page show in the console?
- Measure how long this page takes to load on mobile
Written by PopNx MCP from the maker’s information
Install
Pick the AI app you use, then copy the settings.
You need
- npmNode.js installed (for the npx command)
Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json
{
"mcpServers": {
"chrome-devtools": {
"command": "npx",
"args": [
"-y",
"chrome-devtools-mcp"
]
}
}
}Run this in your terminal
claude mcp add chrome-devtools -- npx -y chrome-devtools-mcpPaste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"chrome-devtools": {
"command": "npx",
"args": [
"-y",
"chrome-devtools-mcp"
]
}
}
}Paste into .vscode/mcp.json in your project
{
"servers": {
"chrome-devtools": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"chrome-devtools-mcp"
]
}
}
}These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
Basic checksi
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 5, 2026
- ✓ Pass
Maker matches the repo
The registry name was verified with the GitHub account ChromeDevTools, which owns the repo
- ✓ Pass
Still maintained
Code last changed today
- ✓ Pass
Has a licence
Uses Apache-2.0
- – Not applicable
Endpoint responds
This one runs on your computer; there is no internet endpoint
- – Not applicable
Sign-in with OAuth
Runs on your computer and uses local settings instead
- … Not checked yet
No hidden instructions in tool descriptions
Needs the server’s tool list first; this check starts in the next step
Compared with others in Web & browsersi
- More stars than 89% of the other 9 servers in this category
- Published to the registry more recently than 56% of the other 9 servers in this category
- Basic checks equal to or better than 100% of the other 9 servers in this category
Compared only with servers in this prototype, not the whole registry.
Common questions
Is Chrome DevTools MCP safe?
It passed 3 of 3 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
What keys or codes does it need?
The registry does not list a required key, though some servers ask you to sign in on first use.
Does it run on my computer or in the cloud?
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
Is it still maintained?
The GitHub repo last changed today, and the latest version (1.12.0) reached the registry 14 days ago.
Which apps can use it?
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.
What can I use instead?
In the same category: Browser Use, MCP Server Browser, Playwright MCP
Alternatives
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
MCP Server Browser
by bytedance
MCP server for browser use access
Runs on your computer★ 39,550Apache-2.0Updated 14 months ago
Playwright MCP
by microsoft
Lets AI open a browser on your computer and click, type and read pages like a person. Made by Microsoft, the team behind Playwright.
Runs on your computer★ 39,198Apache-2.0Updated 5 days ago
README from the maker
Open the README
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
Chrome DevTools for agents
Chrome DevTools for agents (chrome-devtools-mcp) lets your coding agent (such as Antigravity, Claude, Cursor or Copilot) control and inspect a live Chrome browser. It is available as a Model-Context-Protocol (MCP) server and as a CLI. Both give your AI coding assistant access to the full power of Chrome DevTools for reliable automation, in-depth debugging, and performance analysis.
Tool reference | CLI | Skills | Changelog | Contributing | Troubleshooting | Design Principles
Key features
- Get performance insights: Uses Chrome DevTools to record traces and extract actionable performance insights.
- Advanced browser debugging: Analyze network requests, take screenshots and check browser console messages (with source-mapped stack traces).
- Reliable automation. Uses puppeteer to automate actions in Chrome and automatically wait for action results.
Disclaimers
chrome-devtools-mcp exposes content of the browser instance to the MCP clients allowing them to inspect, debug, and modify any data in the browser or DevTools. Avoid sharing sensitive or personal information that you don't want to share with MCP clients.
chrome-devtools-mcp officially supports Google Chrome and Chrome for Testing only. Other Chromium-based browsers may work, but this is not guaranteed, and you may encounter unexpected behavior. Use at your own discretion. We are committed to providing fixes and support for the latest version of Extended Stable Chrome.
Performance tools may send trace URLs to the Google CrUX API to fetch real-user experience data. This helps provide a holistic performance picture by presenting field data alongside lab data. This data is collected by the Chrome User Experience Report (CrUX). To disable this, run with the --no-performance-crux flag.
Usage statistics
Google collects usage statistics (such as tool invocation success rates, latency, and environment information) to improve the reliability and performance of Chrome DevTools MCP.
Data collection is enabled by default. You can opt-out by passing the --no-usage-statistics flag when starting the server:
"args": ["-y", "chrome-devtools-mcp@latest", "--no-usage-statistics"]Google handles this data in accordance with the Google Privacy Policy.
Google's collection of usage statistics for Chrome DevTools MCP is independent from the Chrome browser's usage statistics. Opting out of Chrome metrics does not automatically opt you out of this tool, and vice-versa.
Collection is disabled if CHROME_DEVTOOLS_MCP_NO_USAGE_STATISTICS or CI env variables are set.
Update checks
By default, the server periodically checks the npm registry for updates and logs a notification when a newer version is available. You can disable these update checks by setting the CHROME_DEVTOOLS_MCP_NO_UPDATE_CHECKS environment variable.
Requirements
Getting started
Add the following config to your MCP client:
{"mcpServers": { "chrome-devtools": { "command": "npx", "args": ["-y", "chrome-devtools-mcp@latest"] } } }
[!NOTE]
Using
chrome-devtools-mcp@latestensures that your MCP client will always use the latest version of the Chrome DevTools MCP server.
MCP Client configuration
For setup instructions specific to your editor or agent (e.g. Antigravity, Claude Code, Cursor, VS Code), please see our Client Configurations Guide.
Your first prompt
Enter the following prompt in your MCP Client to check if everything is working:
Check the performance of https://developers.chrome.comYour MCP client should open the browser and record a performance trace.
[!NOTE]
The MCP server will start the browser automatically once the MCP client uses a tool that requires a running browser instance. Connecting to the Chrome DevTools MCP server on its own will not automatically start the browser.
CLI
The package also includes the chrome-devtools CLI. Use it to control the browser from your terminal without MCP:
npm i chrome-devtools-mcp@latest -gchrome-devtools navigate_page 1 --url "https://developers.chrome.com" chrome-devtools take_screenshot 1 --filePath screenshot.png chrome-devtools stop
See the CLI guide for all commands and options.
Skills
The package includes skills that teach your agent how to use Chrome DevTools:
| Skill | Use it to |
|---|---|
chrome-devtools | Debug and automate pages with the MCP tools. |
chrome-devtools-cli | Run the CLI and write shell scripts with it. |
a11y-debugging | Audit and fix accessibility issues. |
cookie-debugging | Debug cookies, sessions, and authentication. |
debug-optimize-lcp | Debug and improve Largest Contentful Paint. |
memory-leak-debugging | Find and fix memory leaks. |
troubleshooting | Fix connection problems between MCP and Chrome. |
Install skills as a plugin
A plugin installs the MCP server and all skills, including the CLI skill:
- Claude Code: Run
/plugin marketplace add ChromeDevTools/chrome-devtools-mcp, then/plugin install chrome-devtools-mcp@chrome-devtools-plugins. - Copilot / VS Code: Run Chat: Install Plugin From Source and enter
ChromeDevTools/chrome-devtools-mcp. - Gemini CLI: Run
gemini extensions install --auto-update https://github.com/ChromeDevTools/chrome-devtools-mcp.
See the Client Configurations Guide for more information.
Install skills manually
If your agent does not support plugins, copy the skill folders into the skills directory of your agent. The npm package contains the skills:
npm i chrome-devtools-mcp@latest -gExample for Claude Code. Use the skills directory of your agent.
mkdir -p ~/.claude/skills cp -R "$(npm root -g)/chrome-devtools-mcp/skills/chrome-devtools-cli" ~/.claude/skills/
[!IMPORTANT]
The
chrome-devtools-cliskill requires the CLI. Install the package globally before you use the skill.
Keep skills up to date
Skills describe the tools of a specific version. Update the skills each time you update the MCP server or the CLI. Outdated skills can tell your agent to use tools or parameters that changed.
- Plugins: Use the update command of the plugin manager of your agent. The Gemini CLI command above enables automatic updates with
--auto-update. - Manual installs: Update the package, then copy the skill folders again:
npm i chrome-devtools-mcp@latest -gmkdir -p ~/.claude/skills cp -R "$(npm root -g)/chrome-devtools-mcp/skills/chrome-devtools-cli" ~/.claude/skills/
Tools
If you run into any issues, checkout our troubleshooting guide. See the full Tool Reference for a complete list of all supported MCP capabilities.
Configuration
Find the complete list of server parameters (e.g., --headless, --isolated, --slim) and how to configure WebSocket connections in the Configuration Guide.
For basic browser tasks only, the --slim flag exposes a reduced set of tools. See the Slim tool reference.
Advanced Usage
For advanced features such as handling concurrent sessions, persistent user data directories, connecting to a running Chrome instance instead of starting a new one, or debugging on Android, see our Advanced Usage Guide.
Integrating as a browser subagent
If you are developing agentic tooling and want to provide an integrated browser subagent as part of your product, we recommend building on top of Chrome DevTools for agents.
For a reference implementation, see the Gemini CLI browser agent documentation.