Skip to content

Application Development

Browserbase MCP connector

Connecting Browserbase to Elaichi lets Claude, ChatGPT, Cursor, or the Elaichi Agent start and review browser sessions, pull recordings and logs, manage saved contexts and projects, and check usage, all inside each person's own Browserbase access.

Connect on Elaichi How to connect

  • How it connects. Connects with an API key. The credential goes into a vault nobody reads back.

  • One address. https://api.elaichi.ai/mcp, the same for every user.

  • Their own access. An agent never gets more than the person it acts for.

How to connect

How to connect Browserbase to Claude, ChatGPT or Cursor

Two steps, about a minute.

1

In Elaichi

Connect Browserbase once

  1. Open Connections, choose Add connection, and pick Browserbase.

  2. Optionally set Share with to give a team access, then press Connect.

  3. Paste a Browserbase API key. One person generates a token in Browserbase and pastes it once. Everyone else works through Share with, and never sees it.

The credential is vaulted. Nobody reads it back, not even the AI.

Add connection

Choose a connector.

browserbase
Browserbase
Apache Airflow
Apify
Boomi
Caspio
Cloudflare
2

In your AI client

Point it at one endpoint

Everyone in the organization uses the same address, and each person only ever reaches what their own account allows.

Browserbase MCP connector for Claude

  1. 1

    Open Customize, then Connectors.

  2. 2

    Press Add.

  3. 3

    Name it, paste the MCP server URL, then Continue.

    https://api.elaichi.ai/mcp
  4. 4

    Sign in and approve.

On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves.

Browserbase MCP connector for ChatGPT

  1. 1

    Open Plugins, then press the + button.

  2. 2

    Name it and paste the endpoint into Server URL.

    https://api.elaichi.ai/mcp
  3. 3

    Leave Authentication on OAuth, then tick the risk acknowledgement.

  4. 4

    Press Create, then sign in and approve.

Works on the web today. The plugin directory lives at chatgpt.com/plugins.

Browserbase MCP connector for Cursor

  1. 1

    Open ~/.cursor/mcp.json.

  2. 2

    Add the endpoint under mcpServers.

    https://api.elaichi.ai/mcp
  3. 3

    Reload Cursor, then sign in and approve.

~/.cursor/mcp.json

{
  "mcpServers": {
    "elaichi": {
      "url": "https://api.elaichi.ai/mcp"
    }
  }
}

Set up per machine, so repeat it on each computer you work from.

Connect Browserbase to any MCP client

  1. 1

    Add the endpoint as a remote MCP server.

    https://api.elaichi.ai/mcp
  2. 2

    Sign in and approve.

{
  "mcpServers": {
    "elaichi": {
      "url": "https://api.elaichi.ai/mcp"
    }
  }
}

The Elaichi Agent already has these tools, with nothing to set up.

Connect Browserbase on Elaichi See pricing

Use cases

What teams do with Browserbase through Elaichi

Every one of these runs inside the access the person already has, and lands in the same audit log.

  • Engineering

    Find out why a browser run failed

    Ask for the logs and debug links from the Browserbase session that broke overnight, then open the replay to see the exact page where it stopped.

  • QA

    Review last night's test sessions in one place

    List the Browserbase sessions from the latest run, pull their recordings, and get a plain summary of which ones finished cleanly and which did not.

  • Data

    Start a fresh browser for a collection job

    Spin up a new Browserbase session in the right project, upload the file the job needs, and request a recording download when it is done.

  • Platform

    Keep saved browser contexts tidy

    Create a Browserbase context for a reusable login state, update it when credentials rotate, and delete the ones nobody has used in months.

  • Operations

    Check project usage before the invoice lands

    Ask how much browser time each Browserbase project has used this month and which ones are climbing fastest, without opening the dashboard.

  • Support

    Confirm what an agent did for a customer

    Look up a Browserbase agent or session by its ID, walk through the replay page by page, and tell the customer exactly what happened.

Try asking

  • “Summarize Browserbase sessions started this week by team.”
  • “Which Browserbase sessions ran longest yesterday?”
  • “List Browserbase contexts and the sessions using them.”

