• TidioReply faster to tickets across all channels
  • LyroHire AI to handle customer servicecheck
  • Hubi AIRun on-brand marketing with an AI coworker
  • LabsTidio LabsGet a custom AI solution built by experts
  • Master AgentOrchestrates every channel
  • AI Voice AgentResolves calls on its own
  • Lyro for Zendesk
  • Lyro for Freshdesk
  • Lyro for Salesforce
  • Lyro for HubSpot
Browse all integrationsarrow_forward
  • Borrowell83% resolved
  • GameBoost86% automated
  • Cove Smart70% self-service
  • Secureframe59% automated
See all customer storiesarrow_forward
  • AI in E-Commerce in 2026Free report on the new shopping funnel
  • Shadow AIFree report on the hidden AI habit
  • AI in Insurance in 2026Free report on AI in insurance
See all reportsarrow_forward
  • Features
  • Pricing
Talk to salesGet started
Lyro wordmark

Product

  • Features
  • Master Agent
  • AI Voice Agent
  • Integrations
  • Pricing
  • Copilot

Resources

  • Blog
  • Customer Stories
  • Reports
  • AI in Ecommerce Report
  • Docs

Company

  • Contact
  • Book a Demo

Legal

  • Privacy Policy
  • Terms of Service
  • Data Processing Agreement

4.7/5on G2G2 logo

SOC 2 Type II · GDPR · CCPA

© 2026 Lyro by Tidio. All rights reserved.

Browserbase tool

Browserbase tool MCP integration

Opens and closes browser sessions, pulls debug URLs, logs and artifacts, manages reusable contexts, and reports project usage.

Connect Browserbase toolSee all integrations

19actions available

  1. Home/
  2. Integrations/
  3. Browserbase tool

Three actions you can hand over today

Every action runs live through MCP. Nothing to build, nothing to maintain.

  • Create browser session

    Lyro creates a new browser session with Browserbase. Support agents can automate web scraping and testing workflows directly from conversation context.

  • Upload file to session

    Lyro uploads files to a browser session for file input operations. Agents automate document handling and form submissions without manual intervention.

  • List browser sessions

    Lyro lists all browser sessions. Agents monitor active automation runs and troubleshoot issues in real time.

See all 19 actions

How businesses use Browserbase tool + Lyro

Each card is one request a support team gets, and the Browserbase tool actions Lyro runs to close it.

  • cloud

    Start an isolated browser and feed it what it needs

    Lyro creates the session, uploads any file the run has to submit into a file input, and requests completion when the work is done rather than waiting for the timeout.

    Create Browser SessionUpload File To SessionUpdate Browser Session
  • search

    Work out why an automation run went wrong

    Lyro fetches the live debug URLs to connect to a running session, reads the network events and data exchange from its logs, and downloads everything the session produced.

    Retrieve Session Debug URLsRetrieve Session LogsDownload Session Artifacts
  • key

    Carry a signed-in state between runs

    Lyro creates a browser context to hold cookies and local storage, refreshes its upload and encryption details when they expire, and wipes it when the state should not persist.

    Create A New Browser ContextUpdate Browser ContextDelete A Browser Context
  • insights

    Answer where the browser spend is going

    Lyro lists the projects on the account, reports the browser minutes and proxy bytes each has consumed, and shows which sessions are running or recently finished.

    List ProjectsGet Project Usage StatisticsList Browser Sessions

How it works

Get started in 3 steps

Connect once, then just ask. There is no workflow builder to learn and nothing to maintain — Lyro reads the Browserbase tool actions it has and picks the ones a request needs.

  1. 01

    Connect Browserbase tool

    Authorize the Browserbase tool account your team already uses — one consent screen, no API keys, no mapping tables. Lyro can only do what you granted that account, and you can disconnect it at any time.

  2. 02

    Tell your agent what you need

    Describe the job the way you would hand it to a teammate. Lyro maps it to the Browserbase tool actions that close it and chains as many as the request needs.

  3. 03

    Watch it work

    The agent runs the actions inside the conversation the customer is already in, so nobody copies data between tabs and your team can take over at any point.

    Get started free

