How to Use the Browserbase MCP in Claude Code

Q: What is the default timeout for a session?

Sessions initiated by createbrowsersession timeout after 300 seconds. If your terminal pipeline runs longer than five minutes, you will need to split the tasks across multiple sessions.

Drive headless cloud browsers from your terminal using Claude Code and Browserbase.

See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

MCP Servers - Free for Subscribers

Connect Browserbase MCP to Claude Code

Create your Vinkius account to connect Browserbase to Claude Code and route execution through our secure gateway. The platform manages server hosting, runtime updates, and security layers. Configuration requires no manual server provisioning.

GDPR Free for Subscribers

Setup Browserbase with Claude Code

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Spin up cloud browsers via the terminal

This `create_browser_session` tool lets Claude Code launch cloud-hosted Chromium instances directly from your command line. It returns a CDP WebSocket URL, allowing your CLI agent to pipe browser automation straight into your scripts. Because it runs headlessly in the cloud, you don't need to install Chrome or heavy dependencies in your local terminal environment or CI/CD runner.

Audit active terminal-driven browser runs

The `list_browser_sessions` tool lets Claude Code query your active remote instances. It filters by RUNNING, COMPLETED, or ERROR, letting the agent log session history directly to your terminal output. Using `get_browser_session`, your CLI agent can get the exact state of any running container. This is crucial for debugging failing pipelines or cron jobs without a GUI.

Terminate stale sessions with this MCP Server

The `stop_browser_session` tool instantly kills any remote browser container. Claude Code runs this command the second a script finishes to make sure you aren't paying for idle cloud compute. Any unsaved state is wiped out immediately upon termination. This ensures clean, stateless environments for every single run in your pipeline.

Setup guide

Set up Browserbase MCP in Claude Code

Prerequisites

Claude Code CLI installed (npm install -g @anthropic-ai/claude-code)
Active Vinkius subscription with a valid endpoint token

1

Run the add command

Open your terminal and run the command shown on the right. Replace [YOUR_TOKEN_HERE] with your endpoint token from cloud.vinkius.com. Use --scope user to make it available across all projects.
2

Verify the connection

Start a Claude Code session and type /mcp to list connected servers. You should see browserbase-mcp with a green status indicator.
3

Start using tools

Ask Claude Code something like "Check my latest Browserbase transactions." It will automatically discover and invoke the available Browserbase tools.

Terminal

claude mcp add --transport http browserbase-mcp https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp

Get your connection token →

Prerequisites

Claude Code CLI installed
Active Vinkius subscription with a valid endpoint token

1

Open the config file

Create or edit .mcp.json in your project root for project-level scope, or ~/.claude.json for user-level scope.
2

Add the Browserbase MCP

Paste the JSON snippet shown on the right into the mcpServers object. Replace [YOUR_TOKEN_HERE] with your endpoint token from cloud.vinkius.com.
3

Restart Claude Code

Start a new Claude Code session. Type /mcp to confirm the server is connected. The tools will be automatically available in your conversation.

.mcp.json

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

Get your connection token →

Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by Browserbase. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.

Why Choose Vinkius

Vinkius connects your tools to AI with real-time monitoring and automatic cost savings — all from one dashboard.

Connect Browserbase now

Real-time monitoring

Live

visibility into every interaction

Connect your favorite tools to your AI and see exactly what's happening — every request, every response, in real time.

Built-in savings

60%

lower AI costs

Vinkius compresses data between your apps and your AI automatically. Lower bills every month — no configuration required.

Single dashboard

One

place for every integration

Every tool your AI connects to, managed from a single screen. One account, complete control.

Common questions about Browserbase MCP in Claude Code

Run the claude command to add the MCP Server to your terminal configuration. This command automatically writes the configuration to your `~/.claude.json` file.

Absolutely. Since Claude Code operates entirely in the terminal, you can trigger these tools inside GitHub Actions or Docker containers to run automated web tests.

The MCP Server uses your Vinkius endpoint token. This handles all API authentication behind the scenes, so your CLI agent can connect without managing raw API keys.

Sessions initiated by `create_browser_session` timeout after 300 seconds. If your terminal pipeline runs longer than five minutes, you will need to split the tasks across multiple sessions.

Yes. Only connection URLs and session metadata are sent over the network. Your actual browser traffic, cookies, and DOM data are isolated inside ephemeral sandboxes that are wiped when the session stops.

Use it with your favorite AI tools

Connect this server to Cursor, Claude, VS Code, and more.

OpenAI Agents SDK sdk-python

Google ADK sdk-python

Pydantic AI sdk-python

Vercel AI SDK sdk-typescript