Context7
by upstash
Feeds AI the latest docs for libraries and frameworks before it answers, so code it writes does not use outdated, removed functions.
Computer or cloud★ 64,224MITUpdated yesterday
Install
Brave DevTools MCP
Overview
Description from the maker (original English)
MCP server and CLI for Brave 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 checksi1 of 1 passedChecked from public information; code not scanned yet
- UsageiNot measured yet★ –
What you can do with it
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
- Connection: Runs on your computer
- Transport: stdio
- Category: Search & AI memory
Install
Pick the AI app you use, then copy the settings.
Before you install
- Basic checks: 1 of 1 passed
- Runs on your computer with your user’s permissions (files, network, apps).
- The registry lists no key to fill in.
You need
- npmNode.js installed (for the npx command)
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json
{
"mcpServers": {
"brave": {
"command": "npx",
"args": [
"-y",
"brave-mcp"
]
}
}
}Run this in your terminal
claude mcp add brave -- npx -y brave-mcpOr copy the settings yourself
Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"brave": {
"command": "npx",
"args": [
"-y",
"brave-mcp"
]
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Or copy the settings yourself
Paste into .vscode/mcp.json in your project
{
"servers": {
"brave": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"brave-mcp"
]
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.
Your choice stays on this device in a cookie; no account needed.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
What it can do
Runs on your computer; the tool list appears in your AI app after you install it.
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 7, 2026
- ✓ Pass
Maker matches the repo
The registry name was verified with the GitHub account triuzzi, which owns the repo
- … Not checked yet
Still maintained
We have not read this repo from GitHub yet
- … Not checked yet
Has a licence
We have not read this repo from GitHub yet
- – 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
Runs on your computer; we can only read tool lists from internet endpoints
Compared with others in Search & AI memoryi
- More stars than 0% of the other 7277 servers in this category
- Published to the registry more recently than 62% of the other 7277 servers in this category
- Basic checks equal to or better than 100% of the other 7277 servers in this category
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
Common questions
Is Brave DevTools MCP safe?
It passed 1 of 1 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 –, and the latest version (1.11.0) reached the registry 23 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: Context7, Codebase Memory, Exa
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
Codebase Memory
by DeusData
Codebase knowledge graph for AI agents — 162 languages, sub-ms queries, 99% fewer tokens.
Runs on your computer★ 48,148MITUpdated 21 days ago
Install
Exa
by exa-labs
Connect AI agents to Exa for web search, content fetching, and multi-step research.
Runs in the cloud★ 5,213MITUpdated last month
Install
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.
Brave DevTools for agents
Full Chrome DevTools MCP parity, rebuilt for Brave.
brave-mcp gives Claude Code, Codex, Cursor, OpenCode, and other MCP clients direct access to Brave for browser automation, network and console debugging, performance analysis, screenshots, accessibility inspection, and memory profiling. A standalone brave-devtools CLI is included too.
Install in one command
The commands below use --autoConnect, which attaches brave-mcp to the Brave you already have open, so the agent works with your real tabs and signed-in sessions. Enable it once: open brave://inspect/#remote-debugging in Brave and check Allow remote debugging for this browser instance. Brave keeps this setting across restarts.
Claude Code
claude mcp add brave-devtools --scope user -- npx -y brave-mcp@latest --autoConnectCursor
cursor --add-mcp '{"name":"brave-devtools","command":"npx","args":["-y","brave-mcp@latest","--autoConnect"]}'Codex
codex mcp add brave-devtools -- npx -y brave-mcp@latest --autoConnectOpenCode
opencode mcp add brave-devtools -- npx -y brave-mcp@latest --autoConnectRestart your client, then try this prompt:
Open my app in Brave. Find console errors and failed network requests, inspect the accessibility tree, run Lighthouse, and explain the highest-impact issue.
When the agent connects, Brave asks for permission. Click Allow.
--autoConnect attaches to Brave Release unless you add --channel beta or --channel nightly. To keep the agent out of your everyday browser, leave out --autoConnect: the server then launches its own Brave with a dedicated profile.
Why use this instead of Chrome DevTools MCP?
| Capability | brave-mcp | chrome-devtools-mcp |
|---|---|---|
| Browser launched and discovered natively | Brave Release, Beta, and Nightly | Chrome Stable, Beta, Dev, and Canary |
| Attach to an existing browser | Brave profiles, HTTP, or WebSocket | Chrome profiles, HTTP, or WebSocket |
| Upstream DevTools features | Full parity; currently 0 commits behind | Source implementation |
| Usage telemetry | Disabled by default | Enabled by default |
| Standalone CLI | brave-devtools | chrome-devtools |
Use Chrome DevTools MCP when your target browser is Chrome. Use brave-mcp when your target browser is Brave and you want Brave-native discovery, profiles, channels, naming, and privacy defaults without giving up upstream features.
Tool reference | 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 Brave and automatically wait for action results.
Disclaimers
brave-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.
brave-mcp officially supports the current Brave release. Beta and Nightly channels can be selected explicitly.
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
Usage statistics collection is disabled by default in this fork. It can be enabled explicitly with --usage-statistics, which uses the upstream Google Clearcut implementation:
"args": ["-y", "brave-mcp@latest", "--usage-statistics"]When enabled, Google handles this data in accordance with the Google Privacy Policy. Collection remains disabled if BRAVE_DEVTOOLS_MCP_NO_USAGE_STATISTICS or CI is 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 BRAVE_DEVTOOLS_MCP_NO_UPDATE_CHECKS.
Requirements
Getting started
Enable remote debugging once at brave://inspect/#remote-debugging, then add the following config to your MCP client to attach to your running Brave:
{"mcpServers": { "brave-devtools": { "command": "npx", "args": ["-y", "brave-mcp@latest", "--autoConnect"] } } }
[!NOTE]
Using
brave-mcp@latestensures that your MCP client will always use the latest version of the Brave DevTools MCP server.
Leave out --autoConnect to have the server launch its own Brave with a dedicated profile instead.
If you are interested in doing only basic browser tasks, use the --slim mode:
{"mcpServers": { "brave-devtools": { "command": "npx", "args": ["-y", "brave-mcp@latest", "--slim", "--headless"] } } }
See Slim tool reference.
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. To attach to your running Brave, add --autoConnect to the server arguments shown there.
Your first prompt
Enter the following prompt in your MCP Client to check if everything is working:
Check the performance of https://brave.comBrave asks you to allow the connection. After you click Allow, your MCP client opens the page in Brave and records a performance trace.
[!NOTE]
The MCP server connects to Brave only when the MCP client first uses a tool that needs a browser, not when the client starts. Without
--autoConnect, that is when the server launches its own Brave.
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.
Advanced usage
For advanced features such as handling concurrent sessions, persistent user data directories, connecting to a running Brave instance instead of starting a new one, or debugging on Android, see our Advanced Usage Guide.
Known limitations
See Troubleshooting.
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 Brave DevTools for agents.
For a reference implementation, see the Gemini CLI browser agent documentation.