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.
-
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.
52 tools
How to connect
How to connect Browserbase to Claude, ChatGPT or Cursor
Two steps, about a minute.
In Elaichi
Connect Browserbase once
-
Open Connections, choose Add connection, and pick Browserbase.
-
Optionally set Share with to give a team access, then press Connect.
-
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.
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.
Connect Browserbase to Claude
-
1
Open Customize, then Connectors.
-
2
Press Add.
-
3
Name it, paste the MCP server URL, then Continue.
https://api.elaichi.ai/mcp -
4
Sign in and approve.
On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves.
Connect Browserbase to ChatGPT
-
1
Open Plugins, then press the + button.
-
2
Name it and paste the endpoint into Server URL.
https://api.elaichi.ai/mcp -
3
Leave Authentication on OAuth, then tick the risk acknowledgement.
-
4
Press Create, then sign in and approve.
Works on the web today. The plugin directory lives at chatgpt.com/plugins.
Connect Browserbase to Cursor
-
1
Open
~/.cursor/mcp.json. -
2
Add the endpoint under
mcpServers.https://api.elaichi.ai/mcp -
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
Add the endpoint as a remote MCP server.
https://api.elaichi.ai/mcp -
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.
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.”
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.
No tools match your search.
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 clientsClaude
ChatGPT
Cursor
Copy the endpoint
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
ElaichiToolsToolboxes
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
ElaichiToolboxesShared 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
ElaichiConnectionsAudit 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 logLaunching 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 Emma Laurent
-
✓
Schedule
Every weekday at 08:00
0.2s -
✓
Fetch sessions
Browserbase
1.4s -
✓
Group by owner
Transform
0.1s -
✓
Draft the digest
Agent step
Ran with 4 tools, returned a structured summary
6.2s -
Approve the digest
Needs approval
Assigned to Michael Brennan
Approve Deny -
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
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%
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 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.
Put Browserbase in front of your team
Fourteen days on Gold, no credit card. Connect it once and pick what each team can call.