Prototype · Preview: every server in the official registry, synced every 30 minutes. Reviews and accounts come in a later step.
PopNx MCPMCP servers for people who use AI · explained in plain words

Browserbase

by mindstoneversion 0.1.1i★ –iRuns on your computer
Registry nameio.github.mindstone/mcp-server-browserbase

Install

Overview

Description from the maker (original English)

Browserbase MCP server: cloud browser sessions, agents, contexts, fetch, search, functions

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

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: Web & browsers
  • You need to fill in: BROWSERBASE_API_KEY

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).
  • You fill in yourself: BROWSERBASE_API_KEY, BROWSERBASE_REQUEST_TIMEOUT_MS, MCP_WORKSPACE_PATH

Values marked secret are keys to your account. Never share them or paste them into a chat.

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": {
    "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-browserbase

Fill in the empty values before running it.

Open in Cursor

Or copy the settings yourself

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.

Open in VS Code

Or copy the settings yourself

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.

Values you fill in

  • BROWSERBASE_API_KEY secret required env
    Browserbase API key (from browserbase.com/settings)
  • BROWSERBASE_REQUEST_TIMEOUT_MS env
    Optional per-request timeout in milliseconds for Browserbase API calls (default 30000).
  • MCP_WORKSPACE_PATH env
    Optional workspace directory for local files uploaded to Browserbase (session files, extensions, certificates). File reads are sandboxed to this directory (defaults to the system temp directory when…

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 6, 2026

  • ✓ Pass

    Maker matches the repo

    The registry name was verified with the GitHub account mindstone, 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 Web & browsersi

  • More stars than 0% of the other 876 servers in this category
  • Published to the registry more recently than 30% of the other 876 servers in this category
  • Basic checks equal to or better than 100% of the other 876 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 Browserbase 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?

You need to fill in: BROWSERBASE_API_KEY

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 (0.1.1) reached the registry 3 months 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, Chrome DevTools MCP, MCP Server Browser

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

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 16 days ago
Install

Chrome DevTools MCP

by ChromeDevTools

Lets AI use Chrome’s developer tools to inspect pages, find what makes them slow and spot errors. Made by the Chrome DevTools team.

Runs on your computer★ 54,821Apache-2.0Updated 15 days ago
Install

MCP Server Browser

by bytedance

MCP server for browser use access

Runs on your computer★ 39,550Apache-2.0Updated 14 months ago
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.

@mindstone/mcp-server-browserbase

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".*

Status

  • Version: 0.1.1 · npm
  • Auth: API key (BROWSERBASE_API_KEY)
  • Tools: 53 (projects, sessions, contexts, agents, agent runs, downloads, extensions, certificates, fetch/search, functions)
  • Surface: cloud-api
  • Machine-readable: STATUS.json

Why this exists

Browserbase'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).

Example interaction

"Extract the pricing tiers from example.com and give them to me as JSON."

Tools the host calls:

  1. create_agent_run — starts a run with the task and a result_schema for the JSON shape.
  2. wait_for_agent_run — polls until the run completes and returns the structured result.
  3. 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 }

Requirements

One-click install

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": "" } } } }

Quick Start

Install & build
cd <path-to-repo>/connectors/browserbase

npm install npm run build

npx
npx -y @mindstone/mcp-server-browserbase
Local
node dist/index.js

Configuration

VariableRequiredDescription
BROWSERBASE_API_KEYYesBrowserbase API key. Get one at browserbase.com/settings
BROWSERBASE_REQUEST_TIMEOUT_MSNoPer-request timeout for Browserbase API calls in milliseconds (default 30000)
MCP_WORKSPACE_PATHNoWorkspace 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.

MCP Host Configuration
{

"mcpServers": { "browserbase": { "command": "npx", "args": ["-y", "@mindstone/mcp-server-browserbase"], "env": { "BROWSERBASE_API_KEY": "your-api-key" } } } }

Security notes

Sessions are billed — release them

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.

Live-view URLs grant control

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.

External content is always enveloped

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.

