MCP server for AI web browser automation using Browserbase and Stagehand
Paste into claude_desktop_config.json:
{
"mcpServers": {
"mcp-server-browserbase": {
"command": "npx",
"args": [
"-y",
"@browserbasehq/mcp-server-browserbase"
],
"env": {
"BROWSERBASE_API_KEY": "<BROWSERBASE_API_KEY>",
"BROWSERBASE_PROJECT_ID": "<BROWSERBASE_PROJECT_ID>",
"GEMINI_API_KEY": "<GEMINI_API_KEY>"
}
}
}
}Run in a terminal:
claude mcp add mcp-server-browserbase --env BROWSERBASE_API_KEY=<BROWSERBASE_API_KEY> --env BROWSERBASE_PROJECT_ID=<BROWSERBASE_PROJECT_ID> --env GEMINI_API_KEY=<GEMINI_API_KEY> -- npx -y @browserbasehq/mcp-server-browserbase
Paste into .cursor/mcp.json (project) or ~/.cursor/mcp.json (global):
{
"mcpServers": {
"mcp-server-browserbase": {
"command": "npx",
"args": [
"-y",
"@browserbasehq/mcp-server-browserbase"
],
"env": {
"BROWSERBASE_API_KEY": "<BROWSERBASE_API_KEY>",
"BROWSERBASE_PROJECT_ID": "<BROWSERBASE_PROJECT_ID>",
"GEMINI_API_KEY": "<GEMINI_API_KEY>"
}
}
}
}Transport: stdio - Runs locally over stdio. Your client launches the process itself; you need the matching runtime installed (Node for npx, uv for uvx, Docker for docker run).
Auth: requires credentials - replace the <PLACEHOLDER> environment values in the config with your own keys (see the vendor's docs).
https://wingmanprotocol.com/mcp.