Browserbase MCP Server for Cursor: Setup & Config

What you can do with Browserbase in Cursor

Use a compact browser toolset with a hosted starting point and configurable self-hosted alternative.

• Discover actionable page elements before choosing an operation.
• Extract page data through Stagehand-backed automation.

Before you start: Browserbase in Cursor

• An MCP-compatible client
• npx for local npm execution
• Browserbase credentials and a model key for self-hosted execution

The command is the self-hosted stdio option. The remote URL uses Streamable HTTP and is the README's recommended setup. Self-hosted custom models use --modelName and --modelApiKey.

Browserbase Cursor configuration

1. Choose Cursor configuration scope

   For Browserbase MCP Server, open Project: .cursor/mcp.json User: ~/.cursor/mcp.json. Merge into mcpServers at project or user scope.

2. Add Browserbase MCP Server to Cursor

   Use the mcp-server-browserbase entry below in mcpServers. Keep Browserbase MCP Server's documented stdio connection fields and your other Cursor entries.

3. Check Browserbase MCP Server in Cursor

   Browserbase MCP Server: Enable in Cursor’s MCP settings; inspect tools.

{
  "mcpServers": {
    "mcp-server-browserbase": {
      "command": "npx",
      "args": [
        "@browserbasehq/mcp"
      ],
      "env": {
        "BROWSERBASE_API_KEY": "<your Browserbase API key>",
        "BROWSERBASE_PROJECT_ID": "<your Browserbase project ID>",
        "GEMINI_API_KEY": "<your Gemini API key for the default model>"
      }
    }
  }
}

Browserbase tools available to Cursor

Browserbase's stored tool list documents 6 tools; compare it with Cursor's connected tool list, because the stored list is not a live check.

start

Find start under Browserbase in Cursor's MCP settings; inspect its arguments when the agent requests a call.

end

Find end under Browserbase in Cursor's MCP settings; inspect its arguments when the agent requests a call.

navigate

Find navigate under Browserbase in Cursor's MCP settings; inspect its arguments when the agent requests a call.

act

Find act under Browserbase in Cursor's MCP settings; inspect its arguments when the agent requests a call.

Carry out an instructed action on the page.

observe

Find observe under Browserbase in Cursor's MCP settings; inspect its arguments when the agent requests a call.

Identify page elements relevant to an interaction instruction.

extract

Find extract under Browserbase in Cursor's MCP settings; inspect its arguments when the agent requests a call.

Retrieve page data, optionally guided by an instruction.

Browserbase: full stored tool descriptions

Troubleshooting Browserbase in Cursor

• Cursor must find npx @browserbasehq/mcp (Node.js/npm) for Browserbase MCP Server. Enable the project/user entry in MCP settings and inspect its tools.
• Review BROWSERBASE_API_KEY, BROWSERBASE_PROJECT_ID, GEMINI_API_KEY for Browserbase MCP Server before sharing project .cursor/mcp.json; project scope travels with the repository.
• Browserbase MCP Server uses stdio here: Cursor must keep the configured process running; protocol output belongs on stdout and diagnostics on stderr.
• Known limitation: Self-hosted setup requires Browserbase credentials and model authentication.
• Known limitation: Custom models require a separate provider key.
• Known limitation: Verified Identity is restricted to Scale plan users.
• General Cursor troubleshooting lives in the /clients/cursor guide.

Frequently asked questions