Opens and closes browser sessions, pulls debug URLs, logs and artifacts, manages reusable contexts, and reports project usage.
19actions available
Every action runs live through MCP. Nothing to build, nothing to maintain.
Ayro creates a new browser session with Browserbase. Support agents can automate web scraping and testing workflows directly from conversation context.
Ayro uploads files to a browser session for file input operations. Agents automate document handling and form submissions without manual intervention.
Ayro lists all browser sessions. Agents monitor active automation runs and troubleshoot issues in real time.
Each card is one request a support team gets, and the Browserbase tool actions Ayro runs to close it.
Ayro 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.
Ayro 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.
Ayro 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.
Ayro 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.
How it works
Connect once, then just ask. There is no workflow builder to learn and nothing to maintain — Ayro reads the Browserbase tool actions it has and picks the ones a request needs.
Authorize the Browserbase tool account your team already uses — one consent screen, no API keys, no mapping tables. Ayro can only do what you granted that account, and you can disconnect it at any time.
Describe the job the way you would hand it to a teammate. Ayro maps it to the Browserbase tool actions that close it and chains as many as the request needs.
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 freeBrowserbase tool · Ayro
What can you do in Browserbase tool without me setting anything up?
These, right away:
Great, let's start with the first one.
FAQ
Setup, permissions, and the limits of what Ayro 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.
All 19 actions your agent can call on Browserbase tool, straight from the live MCP connection.
Create a new browser context.
Retrieve details of a specific browser context.
Update a specific browser context.
Create a new browser session.
Delete a browser context and all its stored data (cookies, localStorage, etc.).
Delete an uploaded browser extension by its ID.
Delete all file downloads from a specific browser session.
Retrieve details of a specific browser extension.
Retrieve details of a specific project including settings and configuration.
Retrieve usage statistics for a project including browser minutes and proxy bytes consumed.
List all projects for the authenticated account.
Retrieve details of a specific browser session.
Retrieve live debug URLs for a specific session.
Download files from a specific session.
Retrieve logs of a specific session.
List all browser sessions.
Update the status of a specific browser session.
Upload a browser extension for use in sessions.
Upload files to a browser session for file input operations.
Same connection, same setup. Pick the next one your team already uses.
Checks whether a service is actually up, acknowledges and escalates open incidents, publishes status page updates, and maintains the on-call rota.
Creates projects and deployments, batches query functions to read app data, issues and audits deploy keys, and reports log streams.
Answers Gitea configuration questions from the running instance and renders Markdown or AsciiDoc into the HTML Gitea itself would produce.
Lists branches, reads schemas and connection strings, provisions branches, databases, and compute endpoints, and reports project consumption.
Reports Sauce Labs status, pulls test job history, and confirms supported platforms, tunnel versions, and Appium end-of-life dates.
Reads back every configured check with its status and settings, and returns the current monitoring node list with IPv4 and IPv6 addresses.

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