How is Browserbase different from Firecrawl?

Firecrawl is optimized for content extraction — it scrapes pages and returns clean data. Browserbase provides a full browser environment for interactive automation — your agent can click buttons, fill forms, log into websites, scroll, and navigate complex single-page applications (SPAs). Browserbase gives you a real browser, Firecrawl gives you the text from a page.

Which automation frameworks are supported?

Browserbase sessions expose a CDP (Chrome DevTools Protocol) WebSocket URL, which is compatible with all major browser automation frameworks: Playwright, Puppeteer, Selenium WebDriver, and any tool that supports CDP connections. Simply point your framework at the connectUrl returned when creating a session.

What does the free tier include?

The free tier includes 1 browser hour, 1 concurrent browser session, and 7 days of data retention. No credit card required. For production workloads, paid plans start at $20/month (Developer) with more browser hours and concurrent sessions.

Browserbase MCP Server for Cursor 4 tools — connect in under 2 minutes

Name: Browserbase
Availability: InStock
Author: Vinkius

docs.cursor.com/context/model-context-protocol

Built by Vinkius GDPR 4 Tools IDE

Cursor is an AI-first code editor built on VS Code that integrates LLM-powered coding assistance directly into the development workflow. Its Agent mode enables autonomous multi-step coding tasks, and MCP support lets agents access external data sources and APIs during code generation.

Get MCP Server for AI Agents

ASK AI ABOUT THIS MCP SERVER

Open in ChatGPT Open in Claude Open in Perplexity

Vinkius supports streamable HTTP and SSE.

RecommendedModern Approach — Zero Configuration

Vinkius Desktop App

The modern way to manage MCP Servers — no config files, no terminal commands. Install Browserbase and 2,500+ MCP Servers from a single visual interface.

Download Free Open SourceNo signup required

Classic Setup·json

{
  "mcpServers": {
    "browserbase": {
      "url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    }
  }
}

Fully ManagedVinkius Servers

60%Token savings

High SecurityEnterprise-grade

IAMAccess control

EU AI ActCompliant

DLPData protection

V8 IsolateSandboxed

Ed25519Audit chain

<40msKill switch

Stream every event to Splunk, Datadog, or your own webhook in real-time

* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure

About Browserbase MCP Server

Connect your AI agent to Browserbase — the serverless platform for running headless cloud browsers at scale.

Cursor's Agent mode turns Browserbase into an in-editor superpower. Ask Cursor to generate code using live data from Browserbase and it fetches, processes, and writes. all in a single agentic loop. 4 tools appear alongside file editing and terminal access, creating a unified development environment grounded in real-time information.

What you can do

Create Sessions — Spin up isolated Chromium browser sessions in the cloud. Each session returns a CDP (Chrome DevTools Protocol) WebSocket URL for connecting Playwright, Puppeteer, or Selenium
List Sessions — Monitor all active, completed, or errored browser sessions across your account
Get Session Details — Check status, connection URLs, pages visited, and duration of any session
Stop Sessions — Terminate running sessions to free resources

The Browserbase MCP Server exposes 4 tools through the Vinkius. Connect it to Cursor in under two minutes — no API keys to rotate, no infrastructure to provision, no vendor lock-in. Your configuration, your data, your control.

How to Connect Browserbase to Cursor via MCP

Follow these steps to integrate the Browserbase MCP Server with Cursor.

Open MCP Settings

Press Cmd+Shift+P (macOS) or Ctrl+Shift+P (Windows/Linux) → search "MCP Settings"

Add the server config

Paste the JSON configuration above into the mcp.json file that opens

Save the file

Cursor will automatically detect the new MCP server

Start using Browserbase

Open Agent mode in chat and ask: "Using Browserbase, help me...". 4 tools available

Why Use Cursor with the Browserbase MCP Server

Cursor AI Code Editor provides unique advantages when paired with Browserbase through the Model Context Protocol.

Agent mode turns Cursor into an autonomous coding assistant that can read files, run commands, and call MCP tools without switching context

Cursor's Composer feature can generate entire files using real-time data fetched through MCP. no copy-pasting from external dashboards

MCP tools appear alongside built-in tools like file reading and terminal access, creating a unified agentic environment

VS Code extension compatibility means your existing workflow, keybindings, and extensions all work alongside MCP tools

Browserbase + Cursor Use Cases

Practical scenarios where Cursor combined with the Browserbase MCP Server delivers measurable value.

Code generation with live data: ask Cursor to generate a security report module using live DNS and subdomain data fetched through MCP

Automated documentation: have Cursor query your API's tool schemas and generate TypeScript interfaces or OpenAPI specs automatically

Infrastructure-as-code: Cursor can fetch domain configurations and generate corresponding Terraform or CloudFormation templates

Test scaffolding: ask Cursor to pull real API responses via MCP and generate unit test fixtures from actual data

Browserbase MCP Tools for Cursor (4)

These 4 tools become available when you connect Browserbase to Cursor via MCP:

create_browser_session

The session provides a connectUrl (CDP WebSocket) that can be used with Playwright, Puppeteer, or Selenium to control the browser programmatically. Default timeout is 300 seconds. Create a new cloud browser session. Returns a CDP WebSocket URL for connecting automation frameworks like Playwright or Puppeteer

get_browser_session

Useful for monitoring active sessions. Get details of a specific browser session by its ID

list_browser_sessions

Filter by status: RUNNING, COMPLETED, ERROR. List all active browser sessions in your Browserbase account

stop_browser_session

Any unsaved state in the browser is lost. Stop a running browser session by its ID

Example Prompts for Browserbase in Cursor

Ready-to-use prompts you can give your Cursor agent to start working with Browserbase immediately.

"Create a new browser session so I can automate a login flow."

"Show me all my running browser sessions."

"Stop browser session sess_abc123."

Troubleshooting Browserbase MCP Server with Cursor

Common issues when connecting Browserbase to Cursor through the Vinkius, and how to resolve them.

Tools not appearing in Cursor

Ensure you are in Agent mode (not Ask mode). MCP tools only work in Agent mode.

Server shows as disconnected

Check Settings → Features → MCP and verify the server status. Try clicking the refresh button.

Browserbase + Cursor FAQ

Common questions about integrating Browserbase MCP Server with Cursor.

What is Agent mode and why does it matter for MCP?

Agent mode is Cursor's autonomous execution mode where the AI can perform multi-step tasks: reading files, editing code, running terminal commands, and calling MCP tools. Without Agent mode, Cursor operates in a simpler ask-and-answer mode that doesn't support tool calling. Always ensure you're in Agent mode when working with MCP servers.

Where does Cursor store MCP configuration?

Cursor looks for MCP server configurations in a mcp.json file. You can configure servers at the project level (.cursor/mcp.json in your project root) or globally (~/.cursor/mcp.json). Project-level configs take precedence.

Can Cursor use MCP tools in inline edits?

No. MCP tools are only available in Agent mode through the chat panel. Inline completions and Tab suggestions do not trigger MCP tool calls. This is by design. tool calls require user visibility and approval.

How do I verify MCP tools are loaded?

Open Settings → Features → MCP and look for your server name. A green indicator means the server is connected. You can also check Agent mode's available tools by clicking the tools dropdown in the chat panel.