Use Browserbase from Claude
Add the Browserbase connection to a Space that runs Claude, then use it from every channel in that Space.
ConnectorBrowserbase
Browserbase integration for Claude and Codex
Connect Browserbase once, then control which Spaces can use its approved tools and data without pasting credentials into prompts or threads.
CategoryDeveloper Tools & IT
Use Browserbase from Codex
Add the Browserbase connection to a Space that runs Codex, then use it from every channel in that Space.
Use Browserbase from Sidekick
Connect your own OpenClaw to Sidekick while type.com provides the conversations, permissions, connections, skills, and automations.
Developer Tools & IT
What the Browserbase connector can do
Browserbase runs headless browsers in the cloud so teams can automate web tasks with Playwright, Puppeteer, or Selenium without hosting their own browser infrastructure. From type.com, a dev Space can ask Claude to spin up a browser context, start a session, or retrieve and clean up contexts as part of a testing or scraping workflow.
One connection, many Spaces
Connect Browserbase once, then decide which Spaces can use it in threads, skills, automations, and coding work.
Use Browserbase from Claude Code, Codex, and automations
Use Browserbase from Claude Code or Codex
Once Browserbase is connected in type.com, install the type.com CLI, and Claude Code or Codex can call its tools with type-cli integrations call. Calls run with your type.com access, and the credentials stay on type.com's servers.
Automate Browserbase on a schedule or webhook
In a Space with Browserbase connected, describe the job, and type.com proposes an automation with its trigger, schedule, and destination. Runs can start on a schedule or from a webhook, Slack, GitHub, Linear, email, or RSS, and each run leaves a thread the team can read.
What teams do with Browserbase in type.com
Prepare an isolated browser before automation
Create a browser context and session so a new automation run starts with a clean, isolated environment instead of a shared one.
Create a new Browserbase context and session for our nightly checkout test run.
Check an existing context's details
Retrieve a browser context by ID to confirm its configuration before reusing it in a new automation run.
Retrieve the Browserbase context details for context ID bc-5521 before we reuse it.
Clean up old browser contexts
Delete a context and its stored cookies or local storage once an automation project is finished.
Delete the Browserbase context we used for last month's scraping project.
Representative actions
- Create a new browser context
Creates a browser context and returns the credentials needed to upload a custom user-data directory within a project.
- Retrieve a browser context
Fetches metadata for a specific browser context by its ID.
- Update Browser Context
Refreshes a browser context's upload link and encryption settings once its ID is already known.
- Create Browser Session
Starts a new isolated browser session, the step before running any page interactions.
- Delete a browser context
Permanently removes a browser context and its stored data, like cookies and local storage.
Connection
API and auth details
Browserbase is a platform for cloud browser sessions, browser automation, web search, page fetch, and browser-agent workflows. Official docs cover Browserbase SDKs, REST API references, Playwright/Puppeteer/Selenium access, and Stagehand-based agent automation.
- Source
- type.com catalog metadata
- Auth schemes
- API key
- API docs
- https://docs.browserbase.com/
- Official site
- https://www.browserbase.com/
FAQ
Questions people ask before connecting Browserbase
Can Claude manage Browserbase sessions from type.com?
Yes. With a Browserbase connection shared to your Space, Claude can create, check, and clean up browser contexts and sessions directly in a thread.
How does type.com authenticate with Browserbase?
Browserbase uses an API key you add once to the connection, managed by an admin who decides which Spaces can use it.
Can Browserbase cleanup run on a schedule?
Yes. A recurring task, like deleting contexts older than a set age, can be set up as a type.com automation.
Can Claude Code or Codex use Browserbase?
Yes. Once Browserbase is connected in type.com, install the type.com CLI, and Claude Code or Codex can call its tools with type-cli integrations call. Calls run with your type.com access, and the credentials stay on type.com's servers.
Can I automate Browserbase on a schedule?
Yes. In a Space with Browserbase connected, describe the job, and type.com proposes an automation with its trigger, schedule, and destination. Runs can start on a schedule or from a webhook, Slack, GitHub, Linear, email, or RSS, and each run leaves a thread the team can read.
Is this the same as an MCP server for Browserbase?
Not exactly. type.com uses connectors and connections to give selected Spaces access to approved app tools and data. Some connectors use hosted MCP, while others use OAuth, API keys, service accounts, or custom APIs.
More developer tools & it connectors
All Developer Tools & IT integrationsConnect Marketstack to Claude in type.com to pull stock prices, dividends, and exchange data in a shared thread.
Connect Matterport to Claude in type.com to search models, pull model details, and check webhook configurations from a shared thread.
Connect Mercury MCP to Claude in type.com to check account balances, review transactions, and pull statements without touching the Mercury dashboard.
Connect Mezmo to Claude in type.com to create exclusion rules, provision API keys, and set up log alerts from a shared thread.