How to Use the Browserbase MCP in CrewAI

Q: How do I pass the Browserbase MCP Server URL to a CrewAI agent?

You can pass your Vinkius HTTP URL directly into the mcps list when defining your CrewAI Agent. The framework auto-discovers tools like createbrowsersession instantly using our MCP tools.

Q: Is it possible to restrict certain CrewAI agents from stopping Browserbase sessions?

Yes, use the toolfilter option in MCPServerHTTP to expose only specific tools to certain agents. This prevents researchers from calling stopbrowsersession accidentally.

Q: How does CrewAI handle browser session failures?

When createbrowsersession fails, CrewAI's error-handling mechanisms catch the exception. You can configure your crew to retry the task or assign a different agent to handle it.

Coordinate teams of specialized agents to run parallel browser tasks with CrewAI.

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 CrewAI

Create your Vinkius account to connect Browserbase to CrewAI 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 CrewAI

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Run Collaborative Browser Crews with CrewAI

Instead of one agent doing everything, CrewAI lets you split up the work. One agent can call `create_browser_session` to navigate a site, while a second agent monitors the progress. They share memory and session IDs, meaning they can pass the CDP WebSocket URL back and forth. You get a coordinated team working on the same web task instead of a single overloaded script.

Monitor Active Browser Sessions with CrewAI

When running complex multi-agent jobs, you need a way to keep track of what's running. A supervisor agent can run `list_browser_sessions` to check for stuck processes. If a session shows an ERROR status, the agent can instantly trigger an escalation workflow. This keeps your autonomous operations running smoothly without manual intervention.

Limit Browser Access Using CrewAI Tool Filters

You might not want every agent in your crew to have full control over your browser account. Exposing this MCP Server via `MCPServerHTTP` lets you apply filters so only specific agents can run destructive actions. For example, you can allow your research agent to use `get_browser_session` while restricting `stop_browser_session` to the manager agent. This keeps your automation secure and organized.

Setup guide

Set up Browserbase MCP in CrewAI

Prerequisites

Python 3.10+ installed
crewai package (pip install crewai)
Active Vinkius subscription with a valid endpoint token

1

Install CrewAI
Run pip install crewai to install the framework. MCP support is built-in via the mcps parameter.
2

Add the MCP URL to your agent
Pass your Vinkius endpoint directly to the mcps list. Replace [YOUR_TOKEN_HERE] with your token from cloud.vinkius.com. CrewAI handles tool discovery and caching automatically.
3

Kick off your crew
Create a Crew with your agent and tasks. Call crew.kickoff() — the agent will automatically invoke Browserbase tools as needed.

crew.py

from crewai import Agent, Task, Crew

agent = Agent(
    role="Browserbase Analyst",
    goal="Access and analyze Browserbase data via MCP.",
    backstory="Expert analyst with direct Browserbase access.",
    mcps=[
        "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    ],
)

task = Task(
    description="List recent Browserbase transactions",
    agent=agent,
    expected_output="A summary of recent activity",
)

crew = Crew(agents=[agent], tasks=[task])
result = crew.kickoff()
print(result)

Get your connection token →

Prerequisites

Python 3.10+ installed
crewai + crewai-tools packages
Active Vinkius subscription with a valid endpoint token

1

Install dependencies
Run pip install crewai crewai-tools. The MCPServerAdapter handles lifecycle management and tool conversion.
2

Connect with MCPServerAdapter
Use MCPServerAdapter as a context manager with SseServerParameters pointing to your Vinkius endpoint. The adapter automatically manages connection lifecycle.
3

Assign tools and run
Pass the returned mcp_tools to your agent's tools parameter. The adapter converts MCP tools to native BaseTool objects compatible with all CrewAI agents.

crew.py

from crewai import Agent, Task, Crew
from crewai_tools import MCPServerAdapter
from mcp import SseServerParameters

server_params = SseServerParameters(
    url="https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
)

with MCPServerAdapter(server_params) as mcp_tools:
    agent = Agent(
        role="Browserbase Analyst",
        goal="Access and analyze Browserbase data via MCP.",
        backstory="Expert analyst with direct Browserbase access.",
        tools=mcp_tools,
    )

    task = Task(
        description="List recent Browserbase transactions",
        agent=agent,
        expected_output="A summary of recent activity",
    )

    crew = Crew(agents=[agent], tasks=[task])
    result = crew.kickoff()
    print(result)

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 CrewAI

You can pass your Vinkius HTTP URL directly into the `mcps` list when defining your CrewAI Agent. The framework auto-discovers tools like `create_browser_session` instantly using our MCP tools.

Yes, one agent can create the session and pass the ID to another. The second agent can then use `get_browser_session` to continue the task or monitor progress.

Yes, use the `tool_filter` option in `MCPServerHTTP` to expose only specific tools to certain agents. This prevents researchers from calling `stop_browser_session` accidentally.

When `create_browser_session` fails, CrewAI's error-handling mechanisms catch the exception. You can configure your crew to retry the task or assign a different agent to handle it.

No, each browser session runs in a secure, isolated V8 sandbox. All history, cookies, and DOM data are wiped from the cloud infrastructure via MCP the moment the session ends.

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