Browserbase tool · Lyro

What can you do in Browserbase tool without me setting anything up?

These, right away:

  • Create a new browser context
  • Retrieve a browser context
  • Update browser context

Great, let's start with the first one.

Ask Lyro anything...

FAQ

Everything else about Browserbase tool

Setup, permissions, and the limits of what Lyro can do inside Browserbase tool.

  • Not from this toolkit. It provisions and observes browsers: sessions, contexts, extensions, logs, artifacts, and usage. Page interaction belongs to your Playwright or Selenium script, and Retrieve Session Debug URLs is what gives that script a live connection to a running session.

  • Update Browser Session requests session completion before the timeout, which Browserbase ties directly to avoiding additional charges. Get project usage statistics then reports the browser minutes and proxy bytes consumed, so Lyro can say where the spend actually went.

  • A context carries persistent browser state - cookies, localStorage, and the rest of a user-data directory. Create a new browser context returns upload credentials for it and Update Browser Context issues fresh upload and encryption details, while Delete a browser context permanently removes the context and everything stored in it.

  • Both are supported. Upload Browser Extension takes a Chrome extension in ZIP format into the project, and Upload File to Session makes a file available to file input fields in a running session. Download Session Artifacts returns everything the session generated as a ZIP once it finishes.

Every action available in Browserbase tool

All 19 actions your agent can call on Browserbase tool, straight from the live MCP connection.

  • Create a new browser context

    Create a new browser context.

  • Retrieve a browser context

    Retrieve details of a specific browser context.

  • Update browser context

    Update a specific browser context.

  • Create browser session

    Create a new browser session.

  • Delete a browser context

    Delete a browser context and all its stored data (cookies, localStorage, etc.).

  • Delete a browser extension

    Delete an uploaded browser extension by its ID.

  • Delete session downloads

    Delete all file downloads from a specific browser session.

  • Retrieve a browser extension

    Retrieve details of a specific browser extension.

  • Retrieve a project

    Retrieve details of a specific project including settings and configuration.

  • Get project usage statistics

    Retrieve usage statistics for a project including browser minutes and proxy bytes consumed.

  • List projects

    List all projects for the authenticated account.

  • Retrieve a browser session

    Retrieve details of a specific browser session.

  • Retrieve session debug urls

    Retrieve live debug URLs for a specific session.

  • Download session artifacts

    Download files from a specific session.

  • Retrieve session logs

    Retrieve logs of a specific session.

  • List browser sessions

    List all browser sessions.

  • Update browser session

    Update the status of a specific browser session.

  • Upload browser extension

    Upload a browser extension for use in sessions.

  • Upload file to session

    Upload files to a browser session for file input operations.

The tools Browserbase tool sits next to

Same connection, same setup. Pick the next one your team already uses.

  • Better stackarrow_outward

    Better stack

    Checks whether a service is actually up, acknowledges and escalates open incidents, publishes status page updates, and maintains the on-call rota.

  • Convexarrow_outward

    Convex

    Creates projects and deployments, batches query functions to read app data, issues and audits deploy keys, and reports log streams.

  • Giteaarrow_outward

    Gitea

    Answers Gitea configuration questions from the running instance and renders Markdown or AsciiDoc into the HTML Gitea itself would produce.

  • Neonarrow_outward

    Neon

    Lists branches, reads schemas and connection strings, provisions branches, databases, and compute endpoints, and reports project consumption.

  • Saucelabsarrow_outward

    Saucelabs

    Reports Sauce Labs status, pulls test job history, and confirms supported platforms, tunnel versions, and Appium end-of-life dates.

  • Updown.ioarrow_outward

    Updown.io

    Reads back every configured check with its status and settings, and returns the current monitoring node list with IPv4 and IPv6 addresses.

Browse every integration
Support agent working at a laptop next to the Lyro mascot

Ready to connect Browserbase tool?

Authorize the account and your agent has all 19 actions from the first conversation.

Connect Browserbase toolTalk to sales
Connect Browserbase toolTalk to sales
Support agent working at a laptop next to the Lyro mascot