File uploads are workspace-sandboxed

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 cannot probe internal networks

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 and stop tools are annotated as destructive

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.

Tools (53)

Configuration
  • configure_browserbase_api_key — Save your Browserbase API key (host-persisted when a bridge is present)
Projects
  • list_projects — List projects (IDs, concurrency limits, default timeouts)
  • get_project — Get one project's details
  • get_project_usage — Browser minutes and proxy bytes consumed
Sessions
  • create_session — Create a cloud browser session (billed per minute; returns connectUrl)
  • list_sessions — List sessions, filtered by status or userMetadata query
  • get_session — Get a session's status and connectUrl
  • end_session — Release a session (REQUEST_RELEASE semantics; sessions also auto-expire)
  • get_session_debug_urls — Live-view + debugger URLs to share with a human
  • get_session_logs — CDP-level session logs (raw bodies truncated beyond ~4KB)
  • get_session_replays — List recorded pages available for replay
  • get_session_replay_playlist — Fetch a page's m3u8 replay playlist
  • request_session_recording_downloads — Request async MP4 assembly (HTTP 202)
  • get_session_recording_downloads — Poll MP4 status; get short-lived signed URLs
  • upload_session_file — Upload a sandboxed local file to /tmp/.uploads/ in the session
Contexts (persistent browser state)
  • create_context — Create a context for persisting cookies/storage across sessions
  • get_context — Get a context's details
  • delete_context — Permanently delete a context
Agents
  • create_agent — Create a reusable agent (name, system prompt, result schema)
  • list_agents — List agents (cursor-paginated, date-filterable)
  • get_agent — Get an agent's prompt and result schema
  • update_agent — Partially update an agent
  • delete_agent — Delete an agent (existing runs unaffected)
Agent Runs
  • create_agent_run — Start a run (ad-hoc or with an agent; %variable% substitution for sensitive values)
  • list_agent_runs — List runs (cursor-paginated, filterable)
  • get_agent_run — Get a run's status and terminal result/cause
  • wait_for_agent_run — Recommended: poll until terminal and return the result
  • get_agent_run_messages — The run's UIMessage conversation (since/nextSince feed)
  • stop_agent_run — Stop a running run (202; 409 if already terminal)
Downloads (files downloaded inside sessions)
  • list_downloads — List downloads for a session (offset-paginated, filterable)
  • get_download_info — Metadata (size, checksum, MIME type)
  • get_download_file — Fetch the bytes as base64 (8MB inline cap)
  • delete_download — Permanently delete a download
Extensions
  • upload_extension — Upload a zipped Chrome extension (sandboxed file read)
  • get_extension — Get an uploaded extension
  • delete_extension — Permanently delete an extension
Certificates
  • upload_certificate — Upload a CA certificate for TLS-inspecting proxies
  • list_certificates — List uploaded certificates
  • get_certificate — Get a certificate
  • delete_certificate — Permanently delete a certificate
Fetch & Search
  • fetch_url — Server-side fetch: raw body, markdown, or schema-driven JSON
  • web_search — Web search with ranked results
Functions (serverless browser automations — list/invoke/inspect only)
  • list_functions — List deployed functions
  • get_function — Get a function
  • invoke_function — Invoke a function (async 202; poll the invocation)
  • list_function_versions — List a function's versions
  • get_function_version — Get a version's userParamsSchema (check before invoking)
  • list_function_invocations — List a version's invocations
  • get_function_invocation — Get an invocation's status, results, and cause
  • get_function_invocation_logs — An invocation's logs
  • list_function_builds — List function builds
  • get_function_build — Get a build's status and failure cause
  • get_function_build_logs — A build's logs

API coverage notes

  • Deprecated upstream: 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.
  • No webhooks: Browserbase is poll-based. Agent runs (wait_for_agent_run / get_agent_run), recording downloads (get_session_recording_downloads), and function invocations (get_function_invocation) are all polled.
  • **No list endpoin

Only the beginning is shown; read the rest in the repo

Ask PopNx