Browserbase MCP integration for AI agents.
Connect AI agents to Browserbase through 11 structured actions, including get context, create context, delete context, and request session release. Review au…
- ACTION CONTRACTS
- 11
- AUTHENTICATION
- API key
- SOURCE STATUS
- Provider-backed
CATALOG SOURCE REVIEWED AUGUST 23, 2026 / ACTION NAMES AND SCHEMAS DERIVED FROM WORKING MACHINES PROVIDER SOURCE
CAPABILITY PROFILE
What the Browserbase integration exposes
The Browserbase Agent App exposes 11 provider-backed actions for developer tools work. Its current contract lets an authorized agent get one browserbase context by context identifier, create a browserbase context and return the upload credentials for an encrypted user-data directory, and delete one browserbase context by context identifier. These operations are called through Working Machines as typed capabilities rather than through browser navigation or copied UI steps.
A connection uses API key. Before execution, the agent can inspect the selected action, its required fields, declared scopes, and expected output contract. Provider credentials remain inside the Working Machines runtime; the calling agent receives the capability and its structured result, not the underlying secret.
For reliable operation, start with the narrowest action that satisfies the task, resolve stable provider identifiers before changing state, and validate the returned object or status after execution. Availability still depends on the connected Browserbase account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real Browserbase capabilities.
Showing 11 of 11 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
get_contextREADGet one Browserbase context by context identifier.
INPUTS: id
create_contextWRITECreate a Browserbase context and return the upload credentials for an encrypted user-data directory.
INPUTS: projectId
delete_contextHIGH IMPACTDelete one Browserbase context by context identifier.
INPUTS: id
request_session_releaseREVIEWRequest that Browserbase releases a session before timeout by sending status REQUEST_RELEASE.
INPUTS: id / projectId
create_sessionWRITECreate a Browserbase session using the connected project by default, with optional context reuse and persistence.
INPUTS: projectId / timeout / keepAlive / region / userMetadata
get_projectREADGet one Browserbase project by project identifier.
INPUTS: id
get_project_usageREADGet Browserbase browser minute and proxy byte usage for one project, defaulting to the connected project.
INPUTS: id
get_sessionREADGet one Browserbase session by session identifier.
INPUTS: id
list_projectsREADList the Browserbase projects visible to the current API key.
list_sessionsREADList Browserbase sessions with optional status or metadata query filters.
INPUTS: status / q
refresh_context_upload_credentialsWRITERefresh the Browserbase upload credentials for an existing context so a new encrypted archive can be uploaded.
INPUTS: id
INPUT CONTRACTS
Know what the action needs before it runs.
get_context
idREQUIRED- The Browserbase context identifier.
create_context
projectIdOPTIONAL- The Browserbase project identifier. When omitted, the connected project is used.
delete_context
idREQUIRED- The Browserbase context identifier.
request_session_release
idREQUIRED- The Browserbase session identifier.
projectIdOPTIONAL- The Browserbase project identifier. When omitted, the connected project is used.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Get Context
Get one Browserbase context by context identifier. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
get_contextControl Create Context
Create a Browserbase context and return the upload credentials for an encrypted user-data directory. Resolve the target first, present material changes for confirmation, and make retries idempotent where the provider supports it.
create_contextVerify with Get Project
Get one Browserbase project by project identifier. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
get_projectSAFETY BOUNDARY
Operate Browserbase with explicit limits
- Authorize Browserbase with API key and grant only the provider access required by the selected actions.
- 4 actions are change-capable by name. Confirm the target identity and material parameters before allowing a write.
- Treat `delete_context` as high-impact operations and require an explicit approval boundary.
- No provider scope string is declared on the sampled actions. Verify the connected account's actual permissions in Browserbase rather than assuming unrestricted access.
- After a call, inspect the structured result and execution record before reporting that the Browserbase task completed successfully.
CONNECTION MODEL
API key
Browserbase API key used with the X-BB-API-Key header. Find it in Browserbase Dashboard Settings: https://docs.browserbase.com/introduction/getting-started.
Working Machines stores provider credentials behind the execution boundary. An agent can use an authorized connection identity, but catalog discovery alone does not reveal OAuth tokens, API keys, or provider secrets.
- READ SIGNALS
- 6
- WRITE SIGNALS
- 3
- HIGH IMPACT
- 1
- REVIEW SIGNALS
- 1
EVIDENCE AND AVAILABILITY
Provider reference
Action names, input fields, authentication types, and counts on this page are generated from the Working Machines provider catalog. Provider behavior, quotas, object semantics, account eligibility, and regional availability remain governed by Browserbase.