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)
Browserbase MCP server: cloud browser sessions, agents, contexts, fetch, search, functions
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.
BROWSERBASE_API_KEY, BROWSERBASE_REQUEST_TIMEOUT_MS, MCP_WORKSPACE_PATHValues 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 …”.
Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json
{
"mcpServers": {
"browserbase": {
"command": "npx",
"args": [
"-y",
"@mindstone/mcp-server-browserbase"
],
"env": {
"BROWSERBASE_API_KEY": "your-value",
"BROWSERBASE_REQUEST_TIMEOUT_MS": "your-value",
"MCP_WORKSPACE_PATH": "your-value"
}
}
}
}Run this in your terminal
claude mcp add browserbase --env BROWSERBASE_API_KEY=your-value --env BROWSERBASE_REQUEST_TIMEOUT_MS=your-value --env MCP_WORKSPACE_PATH=your-value -- npx -y @mindstone/mcp-server-browserbaseFill in the empty values before running it.
Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"browserbase": {
"command": "npx",
"args": [
"-y",
"@mindstone/mcp-server-browserbase"
],
"env": {
"BROWSERBASE_API_KEY": "your-value",
"BROWSERBASE_REQUEST_TIMEOUT_MS": "your-value",
"MCP_WORKSPACE_PATH": "your-value"
}
}
}
}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": {
"browserbase": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@mindstone/mcp-server-browserbase"
],
"env": {
"BROWSERBASE_API_KEY": "your-value",
"BROWSERBASE_REQUEST_TIMEOUT_MS": "your-value",
"MCP_WORKSPACE_PATH": "your-value"
}
}
}
}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.
BROWSERBASE_REQUEST_TIMEOUT_MS envMCP_WORKSPACE_PATH envThese settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
Runs on your computer; the tool list appears in your AI app after you install it.
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 6, 2026
The registry name was verified with the GitHub account mindstone, which owns the repo
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Runs on your computer; we can only read tool lists from internet endpoints
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
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.
You need to fill in: BROWSERBASE_API_KEY
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).
The GitHub repo last changed –, and the latest version (0.1.1) reached the registry 3 months ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.
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:★ 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.
MCP server for browser use access
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.
Cloud browser automation via the Browserbase API: sessions with live-view debugging, AI web agents, persistent contexts, downloads, fetch/search, and serverless functions.
*Best for MCP hosts that want a local browser-automation connector covering the entire Browserbase API — from "open a browser and show me" to "run an agent that extracts pricing data".*
BROWSERBASE_API_KEY)STATUS.jsonBrowserbase's API spans everything from raw CDP sessions to fully-managed AI agents. This package exposes all of it to local stdio MCP hosts as a single connector with deliberate guardrails: session billing is called out in tool descriptions, destructive actions are annotated, external web content is always wrapped as untrusted data, and long-running work is polled (Browserbase has no webhooks).
"Extract the pricing tiers from example.com and give them to me as JSON."
Tools the host calls:
create_agent_run — starts a run with the task and a result_schema for the JSON shape.wait_for_agent_run — polls until the run completes and returns the structured result.get_agent_run_messages — (optional) shows what the agent did, step by step.Response (trimmed):
{
"ok": true, "runId": "r0a0b0c0-…", "status": "COMPLETED", "result": { "plans": [ { "name": "…", "price": 0 } ] }, "waited_seconds": 47 }
After clicking the button, your host will prompt you to fill: BROWSERBASE_API_KEY.
Manual config for Claude Desktop / Claude Code / Goose / Continue.dev (Browserbase)
{
"mcpServers": { "Browserbase": { "command": "npx", "args": [ "-y", "@mindstone/mcp-server-browserbase" ], "env": { "BROWSERBASE_API_KEY": "" } } } }
cd <path-to-repo>/connectors/browserbase
npm install npm run build
npx -y @mindstone/mcp-server-browserbase
node dist/index.js
| Variable | Required | Description |
|---|---|---|
BROWSERBASE_API_KEY | Yes | Browserbase API key. Get one at browserbase.com/settings |
BROWSERBASE_REQUEST_TIMEOUT_MS | No | Per-request timeout for Browserbase API calls in milliseconds (default 30000) |
MCP_WORKSPACE_PATH | No | Workspace directory for local files uploaded by upload_session_file, upload_extension, and upload_certificate. File reads are sandboxed to this directory; defaults to the system temp directory. |
When running inside a host that provides the credential bridge, configure_browserbase_api_key persists the key through the host instead of the environment.
{
"mcpServers": { "browserbase": { "command": "npx", "args": ["-y", "@mindstone/mcp-server-browserbase"], "env": { "BROWSERBASE_API_KEY": "your-api-key" } } } }
Every create_session starts a billable browser (per-minute, 1-minute minimum). The create_session and end_session descriptions tell the agent this explicitly, and end_session should be called as soon as automation finishes. Exceeding the project's concurrency limit returns 429 with a retry-after window that the error resolution surfaces verbatim.
get_session returns a credentialed connectUrl and get_session_debug_urls returns debugger/live-view URLs. Anyone with these URLs can watch AND drive the browser — they are for sharing with the session's owner, never publicly.
Anything authored outside your account — fetched page content, search results, page titles in debug URLs, agent run tasks/results/messages, CDP log bodies, replay playlists, download filenames, function output, error details — is wrapped in envelopes with close-tag breakout escaping before it reaches the model. CDP log rawBody values are additionally truncated beyond ~4KB with a truncation note.
upload_session_file, upload_extension, and upload_certificate accept local file_paths. Reads are constrained to MCP_WORKSPACE_PATH (or the system temp directory when unset) using canonical-prefix containment: .. traversal, absolute paths outside the sandbox, and symlinks that escape it are rejected before any disk read. The read is open-then-validate: the connector opens a descriptor, confirms the opened inode is the file the sandbox approved, reads through that descriptor, and re-checks it after the read — a file swapped or modified mid-read fails closed.
fetch_url (and the URLs embedded in search results you might fetch next) are guarded by a public-URL check: only http:///https:// schemes, and localhost, loopback, link-local, and private IP ranges are rejected before any request is sent.
delete_context, delete_agent, delete_download, delete_extension, delete_certificate, end_session, stop_agent_run, invoke_function, and all create_*/upload_* tools carry destructiveHint: true. Deletes are permanent; hosts should require explicit user confirmation.
GET /sessions/{id}/recording (rrweb event dump) is deprecated by Browserbase and returns a deprecation 404 — it is deliberately not exposed. Use get_session_replays / get_session_replay_playlist (watchable) or the recording-download tools (MP4 files) instead.wait_for_agent_run / get_agent_run), recording downloads (get_session_recording_downloads), and function invocations (get_function_invocation) are all polled.Only the beginning is shown; read the rest in the repo