Browserbase MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GEMINI_API_KEY | Yes | Your Gemini API key (required when using the default Gemini model) | |
| BROWSERBASE_API_KEY | Yes | Your Browserbase API key | |
| BROWSERBASE_PROJECT_ID | Yes | Your Browserbase project ID |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| browserbase_session_createB | Create or reuse a Browserbase browser session and set it as active. |
| browserbase_session_closeA | Close the current Browserbase session and reset the active context. |
| browserbase_stagehand_navigateA | Navigate to a URL in the browser. Only use this tool with URLs you're confident will work and be up to date. Otherwise, use https://google.com as the starting point |
| browserbase_stagehand_actC | Perform a single action on the page (e.g., click, type). |
| browserbase_stagehand_extractB | Extract structured data or text from the current page using an instruction. |
| browserbase_stagehand_observeB | Find interactive elements on the page from an instruction; optionally return an action. |
| browserbase_screenshotC | Capture a full-page screenshot and return it (and save as a resource). |
| browserbase_stagehand_get_urlA | Return the current page URL (full URL with query/fragment). |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 8 tools
Each tool has a clearly distinct purpose with no overlap: session management (create/close), navigation (navigate/get_url), interaction (act/observe), extraction (extract), and capture (screenshot). The descriptions reinforce unique functions, making misselection unlikely.
All tools follow a consistent 'browserbase_' prefix with descriptive suffixes (e.g., session_create, stagehand_act). The naming is uniformly snake_case and logically groups tools by functionality (session_*, stagehand_*), providing excellent predictability.
With 8 tools, the server is well-scoped for browser automation, covering core workflows like session lifecycle, navigation, interaction, and data extraction. Each tool earns its place without redundancy or bloat, fitting typical automation needs.
The toolset provides strong coverage for browser automation, including session management, navigation, interaction, and data extraction. A minor gap exists in advanced features like file uploads or cookie handling, but core workflows are fully supported without dead ends.