Add the Browserbase MCP server to VS Code

Config last verified Jun 1, 2026

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

Prerequisites

  • VS Code 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 .vscode/mcp.json

2. Add this configuration

Add to .vscode/mcp.json

.vscode/mcp.json
json
{
  "servers": {
    "browserbase": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "@browserbasehq/mcp"
      ],
      "env": {
        "BROWSERBASE_API_KEY": "<BROWSERBASE_API_KEY>",
        "BROWSERBASE_PROJECT_ID": "<BROWSERBASE_PROJECT_ID>",
        "GEMINI_API_KEY": "<GEMINI_API_KEY>"
      }
    }
  }
}

Heads up

  • VS Code uses the `servers` key (not `mcpServers`) and requires `type`.

3. Restart VS Code and confirm the Browserbase tools load.

Gotchas

  • VS Code uses the `servers` key (not `mcpServers`) and requires `type`.

VS Code is the exception to every other client: its top-level key is "servers", not "mcpServers", and each entry needs an explicit "type" (for example "http" or "stdio"). Secrets are not inlined; instead you declare an "inputs" array and reference each value as ${input:id}, so VS Code prompts for it once and never writes it to disk. Remote servers connect natively with OAuth.

← Back to the Browserbase MCP server