Be the first to get access to new connectors. Get early access →
ConnectorBay Early access
Discover
Browserbase (BYOK) icon

Browserbase (BYOK)

Read your Browserbase projects, browser sessions, session logs, usage, functions, webhooks and agent runs with your own API key

Unify Dynamics LLC

Tools9read-only
Sign-inBYOKbring your own key
Key keptNeverused for one call only
PriceFreeoptional Pro limits
ProviderBrowserbaseunofficial, not affiliated
Works withMCP · RESTany agent

Try asking

Real questions, and the tools your agent calls to answer them.

Which Browserbase projects do I have and what is their concurrency limit?
Tools called
list_projects
Show the settings of my Browserbase project
Tools called
get_project
How many browser minutes has my Browserbase project used?
Tools called
get_project_usage
Which Browserbase sessions are running right now?
Tools called
list_sessions
Show the details of one Browserbase session
Tools called
get_session
What did my Browserbase session do, step by step?
Tools called
get_session_logs

About

Browserbase (BYOK) lets an AI assistant read your own Browserbase data through the Browserbase API with a key you supply (API key). Read-only: 9 tools (list_projects, get_project, get_project_usage, list_sessions, get_session, get_session_logs, list_functions, list_webhooks, list_agent_runs). The BYOK key travels with each request, is used for that one call only and is never stored, logged or cached; it is only ever sent to api.browserbase.com. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Browserbase. Browserbase and its logos are trademarks of their owners and are used only to say which service the connector works with.

Sources: Live from the Browserbase API (api.browserbase.com) with a BYOK key; documentation: https://docs.browserbase.com/reference/api/overview. Endpoints checked against that documentation on 2026-10-16.

Privacy

The publisher, Unify Dynamics LLC, states that tool inputs are processed in memory and not retained.

Data not collectedNo account, no profile, no stored prompts or results.

What it can do

9 tools, grouped by job. Every one is read-only or compute-only.

OpenAPI
Read your data9 tools
  • List projectsList the projects the key can see with name, default timeout and concurrency limit.
  • Get projectGet one project: name, default session timeout in seconds and concurrency limit.
  • Get project usageShow a project's usage: browser minutes used and proxy bytes transferred.
  • List sessionsList browser sessions of the project the key belongs to, optionally by status or a user-metadata query, with status, region, timing and proxy bytes.
  • Get sessionGet one browser session: status, region, timing, expiry, proxy bytes, context and user metadata (connection URLs and signing keys are not returned).
  • Get session logsGet the recorded browser protocol log of a session (method, page, request and response timestamps); can be long.
  • List functionsList deployed Browserbase functions with name and update time (offset paging).
  • List webhooksList the project's webhooks with endpoint URL and event types, newest first (signing secrets are not included).
  • List agent runsList agent runs with status, task, start and end times and failure cause, optionally by status or agent.

Information

PublisherUnify Dynamics LLC
CategoryDeveloper tools
LanguagesEnglish
Built forWorldwide
CompatibilityAny MCP client · any agent · REST
Version0.1.0
MCP endpointhttps://byok-browserbase.connectorbay.com/mcp
REST APIopenapi.json
SupportGet help · Status
CountryWorldwide
FunctionOther
LayerDeep connectors

Connect it to your agent

Three ways in, the same 9 tools.

MCP (Claude, Cursor, Windsurf, VS Code, any MCP client)https://byok-browserbase.connectorbay.com/mcp
RESTPOST https://byok-browserbase.connectorbay.com/v1/tools/<tool>
OpenAI function callinghttps://connectorbay.com/openai/byok-browserbase.json
OpenAI-compatible chathttps://connectorbay.com/v1/chat/completions · how it works
  • Add the MCP URL in your client's connector, MCP or integration settings (streamable HTTP, no OAuth).
  • Key: send your API key in the X-Upstream-Key header (get one at www.browserbase.com).
  • Ask a question; the agent picks the right tool and answers from the live data.

Browserbase connector: questions and answers

What is the Browserbase connector?

Browserbase (BYOK) lets an AI assistant read your own Browserbase data through the Browserbase API with a key you supply (API key). It is a hosted MCP server with 9 tools such as List projects, Get project, Get project usage, List sessions, Get session, Get session logs, published by Unify Dynamics LLC. It is independent and not affiliated with Browserbase.

How do I connect Browserbase to Claude, ChatGPT or Cursor?

Add the MCP endpoint https://byok-browserbase.connectorbay.com/mcp to your client's MCP, connector or integration settings (streamable HTTP, no OAuth). For REST, POST JSON to https://byok-browserbase.connectorbay.com/v1/tools/<tool>; the OpenAPI description is at /openapi.json. For OpenAI function calling, load https://connectorbay.com/openai/byok-browserbase.json.

Do I need a Browserbase account or API key?

Yes: this is a bring-your-own-key connector. Create a API key at https://www.browserbase.com/settings and send it in the X-Upstream-Key header. ConnectorBay uses it for that one call only and never stores, logs or caches it.

