# Browserbase MCP server

> Control cloud browsers through Stagehand: navigate pages, act on elements, observe the page and extract data.

- Listing: https://mcp.tc/i/browserbase
- Connect: use the server's own URL `https://mcp.browserbase.com/mcp` (with your API key); clients connect to it directly. The listing link is a page, not an MCP endpoint.
- Type: remote (Streamable HTTP)
- Auth: API key
- Category: [Browser Automation](https://mcp.tc/c/browser-automation)
- Vendor: Browserbase
- Homepage: <https://docs.browserbase.com/integrations/mcp/introduction>
- Repository: <https://github.com/browserbase/mcp-server-browserbase>
- Package: npm `@browserbasehq/mcp-server-browserbase`

## About

Connects an assistant to Browserbase cloud browser sessions using Stagehand. It can start a session, open URLs, perform actions on a page, list actionable elements and extract data from what is on screen.

Runs as a hosted streamable HTTP endpoint at https://mcp.browserbase.com/mcp. The operator notes say a Browserbase API key is passed as the query parameter browserbaseApiKey. The older self-hosted npm package (@browserbasehq/mcp-server-browserbase) needs Browserbase and Gemini keys, and its repository is archived.

## What it can do

- Create or reuse a Browserbase browser session
- Navigate to a URL in a cloud browser
- Perform natural-language actions on a page
- Observe actionable elements on a page
- Extract data from a page with an instruction
- Close the current session when finished

## Tools (6)

- `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.

## Example prompts

- "Open example.com in a browser and extract the main headline."
- "Go to our pricing page and list all plan names and prices."
- "Find the login button on this page and click it."
- "Observe the checkout page and tell me which form fields are required."

## Install

### Claude Code

1. Run this in a terminal, in your project folder:

```bash
claude mcp add --transport http browserbase https://mcp.browserbase.com/mcp
```

2. Start Claude Code and type `/mcp`. **browserbase** should show as connected.

Browserbase needs an API key. Browserbase’s docs say which header carries it; most servers use `Authorization: Bearer <YOUR_API_KEY>`.

### Claude Desktop

1. Custom connectors can’t send this server’s key header, so use the `mcp-remote` bridge. Open **Settings → Developer → Edit Config** and add:

`claude_desktop_config.json`:

```json
{
  "mcpServers": {
    "browserbase": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://mcp.browserbase.com/mcp"
      ]
    }
  }
}
```

2. Replace the placeholder with your key and restart Claude Desktop.

The bridge needs Node.js on your computer.

### Cursor

[Add to Cursor](<https://cursor.com/install-mcp?name=browserbase&config=eyJ1cmwiOiJodHRwczovL21jcC5icm93c2VyYmFzZS5jb20vbWNwIn0%3D>) (opens Cursor)

Or add it by hand to `~/.cursor/mcp.json` (all projects) or `.cursor/mcp.json` (this project):

`mcp.json`:

```json
{
  "mcpServers": {
    "browserbase": {
      "url": "https://mcp.browserbase.com/mcp"
    }
  }
}
```

Browserbase needs an API key. Browserbase’s docs say which header carries it; most servers use `Authorization: Bearer <YOUR_API_KEY>`.

### VS Code

[Install in VS Code](<https://vscode.dev/redirect/mcp/install?name=browserbase&config=%7B%22type%22%3A%22http%22%2C%22url%22%3A%22https%3A%2F%2Fmcp.browserbase.com%2Fmcp%22%7D>) (opens VS Code)

Or from a terminal:

```bash
code --add-mcp '{"name":"browserbase","type":"http","url":"https://mcp.browserbase.com/mcp"}'
```

Or commit it to the repo in `.vscode/mcp.json`:

`.vscode/mcp.json`:

```json
{
  "servers": {
    "browserbase": {
      "type": "http",
      "url": "https://mcp.browserbase.com/mcp"
    }
  }
}
```

Browserbase needs an API key. Browserbase’s docs say which header carries it; most servers use `Authorization: Bearer <YOUR_API_KEY>`.

### Devin Desktop

1. Add it to `~/.config/devin/mcp_config.json` (macOS and Linux) or `%APPDATA%\devin\mcp_config.json` (Windows):

`mcp_config.json`:

```json
{
  "mcpServers": {
    "browserbase": {
      "serverUrl": "https://mcp.browserbase.com/mcp"
    }
  }
}
```

2. Refresh the MCP server list in Cascade.

Devin Desktop is the new name for Windsurf. It reads `serverUrl` (or `url`) for remote servers.

### Codex

```bash
codex mcp add browserbase --url https://mcp.browserbase.com/mcp
```

Or edit `~/.codex/config.toml` directly:

`config.toml`:

```toml
[mcp_servers.browserbase]
url = "https://mcp.browserbase.com/mcp"
```

Browserbase needs an API key. Browserbase’s docs say which header carries it; most servers use `Authorization: Bearer <YOUR_API_KEY>`.

### Gemini CLI

```bash
gemini mcp add --transport http browserbase https://mcp.browserbase.com/mcp
```

This adds it to the current project. Add `-s user` to use it everywhere.

### Any client

Most clients accept this shape. Some name the URL field differently: `serverUrl` in Devin Desktop, `httpUrl` in Gemini CLI’s settings file.

```json
{
  "mcpServers": {
    "browserbase": {
      "type": "http",
      "url": "https://mcp.browserbase.com/mcp"
    }
  }
}
```

Zed puts servers under `context_servers` in its settings. Cline needs `"type": "streamableHttp"`, or it assumes SSE.

Client only starts local servers? Bridge it with `npx -y mcp-remote https://mcp.browserbase.com/mcp`.

Browserbase needs an API key. Browserbase’s docs say which header carries it; most servers use `Authorization: Bearer <YOUR_API_KEY>`.

## Details

- Server version: e4bc9849894d3c6907d383584b689cac9f39e37c
- MCP protocol version: 2025-11-25
- Last checked: 2026-10-03 (reachable)
- Listed: 2026-10-03
- Updated: 2026-10-03

---
Source: https://mcp.tc/i/browserbase (mcp.tc is an independent directory, not affiliated with this server's publisher). Corrections: https://mcp.tc/report