How is this different from connecting Browserbase MCP directly?

Connected directly, an agent sees every tool the server exposes and holds the credential itself. Through TrustGate you choose which tools each agent gets, and every call is logged against the agent that made it.

What if the Browserbase MCP API changes?

We track the Browserbase MCP schema, so the tool catalogue stays current. Tools you have already allowed keep working, and anything new stays denied until you enable it.

Can I give different agents different Browserbase tools?

Yes. Access is set per agent: one can get a handful of read tools, another the full set. You grant the whole MCP or single tools within it.

Where can I see what my agents did in Browserbase?

Every call is logged against the agent that made it, with the tool it used. Activity can be sent on to your own monitoring.

Do I need to run the Browserbase MCP server myself?

No. TrustGate connects to the Browserbase MCP server and sits in front of it. Your agent only talks to your TrustGate URL, never to Browserbase directly.

Connect Browserbase MCP to your AI agents, securely.

Q: Is Browserbase MCP secure?

The server itself exposes 6 tools, and some of them can write to your Browserbase account. Behind TrustGate an agent only sees the tools you allow, requests and responses are inspected, and every call is logged. Anything outside the allowlist is denied before it reaches Browserbase.

One secured endpoint for every Browserbase call your AI agents make, scoped per user, inspected, and logged.

Get started for free

Get a demo

Try Browserbase MCP now

What your agents can ask once Browserbase MCP is connected.

“Open this page and tell me what's on it”
“What can I click on this page?”
“Extract the pricing table from this page”

“Fill in the search box and submit it”
“Start a browser session and go to this URL”
“Close the session when you're done”

Select the tools your AI agents can call

6 tools from the Browserbase MCP schema.

Showing 6 tools

startwriteCreates or reuses a Browserbase session. Takes no input.
endwriteCloses the current Browserbase session. Takes no input.
navigatehigh riskNavigates the session to a URL. The browser loads whatever that URL serves.
acthigh riskPerforms an action on the page from a natural-language instruction. Stagehand resolves the instruction against the live page, so the action taken depends on the page's own content.
observereadObserves the actionable elements on the page for a given instruction.
extractreadExtracts data from the page, optionally guided by an instruction.

What Browserbase MCP exposes

Browserbase MCP groups its 6 tools into 3 categories, each with a suggested starting policy.

Category	Covers	Access	Suggested policy
Session	Creating or reusing a Browserbase session and closing it	Read / Write	With --contextId and --persist (on by default) the session carries cookies and logged-in state between runs; treat a persisted context as a stored credential
Interaction	Navigating to a URL and performing an action on the page from a natural-language instruction	Read / Write	act routes the instruction through an LLM that reads the page to choose what to click, so page content is part of the decision; require approval and pin the allowed domains
Inspection	Observing the actionable elements on the page and extracting data from it	Read	Read-only, but everything returned is third-party page content; keep it out of the instruction path