Is Browserbase read-only?

Yes. Every tool reads or computes. Nothing is created, changed, sent, paid or deleted in your account.

Is the Browserbase connector free?

Yes. It is free to use within the published rate limits; an optional Pro key raises them. There is no account to create.

More like this

More in Other

Grafana Cloud (BYOK)

Read your Grafana Cloud dashboards, folders, data sources, alert rules, annotations and teams with BYOK

Live · MCP + REST10 tools

Grafana Alerting (BYOK)

Read your Grafana Cloud alerting setup (contact point names, notification policies, mute timings, message templates, alert rules and rule groups) with your own service account token

Live · MCP + REST8 tools

Grafana Cloud (BYOK)

Read your Grafana Cloud access policies (names, scopes, realms and status) and the scopes the access policy API offers with your own access policy token

Live · MCP + REST5 tools

Grafana Cloud (BYOK)

Read your Grafana Cloud organization record, settings, monthly billed usage by dimension and usage history with your own access policy token

Live · MCP + REST5 tools

Grafana Cloud (BYOK)

Read your Grafana Cloud stacks, their regions, readiness, connection endpoints, usage counts and installed plugins with your own access policy token

Live · MCP + REST7 tools

Grafana Content (BYOK)

Read your Grafana Cloud library panels, playlists, dashboard tags and versions, public dashboard list and snapshots with your own service account token

Live · MCP + REST9 tools

Documentation

Back to top

Browserbase (BYOK) — connector documentation

  • MCP endpoint: https://byok-browserbase.connectorbay.com/mcp
  • REST API: POST https://byok-browserbase.connectorbay.com/v1/tools/{tool_name}, described by the OpenAPI 3.1 spec at https://byok-browserbase.connectorbay.com/openapi.json
  • Transport: Streamable HTTP, stateless, MCP specification 2025-06-18 or later
  • Authentication: your own Browserbase API key, sent in the X-Upstream-Key header of every request (never stored, logged or cached)
  • Health: https://byok-browserbase.connectorbay.com/health · Tool schemas: https://byok-browserbase.connectorbay.com/tools.json
  • Publisher: Unify Dynamics LLC · connectorbay.com/byok-browserbase · agent@connectorbay.com

What Browserbase (BYOK) is for

Browserbase (BYOK) lets an AI assistant read your own Browserbase data through the Browserbase API with a key you supply (API key). Read-only: 9 tools (list_projects, get_project, get_project_usage, list_sessions, get_session, get_session_logs, list_functions, list_webhooks, list_agent_runs). The BYOK key travels with each request, is used for that one call only and is never stored, logged or cached; it is only ever sent to api.browserbase.com. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Browserbase. Browserbase and its logos are trademarks of their owners and are used only to say which service the connector works with.

Ask your assistant things like:

  • "Which Browserbase projects do I have and what is their concurrency limit?"
  • "Show the settings of my Browserbase project"
  • "How many browser minutes has my Browserbase project used?"
  • "Which Browserbase sessions are running right now?"
  • "Show the details of one Browserbase session"
  • "What did my Browserbase session do, step by step?"

What it does

  • list_projects: List the projects the key can see with name, default timeout and concurrency limit.
  • get_project: Get one project: name, default session timeout in seconds and concurrency limit.
  • get_project_usage: Show a project's usage: browser minutes used and proxy bytes transferred.
  • list_sessions: List browser sessions of the project the key belongs to, optionally by status or a user-metadata query, with status, region, timing and proxy bytes.
  • get_session: Get one browser session: status, region, timing, expiry, proxy bytes, context and user metadata (connection URLs and signing keys are not returned).
  • get_session_logs: Get the recorded browser protocol log of a session (method, page, request and response timestamps); can be long.
  • list_functions: List deployed Browserbase functions with name and update time (offset paging).
  • list_webhooks: List the project's webhooks with endpoint URL and event types, newest first (signing secrets are not included).
  • list_agent_runs: List agent runs with status, task, start and end times and failure cause, optionally by status or agent.

BYOK key

