Add the Browserbase MCP server to VS Code (GitHub Copilot)

VS Code opens the sign-in flow when Copilot first calls a remote OAuth server. Browserbase runs locally and needs BROWSERBASE_API_KEY, BROWSERBASE_PROJECT_ID, GEMINI_API_KEY. Replace the placeholder values above with your own before starting VS Code (GitHub Copilot).

Ask VS Code (GitHub Copilot) for something Browserbase can do. Cloud browser automation with Browserbase and Stagehand. Approve the first tool call and check the result before allowing write actions automatically.

• · mcp.json uses a top-level servers key, not mcpServers.
• · code --add-mcp installs a server into your user profile from the terminal.

How do I add the Browserbase MCP server to VS Code (GitHub Copilot)?

Run: code --add-mcp '{"name":"browserbase","command":"npx","args":["-y","@browserbasehq/mcp-server-browserbase"],"env":{"BROWSERBASE_API_KEY":"<your BROWSERBASE_API_KEY>","BROWSERBASE_PROJECT_ID":"<your BROWSERBASE_PROJECT_ID>","GEMINI_API_KEY":"<your GEMINI_API_KEY>"}}'. VS Code opens the sign-in flow when Copilot first calls a remote OAuth server.

Is this the official Browserbase MCP server?

Yes. It is published by Browserbase as io.github.browserbase/mcp-server-browserbase in the official MCP registry.

Does the Browserbase MCP server need an API key?

Yes. It runs locally and requires BROWSERBASE_API_KEY, BROWSERBASE_PROJECT_ID, GEMINI_API_KEY.