Add the Browserbase MCP server to Cursor

Config last verified Jun 1, 2026

The exact config to run Browserbase in Cursor — paste it in, restart, and the tools load.

Prerequisites

Cursor installed.
BROWSERBASE_API_KEY — Browserbase API key.
BROWSERBASE_PROJECT_ID — Browserbase project ID.
GEMINI_API_KEY — LLM key used by Stagehand's default model.

Setup

1. Open `~/.cursor/mcp.json`

2. Add this configuration

Add to ~/.cursor/mcp.json

~/.cursor/mcp.json

json

{
  "mcpServers": {
    "browserbase": {
      "command": "npx",
      "args": [
        "@browserbasehq/mcp"
      ],
      "env": {
        "BROWSERBASE_API_KEY": "<BROWSERBASE_API_KEY>",
        "BROWSERBASE_PROJECT_ID": "<BROWSERBASE_PROJECT_ID>",
        "GEMINI_API_KEY": "<GEMINI_API_KEY>"
      }
    }
  }
}

3. Restart Cursor and confirm the Browserbase tools load.

Gotchas

Cursor keeps MCP servers under an "mcpServers" object in ~/.cursor/mcp.json for global use, and also reads a project-scoped .cursor/mcp.json so a repository can ship its own servers. Remote servers are configured with a bare "url" field and connect natively, with OAuth handled in-app when a server requires it.

← Back to the Browserbase MCP server