You bring your own Browserbase API key (https://www.browserbase.com/settings). Your assistant sends it in the X-Upstream-Key header with each request. ConnectorBay uses it for that one call only: it is never stored, logged or cached, never shown in an answer, and it is only sent to api.browserbase.com over https, with no redirects followed. Create a key with the fewest permissions the tools need (read-only if the provider offers it), and revoke it at the provider whenever you like.

Notices

Read-only: this connector never creates sessions, fetches pages, runs searches or starts agents, so it does not use up browser time.

Data sources

Live from the Browserbase API (api.browserbase.com) with a BYOK key; documentation: https://docs.browserbase.com/reference/api/overview. Endpoints checked against that documentation on 2026-10-16.

What it is not

Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Browserbase. Browserbase and its logos are trademarks of their owners and are used only to say which service the connector works with. It is read-only: it never creates, changes, sends or deletes anything in your Browserbase account.

Built for: Worldwide. Languages: English.

Privacy policy

Back to top

Browserbase (BYOK) — Privacy Policy

Effective 24 October 2026. Unify Dynamics LLC ("we", "us"), Menlo Park, California.

What Browserbase (BYOK) is. Browserbase (BYOK) is a connector (an MCP server and REST API) that an AI assistant calls on your behalf to read your own Browserbase data: Read your Browserbase projects, browser sessions, session logs, usage, functions, webhooks and agent runs with your own API key. You bring your own Browserbase API key; the assistant sends it to us with each request.

BYOK key. The key you supply is used to make the one Browserbase call you asked for. Our application does not store it, write it to a log, put it in a cache, or share it. It is sent only to api.browserbase.com, over https, and is removed from any text we return to you or your assistant. We do not follow redirects with your key. If Browserbase rejects it, we say so without repeating it.

What we receive. The arguments of each tool call, the BYOK key (for that call only), the technical headers needed to serve the request (an IP address or a client identifier supplied by the assistant) and standard server logs. What Browserbase receives. The request we make on your behalf, including the key and the arguments, under Browserbase's own terms and privacy policy. Browserbase acts at your direction and is the only recipient of the data of your request besides our hosting provider.

What we return. The answer Browserbase gives for your request, trimmed to the fields the tool documents. We do not keep it: it is returned to your assistant and not stored, cached or used to train anything.

What we do not do. We do not build a profile, sell or share personal information, or keep your Browserbase data. Rate-limit counters (a client identifier and timestamps) are held in memory for at most 24 hours. Hosting access logs (IP addresses, request paths and status codes) are kept for up to 30 days for security and abuse prevention; our application adds no request headers or bodies to them.

Sub-processors. Browserbase (the API you call with a BYOK key, at your direction). Hosting: Vercel (United States regions).

Your rights. Because we store no personal data beyond short-lived logs, requests to access, correct or delete data are usually satisfied automatically; you can still contact agent@connectorbay.com and we will respond within 30 days. Revoke your key at Browserbase at any time to end all access.

Children. Browserbase (BYOK) is a general-audience service operated by the adult using the assistant, under Browserbase's own age rules.

Changes. We will post changes here with a new effective date.

Terms of service

Back to top

Browserbase (BYOK) — Terms of Service

Effective 24 October 2026. These terms govern use of the Browserbase (BYOK) connector ("the Service") operated by Unify Dynamics LLC ("we", "us").

  1. The Service. Browserbase (BYOK) provides: Read your Browserbase projects, browser sessions, session logs, usage, functions, webhooks and agent runs with your own API key. It is accessed through an AI assistant or directly over MCP or HTTP, and is read-only.
  2. Your own key, your own account. You must use your own Browserbase credentials and only access data you are allowed to access. Browserbase's terms apply to your use of Browserbase; you are responsible for complying with them, including any rate limits and permitted uses. Do not share a key you do not own.
  3. Independent. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Browserbase. Browserbase and its logos are trademarks of their owners and are used only to say which service the connector works with.
  4. No advice, no guarantees. Output is the data Browserbase returns, lightly trimmed; it may be incomplete, delayed or changed by Browserbase. Check important facts at the source.
  5. Read-only. The Service does not create, change, send or delete anything in your Browserbase account.
  6. Acceptable use. Automated use within the published rate limits is welcome. Do not use the Service to access data you are not entitled to, to circumvent Browserbase's controls, or to attack any system.
  7. Availability. The Service is provided "as is" without warranty. We may change, limit or discontinue it at any time; Browserbase may change or end its API at any time.
  8. Data. Our Privacy Policy describes what we process. In short: the BYOK key is used for the one call and not stored or logged.
  9. Pro keys. Optional ConnectorBay Pro API keys are issued at our discretion and are separate from your Browserbase key.
  10. Liability. To the fullest extent permitted by law, Unify Dynamics LLC is not liable for any loss arising from use of or reliance on the Service, including any action Browserbase takes on your account. Our total liability is limited to US $100.
  11. Governing law. California law; venue in San Mateo County, California.
  12. Contact. Unify Dynamics LLC · agent@connectorbay.com · https://connectorbay.com/byok-browserbase

Browserbase (BYOK) support

Email agent@connectorbay.com. We answer within two business days.

When you report a problem, include the question you asked your agent, roughly when, and which agent you used (for example Claude, ChatGPT or Gemini). Never send us passwords, account numbers or ID numbers. Browserbase (BYOK) never asks for them.

Get Browserbase (BYOK)

Free · BYOK · Read-only

BYOK: bring your own keyThis connector uses your own Browserbase API key. Create one at https://www.browserbase.com/settings, with the fewest permissions it needs (read-only if the provider offers it). Your assistant sends it in the X-Upstream-Key header with every request. It is used for that one call only: never stored, logged or cached, and only ever sent to Browserbase. Revoke it at the provider whenever you like. Unofficial connector: not affiliated with Browserbase.