Which AI clients can use the Browserbase MCP server?

27 AI clients, including Cursor, VS Code, and Claude. Each connects to Browserbase as a remote MCP server through Runlayer, which adds identity, policy, scanning, and audit to every call.

Which Browserbase tools are available?

Browserbase reports its tools when your organization connects it. Admins then choose which ones each group can call.

How does Browserbase authenticate?

Sign in the way Browserbase requires. Runlayer holds the credentials so they stay out of the client’s configuration.

Integrations / MCP servers

Browserbase

Browserbase remote MCP server for browser automation and testing via Stagehand

Book a demo View documentation

Tools

Tools discovered when you connect

Search the tool definitions captured from the MCP server. The live list can vary with version, deployment, and credentials.

Tools load when your organization connects this server

Browserbase can expose tools based on its deployed version and credentials. Runlayer discovers the available list when your organization connects the server.

Compatibility

Connect Browserbase to the clients your teams already use

27 AI clients can connect to Browserbase through Runlayer. Pick one for its setup steps and controls.

Why Runlayer

Why connect Browserbase through Runlayer?

One approved path

Approve Browserbase once and everyone gets it in the AI clients they already use. Runlayer holds the credentials, so nothing sits in client configuration.

Fine-grained policy

Control who can use each server, tool, and resource, and under which runtime conditions.

Runtime security

Scan tool inputs and outputs for prompt injection, credential exposure, PII, and data exfiltration, then alert, mask, or block.

Audit and observability

Trace every request across users, clients, tools, policies, scanner decisions, and downstream systems.