Browserbase MCP for AI agents
Agents read Browserbase MCP at once. Changes and sends are held for a person's approval by default.
About Browserbase MCP
Browserbase MCP gives agents isolated cloud browsers for navigation, observation, extraction, and natural-language web actions through Stagehand.
What an agent can do in Browserbase MCP
Every Browserbase MCP action is classed by the platform as a read, a change or a send. Reads run at once. Changes and sends are held for a person by default.
Runs at once (reads)
Looks things up in Browserbase MCP without asking first. 2 actions.
- ExtractExtract data from the page
- ObserveObserve actionable elements on the page
Held for approval by default (changes and sends)
Held for a person's approval by default. The approval is recorded and the action is sent once, never twice, with 10 seconds to undo. 4 actions.
- ActPerform an action on the page
- EndClose the current Browserbase session
- NavigateNavigate to a URL
- StartCreate or reuse a Browserbase session
Changes wait in Needs you
Changes and sends in Browserbase MCP are held for a person's approval by default. The approval is recorded, and the action is sent once, never twice, with 10 seconds to undo.
Related connectors
Browserbase MCP questions
Can an agent change data in Browserbase MCP on its own?
Not by default. Changes and sends in Browserbase MCP are held for a person's approval. The approval is recorded, and the action is sent once, never twice, with 10 seconds to undo.
What can an agent read in Browserbase MCP?
This connector lists 2 read actions. Reads run at once, without waiting for approval.
How does Browserbase MCP connect?
It connects with API key. Connectors are built and maintained by third-party developers; availability is confirmed during scoping.