# Browserbase MCP [Official] [Health: Active]

**Category:** 📂 Browser Automation  
**Repository:** https://docs.browserbase.com/integrations/mcp/introduction  
**Views:** 0  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/browserbase-mcp

## Description
Browserbase's official hosted MCP server. Gives agents a cloud browser driven by Stagehand: start and end sessions, navigate, act on the page, observe elements and extract data. Replaces the archived self-hosted browserbase/mcp-server-browserbase.

## Tools
Capabilities this server exposes over MCP:

- **start** — Create or reuse a Browserbase session
- **end** — Close the current Browserbase session
- **navigate** — Navigate to a URL
- **act** — Perform an action on the page
- **observe** — Observe actionable elements on the page
- **extract** — Extract data from the page

## Claude Desktop Quick Installation
Remote MCP endpoint (confidence: medium). Install path inferred — verify against the README before running it. Add as a URL/SSE server in your client:

```json
"mcpServers": {
  "browserbase-mcp": {
    "url": "https://docs.browserbase.com/integrations/mcp/introduction"
  }
}
```

## Documentation

## What Browserbase MCP does

Browserbase MCP connects MCP-compatible agents to a Browserbase cloud browser. The browser is driven by Stagehand, while the MCP interface presents browser operations as tools that an agent can call.

The server covers the main lifecycle of a browser session: an agent can create or reuse a session, work with a web page, collect information from it, and close the session when finished. This makes it suitable for browser automation tasks that require navigation and interaction with page content.

Browserbase MCP is the hosted successor to the archived `browserbase/mcp-server-browserbase` project. Use it when the target workflow depends on Browserbase rather than a locally managed browser service.

## How it works

An MCP client invokes Browserbase tools as the agent progresses through a browser task. The `start` operation creates a new Browserbase session or reuses an existing one. Once a session is available, the agent can move to a URL with `navigate`, perform page actions with `act`, inspect available interactions with `observe`, and retrieve page data with `extract`.

The `end` operation closes the current Browserbase session. Together, these operations provide a session-oriented workflow: start the browser, navigate and interact, inspect or extract information, then end the session.

## Tools and capabilities

- `start`: Create or reuse a Browserbase session.
- `end`: Close the current Browserbase session.
- `navigate`: Open a URL in the browser.
- `act`: Perform an action on the current page.
- `observe`: Identify actionable elements on the page.
- `extract`: Extract data from the current page.

The combination of `observe` and `act` supports workflows where an agent first examines what can be interacted with, then performs an action. `extract` provides a separate operation for collecting information from the page after navigation or interaction.

## Limitations and notes

Browserbase MCP is a hosted service rather than the archived self-hosted `browserbase/mcp-server-browserbase` implementation. Its documented scope is the Browserbase session and page workflow exposed through the six tools above: session management, navigation, actions, observation, and extraction. The server belongs in the browser automation category and is intended for agents that need access to a cloud browser through MCP.

_Full upstream README: https://allmcps.com/mcp/browserbase-mcp/readme_