# @mindstone/mcp-server-browserbase

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

- **Type:** MCP server
- **Trust:** 60/100 (B), scored on the package rubric
- **Verification:** community-indexed — nobody has claimed this listing
- **Version:** 0.1.1
- **Author:** io.github.mindstone
- **License:** Unknown
- **npm:** @mindstone/mcp-server-browserbase
- **Source:** https://github.com/mindstone/mcp-servers
- **Compatible clients:** claude-code, cursor, copilot, gemini (basis: transport)

## Trust

60/100 (B), scored on the package rubric
- Publisher verified: no
- Install scripts: nothing suspicious found
- Prompt-injection scan: not run
- Obfuscation scan: not run
- Evidence age: 1 day

## Security scan

- **Status:** clean
- **Scanned:** 2026-09-01T10:02:56.669Z
- **Version scanned:** 0.1.1
- **CVEs:** none found by OSV at scan time
**Findings**
- injection-shaped content (note) in the `get_agent` tool: References the system prompt
- injection-shaped content (note) in the `configure_browserbase_api_key` tool: Links to undeclared domain: browserbase.com

## Tools

40 declared. Statically extracted from the shipped source — a floor on the surface, not a census.
- `create_agent_run`
- `list_agent_runs`
- `get_agent_run`
- `wait_for_agent_run`
- `get_agent_run_messages`
- `stop_agent_run`
- `create_agent`
- `list_agents`
- `get_agent` — Get a reusable agent's full configuration: name, system prompt, and result schema. WHEN TO USE: - Review the prompt before starting a run with this agent - Conf
- `update_agent`
- `delete_agent`
- `upload_certificate`
- `list_certificates` — List CA certificates uploaded to the account. WHEN TO USE: - Find certificate IDs to reference in create_session proxy_settings.ca_certificates ERROR RECOVERY: 
- `get_certificate` — Get details of an uploaded CA certificate. WHEN TO USE: - Verify a certificate still exists before referencing it in create_session proxy_settings ERROR RECOVER
- `delete_certificate` — Permanently delete an uploaded CA certificate. CRITICAL: There is no undo. New sessions referencing this certificate in proxy_settings.ca_certificates will fail
- `configure_browserbase_api_key` — Host-managed setup only. The user adds the Browserbase API key in Settings → Connectors in the app. Do not ask for or accept the key in chat. WHERE TO GET A KEY
- `create_context`
- `get_context` — Get details of a persistent browser context. WHEN TO USE: - Verify a context still exists before referencing it in create_session - Check which project a contex
- `delete_context` — Permanently delete a browser context and all of its stored state (cookies, storage). CRITICAL: There is no undo — any login sessions persisted in the context ar
- `list_downloads`
- `get_download_info`
- `get_download_file`
- `delete_download`
- `upload_extension`
- `get_extension` — Get details of an uploaded extension. WHEN TO USE: - Verify an extension still exists before referencing it in create_session ERROR RECOVERY: - 401: API key is 
- `delete_extension` — Permanently delete an uploaded extension. CRITICAL: There is no undo. Sessions created afterwards can no longer load it (existing sessions are unaffected). ERRO
- `list_functions`
- `get_function` — Get a deployed function's details. WHEN TO USE: - Confirm a function exists and get its project before invoking it ERROR RECOVERY: - 401: API key is missing or 
- `invoke_function`
- `list_function_versions` — List the deployed versions of a function (each CLI deploy creates a new version). WHEN TO USE: - Find the latest version_id before inspecting its params schema 
- `get_function_version`
- `list_function_invocations`
- `get_function_invocation`
- `get_function_invocation_logs` — Get the log lines a function invocation emitted. WHEN TO USE: - Diagnose a FAILED or stalled invocation - Trace what the function did step by step GOTCHAS: - Lo
- `list_function_builds`
- `get_function_build`
- `get_function_build_logs` — Get the log lines a function build emitted. WHEN TO USE: - See compiler/bundler output for a FAILED build GOTCHAS: - Log messages come from the build of third-p
- `list_projects`
- `get_project` — Get details of a single Browserbase project. WHEN TO USE: - Confirm a project's concurrency limit before opening many sessions - Check the default session timeo
- `get_project_usage` — Get a project's current-period usage: browser minutes and proxy bytes consumed. WHEN TO USE: - Check spend drivers before launching a large batch of sessions - 

## Install

**Verdict: review** — Installable, but 1 thing to check first: No publisher has proved control of this listing; it is indexed, not vouched for.
**Cautions** (coverage gaps and advisories — never blocking)
- No publisher has proved control of this listing; it is indexed, not vouched for.
**Config** (claude-code):
```json
"{\n  \"mcpServers\": {\n    \"mcp-server-browserbase\": {\n      \"command\": \"npx\",\n      \"args\": [\n        \"-y\",\n        \"@mindstone/mcp-server-browserbase\"\n      ]\n    }\n  }\n}"
```

## Blast radius

Extensive to critical — no credential declaration found, from the publisher, the upstream registry, or the README. Known so far: deletes data; runs on your machine.
- Floor 42, ceiling 66 (tier: unknown)
- `unknown` means the floor and ceiling land in different bands — not measured enough to name one. It does not mean low.
- This is impact, not likelihood. A high radius is not a defect: a filesystem server is supposed to write files. It is never part of the trust score.

## Machine-readable views of this entry

- Signed JSON: https://forgeregistry.com/api/v1/packages/%40mindstone%2Fmcp-server-browserbase
- Install plan: https://forgeregistry.com/api/v1/packages/%40mindstone%2Fmcp-server-browserbase/install-plan
- Alternatives: https://forgeregistry.com/api/v1/alternatives/%40mindstone%2Fmcp-server-browserbase
- HTML page: https://forgeregistry.com/registry/%40mindstone%2Fmcp-server-browserbase
- MCP: POST https://forgeregistry.com/api/mcp → `forge_get_package` / `forge_install_plan`

## About this document

Generated by Forge (https://forgeregistry.com) — a compact rendering of the same record served, signed, at the JSON URL above. Trust and scan facts are the registry's own measurements; anything Forge did not measure is named as unmeasured rather than omitted.