See all 52 Browserbase tools below

Compare

Elaichi vs Zapier MCP vs Composio for Browserbase

All three can connect Browserbase to an AI assistant, and all three have admin controls. They differ in where access lives and how you pay.

Elaichi compared with Zapier MCP and Composio for Browserbase, by what to check
What to check Elaichi Zapier MCP Composio
Where the AI connects One address for the whole organization. https://api.elaichi.ai/mcp A server per member, created at sign-in. An MCP endpoint per team, or an SDK.
Control over Browserbase tools Allow or restrict single Browserbase tools, per role or user. App and action restrictions on the account. Role permissions, down to the action.
Record of calls One audit entry per Browserbase call. A History tab of tool calls. A log of every tool call.
Single sign-on SAML or OIDC, plus SCIM, on Gold. SAML on Enterprise. SAML and OIDC on Enterprise.
Price $15 per user per month. 2 tasks per successful call. Billed per tool call.

Sources: Zapier MCP docs, security, usage; Composio docs, gateway, enterprise, pricing. Checked September 2026.

Longer take: Zapier MCP alternative and when you don't need an MCP gateway.

AI tools

Browserbase tools for your AI agents

52 tools are ready to call through Elaichi's MCP endpoint the moment you connect Browserbase, governed by the same roles, restrictions, and audit log as everything else in Elaichi.

See it in Elaichi

What connecting Browserbase gets you

6 screens from the product, each doing one job for your Browserbase account.

The agent

Ask about Browserbase sessions in plain language.

The agent reads live sessions, logs and recordings, then answers in one place.

  • sessions
  • contexts
  • recordings
  • logs

Ask Elaichi to work across your apps.

Summarize Browserbase sessions started this week by team.

Which Browserbase sessions ran longest yesterday?

List Browserbase contexts and the sessions using them.

Also runs in Claude, ChatGPT or Cursor

MCP clients

One Browserbase endpoint, every MCP client.

Claude, ChatGPT and Cursor connect over OAuth, no SDK and no shared API key.

ElaichiMCP clients
Claude ChatGPT Cursor

Copy the endpoint

https://api.elaichi.ai/mcp
Client Connected by Status Last used
Claude
E

Emily Carter

 • Connected 4 minutes ago
Cursor
M

Megan Brooks

 • Connected 2 hours ago
ChatGPT
R

Ryan Hayes

 • Connected Yesterday

Tool catalog

52 Browserbase tools, ready without custom code.

Sessions, contexts, recordings, replays, logs and uploads, each with its methods listed.

  • Create a Browserbase session
  • List all Browserbase sessions
  • Get single Browserbase session by ID
  • Update a Browserbase session by ID
ElaichiTools
Tool Action Description
Create a Browserbase session Create Create a new Browserbase session with optional browser settings, proxy configuration, region, and user metadata. Returns: id, createdAt, updatedAt, projectId, startedAt, expiresAt, proxyBytes, keepAlive, connectUrl, seleniumRemoteUrl, signingKey, endedAt, contextId, userMetadata. All body fields are optional; if projectId is omitted it is inferred from the API key. Timeout must be between 60 and…
List all Browserbase sessions List List Browserbase sessions, optionally filtered by status or a user metadata query. Returns: id, createdAt, updatedAt, projectId, startedAt, expiresAt, proxyBytes, keepAlive, connectUrl, seleniumRemoteUrl, signingKey, endedAt, contextId, userMetadata.
Get single Browserbase session by ID Get Get a single Browserbase session by id. Returns: id, createdAt, updatedAt, projectId, startedAt, expiresAt, proxyBytes, keepAlive, connectUrl, seleniumRemoteUrl, signingKey, endedAt, contextId, userMetadata. Required: id.
Update a Browserbase session by ID Update Close or update a Browserbase session by id. Send status REQUEST_RELEASE to end the session before its timeout and avoid unnecessary usage charges. Returns: id, createdAt, updatedAt, projectId, startedAt, expiresAt, proxyBytes, keepAlive, connectUrl, seleniumRemoteUrl, signingKey, endedAt, contextId, userMetadata. Required: id, status.
Browserbase sessions get logs Get Retrieve Chrome DevTools Protocol (CDP) logs for a Browserbase session. Returns: method, pageId, sessionId, request, response, timestamp, frameId, loaderId. Required: session_id.

