Get started

Browserbase for AI agents

Browserbase runs headless Chrome browsers in the cloud so a script can automate web tasks without a team hosting its own browser infrastructure. Connect it once through Arc0, and your agent, or Claude, ChatGPT and Cursor, can use it through one MCP endpoint, limited to what each user approved.

Connect BrowserbaseSee the 33 actions ↓
Developer toolsAPI keyMCP + RESTbrowserbase.com
AUDIT LOG · BROWSERBASEPOLICY: acme-support
09:41:07 · claude · u_8f2read
browserbase_tool.list_projects
List Browserbase Projects✓ allowed · 212ms
09:41:08 · claude · u_8f2read
browserbase_tool.get_context
Get Browser Context✓ allowed · 164ms
09:41:09 · claude · u_8f2write
browserbase_tool.create_context
Create Browser Context✓ approved · approved by user
09:41:12 · claude · u_8f2destructive
browserbase_tool.delete_context
Delete a browser context✕ blocked · policy: deny
EVERY BROWSERBASE CALL, ON THE RECORD
01 · USE CASES

What agents do in Browserbase.

01

Start a browser session

Spin up a new headless browser session and get back a session ID an automation can drive.

02

Check a session before trusting it

Look up a running session's logs and debug URL before letting an automation continue further.

03

Pull a session recording

Download the replay and recording artifacts from a finished session for a teammate to review.

02 · ACTIONS

33 Browserbase actions, graded by risk.

Every Browserbase action is tagged read, write or destructive, so one policy covers the whole app and new actions inherit the right default.

read

13

Look things up. Allowed by default.

  • browserbase_tool.get_context
    Get Browser Context
  • browserbase_tool.get_project
    Get Browserbase Project
  • browserbase_tool.get_session
    Get Browser Session
  • browserbase_tool.get_extension
    Retrieve a browser extension
  • browserbase_tool.list_projects
    List Browserbase Projects
  • browserbase_tool.list_sessions
    List Browser Sessions
  • browserbase_tool.get_session_logs
    Get Session Logs
  • browserbase_tool.get_project_usage
    Get project usage statistics
  • browserbase_tool.get_session_replay
    Get Session Replay
  • browserbase_tool.get_session_debug_urls
    Get Session Debug URLs
  • browserbase_tool.get_session_replay_page
    Get Session Replay Page
  • browserbase_tool.list_recording_downloads
    List Recording Downloads
  • browserbase_tool.download_session_artifacts
    Download Session Artifacts

write

17

Create and change things. Allow, or ask the user first.

  • browserbase_tool.create_context
    Create Browser Context
  • browserbase_tool.create_session
    Create Browser Session
  • browserbase_tool.create_browser_session
    Create browser session
  • browserbase_tool.contexts_get
    Contexts get
  • browserbase_tool.sessions_get
    Sessions get
  • browserbase_tool.sessions_list
    Sessions list
  • browserbase_tool.contexts_create
    Contexts create
  • browserbase_tool.contexts_update
    Update Browser Context
  • browserbase_tool.release_session
    Release Browser Session
  • browserbase_tool.sessions_update
    Sessions update
  • browserbase_tool.upload_extension
    Upload Browser Extension
  • browserbase_tool.sessions_get_logs
    Sessions get logs
  • browserbase_tool.sessions_get_debug
    Sessions get debug
  • browserbase_tool.upload_session_file
    Upload Session File
  • browserbase_tool.upload_session_files
    Upload Session Files
  • browserbase_tool.sessions_get_downloads
    Sessions get downloads
+ 1 MORE

destructive

3

Delete, cancel or archive. Ask first, or deny outright.

  • browserbase_tool.delete_context
    Delete a browser context
  • browserbase_tool.delete_extension
    Delete a browser extension
  • browserbase_tool.delete_session_downloads
    Delete Session Downloads
03 · HOW IT WORKS

Browserbase in three steps.

  1. 01Your users connect BrowserbaseThey add their Browserbase api key on Arc0 Connect, under your brand. It goes straight into the vault.
  2. 02You set the rulesReads run, writes like “create Browser Context” can wait for the user, and “delete a browser context” can be denied outright.
  3. 03Any agent can actYour agent calls Browserbase through the Arc0 SDK or MCP, and so can Claude, ChatGPT and Cursor. Every call lands on the audit log.
POLICY.TS
await arc0.policies.set('browserbase_tool', {
  read: 'allow',
  write: 'ask',        // create_context
  destructive: 'deny',  // delete_context
})

# Claude Code: the same connection, one URL
$ claude mcp add --transport http arc0 \
    https://mcp.arc0.ai/u/u_8f2
04 · AUTH AND DATA

How Browserbase connects.

Users add their Browserbase api key on Arc0 Connect. It is encrypted in the vault, never shown to the model, and each user can rotate or revoke it at any time.

The same Browserbase connection serves your agent over MCP and your own backend over REST and the proxy, so a user connects once. How Arc0 handles credentials →

AUTH
API key
CREDENTIALS
Per-tenant encrypted vault
MODEL SEES
Results only, never credentials
AUDIT LOG
Every call, on every plan
05 · WORKS WITH

Use Browserbase from any agent.

Claude
ChatGPT
Cursor
Codex
VS Code
OpenAI Agents SDK
Claude Agent SDK
Vercel AI SDK
Mastra
LangGraph
06 · RELATED

More developer tools apps.

GitHub896 actionsSupabase129 actions0CodeKit8 actionsAbly25 actionsAbstract3 actionsAddressfinder17 actionsAddresszen2 actionsAlchemy36 actions
ALL DEVELOPER TOOLS APPS →
07 · FAQ

Browserbase and Arc0, answered.

Q01

Can I use Browserbase with Claude, ChatGPT or Cursor?

Yes. Connect Browserbase to Arc0 once, then add your Arc0 MCP URL to Claude, ChatGPT, Cursor, Claude Code or any other remote-MCP client. Each assistant only gets the Browserbase actions you allow.

Q02

How do users connect Browserbase?

Users add their Browserbase api key on Arc0 Connect. It is encrypted in the vault, never shown to the model, and each user can rotate or revoke it at any time.

Q03

Which Browserbase actions can my agent take?

33 in total: 13 read, 17 write and 3 destructive, such as “create Browser Context”. Your policies decide which of them each agent may call.

Q04

Can I stop my agent from deleting things in Browserbase?

Yes. Actions like “delete a browser context” are graded destructive. Set destructive actions to deny, or to ask so the user approves each one, and blocked calls still show up on the audit log.

Q05

Can my own backend call Browserbase too?

Yes. The same Browserbase connection is available over REST and through the Arc0 proxy, so your product and your agent share one connection per user.

Get started

Plug Browserbase into your agent.

Your users connect Browserbase once, under your brand. Your agent gets 33 actions behind your policies, with every call on the record.

Connect BrowserbaseBrowse all apps →

Free to build · MCP + REST · Audit log on every plan