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.
Description from the maker (original English)
Let AI agents observe and control Chrome tabs you explicitly share via Browse Bridge.
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
AuthorizationValues marked secret are keys to your account. Never share them or paste them into a chat.
You need
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
This address needs a key in a request header, which the add-connector menu cannot set. Use Claude Code, Cursor or VS Code instead.
Run this in your terminal
claude mcp add --transport http browse-bridge https://mcp.browsebridge.com/mcp --header 'Authorization: Bearer {api_key}'Fill in the empty values before running it.
Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"browse-bridge": {
"url": "https://mcp.browsebridge.com/mcp",
"headers": {
"Authorization": "Bearer {api_key}"
}
}
}
}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.
Paste into .vscode/mcp.json in your project
{
"servers": {
"browse-bridge": {
"type": "http",
"url": "https://mcp.browsebridge.com/mcp",
"headers": {
"Authorization": "Bearer {api_key}"
}
}
}
}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 address needs a key in a request header, which the add-connector menu cannot set. Use Claude Code, Cursor or VS Code instead.
Your choice stays on this device in a cookie; no account needed.
Authorization secret required HTTP headerThese settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
The server asks you to sign in before it lists its tools.
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 9, 2026
The registry name was verified against the domain browsebridge.com (the registry checks domain ownership)
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
Responded in 375 ms (HTTP 401)
Declares OAuth sign-in, so your AI app can take you to log in
Not checked yet; we read the tool list when we check the endpoint
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
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.
You need to fill in: Authorization
It runs in the maker’s cloud. Connect over the internet with nothing to install, but what you send passes through the maker’s servers.
The GitHub repo last changed –, and the latest version (1.0.0) reached the registry 12 days ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. It connects by URL, so apps that accept remote MCP servers work too, such as ChatGPT in developer mode.
In the same category: Browser Use, Chrome DevTools MCP, MCP Server Browser
Servers in the same category from other makers, sorted by stars.
Reading a card:↓ Downloads per weeki★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
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.
Lets AI use Chrome’s developer tools to inspect pages, find what makes them slow and spot errors. Made by the Chrome DevTools team.
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.
Cursor Plugin that wires Browse Bridge remote MCP into Cursor so agents can observe and control browser tabs you have Explicitly Enabled in the Chrome extension.
https://mcp.browsebridge.com/mcpbbk_). Keep it secret.Install browse-bridge from the Cursor Marketplace and paste your API key when prompted (BROWSEBRIDGE_API_KEY).
# Copy (do not symlink outside this folder)
cp -R /path/to/browsebridge-cursor-plugin ~/.cursor/plugins/local/browse-bridge
Reload Window, open Customize, configure BROWSEBRIDGE_API_KEY, confirm MCP tools appear (browser_observe, browser_click, etc.).
mcp.json snippet{
"mcpServers": { "browse-bridge": { "url": "https://mcp.browsebridge.com/mcp", "headers": { "Authorization": "Bearer ${BROWSEBRIDGE_API_KEY}" } } } }
Plugin variables only fill in inside the plugin, so for a manual config use your real key or ${env:BROWSEBRIDGE_API_KEY}.
chrome://).browser_list_sessions, browser_observe, browser_click, browser_screenshot.| Tool | What it does | |
|---|---|---|
browser_list_sessions | List Enabled shared tabs. | |
browser_get_status | Control mode, URL, deviceOnline, pending approvals, remaining monthly quota (actionsRemaining, screenshotsRemaining, quotaExceeded, quotaResetAt). Tools return QUOTA_EXCEEDED when a monthly quota is exhausted. | |
browser_observe | Semantic page tree + observationId / elementIds. | |
browser_screenshot | Visible-tab JPEG as MCP image content. | |
browser_click | Click an observed element. Optional button: "left" (default), "right", or "middle". | |
browser_type | Set a control's value (not a password). | |
browser_select | Choose a listed . | |
browser_press_key | Key in the focused (or named) element. | |
browser_hover | mouseover / mouseenter on an observed element. | |
browser_scroll | Scroll the page or an element into view. | |
browser_navigate | Go to an allowed http(s) URL. | |
browser_back | History back. | |
browser_forward | History forward. | |
browser_reload | Reload the tab. | |
browser_wait | Pause 0–30000 ms. | |
browser_release_control | Give the tab back to the human (controlMode: "human"). | |
browser_handle_dialog | Accept or dismiss a pending JavaScript alert / confirm / prompt (action: accept\ | dismiss; optional promptText when accepting a prompt). |
browser_get_approval | Read-only status of a pending approval (approvalId). Does not Approve, Deny, or cancel. | |
browser_cancel_approval | Withdraw a pending agent approval (approvalId). | |
get_profile | Read-only Browse Bridge user id for the signed-in account (no email, tokens, cookies, or page content). |
While the agent has control, a page alert / confirm / prompt stays pending until browser_handle_dialog (or about a 30-second timeout dismiss). Other click, type, and navigate calls while a dialog is open return `DIALOG_PENDING`. Native HTTP basic or digest sign-in prompts are not JavaScript dialogs (HTTP_AUTH_REQUIRED). The human completes or cancels them. Browse Bridge never types those credentials.
Sensitive site gates click, type, key, select, and navigation. Those actions, and cross-origin navigations (including cross-origin link clicks), return `APPROVAL_REQUIRED`. The human Approves or Denies in the Chrome side panel. `browser_get_approval` reads a pending approval and does not change it. The agent can withdraw its own request with `browser_cancel_approval` (APPROVAL_CANCELLED — that is not a human Deny). An expired approval returns `APPROVAL_EXPIRED`; the next request for that action returns a fresh `APPROVAL_REQUIRED`. While an approval is pending, observe/screenshot/wait/get_status/list_sessions/release_control still run.
| Variable | Required | Description |
|---|---|---|
BROWSEBRIDGE_API_KEY | Yes | API key from the Browse Bridge dashboard |
Declared in .cursor-plugin/plugin.json → variables and referenced only as ${BROWSEBRIDGE_API_KEY} in mcp.json.
See PRIVACY.md and SECURITY.md.
.cursor-plugin/plugin.json
mcp.json assets/logo.svg assets/icon.png README.md LICENSE PRIVACY.md SECURITY.md SUPPORT.md