Toolboxes

Every team gets its own Browserbase toolbox.

Curate one toolbox per team so each group sees only relevant Browserbase tools.

  • Platform engineering
  • QA
  • Data extraction
  • Support
ElaichiToolboxes
Name Source template Tools Created

Platform engineering toolbox

Browserbase · sessions and contexts

 Browserbase starter 18 Mar 4, 2026

QA toolbox

Browserbase · replays and recordings

 — 9 Mar 2, 2026

Data extraction toolbox

Browserbase · sessions and uploads

 — 24 Feb 27, 2026

Support toolbox

Browserbase · logs and debug urls

 Browserbase starter 6 Feb 19, 2026

Growth engineering toolbox

Browserbase · scheduled session runs

 — 31 Jan 30, 2026

Security toolbox

Browserbase · session audit and access

 — 12 Jan 22, 2026

Shared connections

Teammates run sessions without seeing a key.

Each Browserbase connection shows who connected it and which teams and members use it.

  • Platform prod
  • QA staging
  • Data extraction
  • Support tooling
ElaichiConnections
Connection Scope Status Access
BR

Browserbase (Platform prod)

Connected by Emily Carter

 Personal • Active 1 team · 6 members
BR

Browserbase (QA staging)

Connected by Jake Morgan

 Organization • Active 3 teams · 24 members
BR

Browserbase (Data extraction)

Connected by Megan Brooks

 Organization • Active 2 teams · 11 members
BR

Browserbase (Support tooling)

Connected by Tyler Reed

 Personal • Needs re-auth 1 team · 3 members
BR

Browserbase (Growth experiments)

Connected by Ryan Hayes

 Personal • Active Not shared
BR

Browserbase (Security review)

Connected by Ashley Parker

 Personal • Active 2 teams · 9 members

Audit log

Every Browserbase call is on the record.

Append-only entries show when, who, what happened, the type and the resource touched.

  • When
  • Who
  • What happened
  • Type
ElaichiAudit log
When Who What happened Type

2 minutes ago

Mar 6, 2026, 3:10 PM
E

Emily Carter

emily.carter@northwind.io

 Restriction Created Access

8 minutes ago

Mar 6, 2026, 3:04 PM
J

Jake Morgan

jake.morgan@northwind.io

 Restriction Updated Access

14 minutes ago

Mar 6, 2026, 2:58 PM
M

Megan Brooks

megan.brooks@northwind.io

 Role Assigned Access

20 minutes ago

Mar 6, 2026, 2:52 PM
T

Tyler Reed

tyler.reed@northwind.io

 Browserbase Users Updated MCP

26 minutes ago

Mar 6, 2026, 2:46 PM
R

Ryan Hayes

ryan.hayes@northwind.io

 Browserbase Sessions Created MCP

32 minutes ago

Mar 6, 2026, 2:40 PM
A

Ashley Parker

ashley.parker@northwind.io

 Browserbase Sessions List Toolbox

Launching soon

From answering questions to doing the work

A person no longer has to ask. A trigger starts the work, inside the same permissions and the same audit log as everything else. Automations and live dashboards are launching soon, on the Black plan.

Automations

A schedule runs Browserbase work end to end.

Six steps fetch sessions, group them, draft a digest, get approval, post back.

Browserbase digest

Run 418 · started 2 minutes ago · on behalf of Emily Carter

  1. ✓

    Schedule

    Every weekday at 8:00 AM

    0.2s
  2. ✓

    Fetch sessions

    Browserbase

    1.4s
  3. ✓

    Group by owner

    Transform

    0.1s
  4. ✓

    Draft the digest

    Agent step

    Ran with 4 tools, returned a structured summary

    6.2s

  5. Approve the digest

    Needs approval

    Assigned to Michael Brennan

    Approve

  6. Post the digest

    Browserbase

    Queued

Collections and dashboards

Browserbase health, computed on a schedule.

Four metrics, 14 days of sessions created and a team breakdown, no model involved.

Browserbase health

Refreshed 4 minutes ago · every 15 minutes · from the sessions collection

Live

Sessions

1,284 ↓ 12%

Contexts

96 ↓ 8%

Needs attention

3 ↑ 2

Updated this week

412 ↑ 9%

Sessions created

Last 14 days

By team

Share of activity

Platform prod 34%

QA staging 27%

Data extraction 21%

Support tooling 18%

Related connectors

More from the catalog

Browse all 600+ connectors →

FAQ

Frequently asked questions

How do I connect Browserbase to Claude?

Two steps. In Elaichi, choose Browserbase and paste in an API key from your Browserbase dashboard, which is the whole sign-in step, with no OAuth application to register and no client ID or secret to generate. Then in Claude, open Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp. Claude can now work with your Browserbase sessions, contexts, projects, and agents as you.

Does Browserbase work with ChatGPT and Cursor as well as Claude?

Yes. Once Browserbase is connected in Elaichi, the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, any other MCP client, and the Elaichi Agent. You connect Browserbase once and every client you use picks it up.

What can an AI agent actually do with my Browserbase data?

It can start a new Browserbase session, list the ones already running or finished, and pull the logs, debug links, recordings, and page-by-page replays from any of them. It can also create, update, and delete saved contexts, look up projects and their usage, and manage Browserbase agents. Because Browserbase exposes a lot of actions, short concrete asks like "show me the logs for the session that failed this morning" work better than long instructions.

Does connecting Browserbase give the AI access to every project?

No. The AI works inside whatever the Browserbase API key you connected can already reach, so it sees the projects, sessions, and contexts that key is allowed to see and nothing more. Elaichi can narrow that access further by team or by action, and it never widens it beyond what Browserbase itself permits.

Can my team share one Browserbase connection?

Yes. One person connects Browserbase in Elaichi and shares the connection with a team, and nobody else ever handles the API key. Each teammate still signs in to Elaichi as themselves, so every session they start or recording they pull is recorded in the audit log under their own name.

Can I stop an agent from deleting or changing things in Browserbase?

Yes. Restrictions in Elaichi apply per action, so you can allow reading Browserbase sessions, logs, and replays while blocking deleting contexts, removing agents, or updating a session. A blocked action is never shown to Claude, ChatGPT, or Cursor at all, so no prompt, however worded, can reach it.

What happens to a Browserbase connection when someone leaves?

When you offboard someone in Elaichi, their access to Browserbase through Elaichi ends immediately, along with everything else they were connected to. A shared Browserbase connection keeps working for the rest of the team. If you ever want to remove Browserbase entirely, disconnecting it once in Elaichi removes it from Claude, ChatGPT, Cursor, and every other client at the same time.

Does the Browserbase MCP connector work with Gemini, Codex, Claude Code or other MCP clients?

Yes. Browserbase is reached over the same MCP endpoint every client uses, so anything that speaks MCP can call it — Gemini, Codex, Claude Code, Windsurf, Cline, Zed and OpenCode among them — alongside Claude, ChatGPT, Cursor, and the Elaichi Agent. The tools on offer and the access behind them are identical whichever client asks. Only the setup screen differs.

Is Elaichi an alternative to Zapier MCP for Browserbase?

Yes. Both let Claude, ChatGPT or Cursor use Browserbase. Zapier MCP fits a team that already automates in Zapier, since each person signs in and acts as themselves in that account. Elaichi fits when IT wants one address for the whole company, per-tool rules by role, and a record of every Browserbase call.

How is Elaichi different from Composio for Browserbase?

Composio gives AI agents tools and sign-in handling across 1,000+ apps, for developers building agents or people using an assistant, billed per tool call. Elaichi gives a company's own people governed access to Browserbase: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.

Put Browserbase in front of your team

14 days on Gold, no credit card. Connect it once and pick what each team can call.

Connect Browserbase Talk to us
Works with
Claude ChatGPT Cursor and any other MCP client, or the Elaichi Agent.
When the trial ends
Nothing is deleted. Connections, roles and the audit log stay where they are, so subscribing picks up exactly where you left off.