Can I trigger a browser task with a different starting URL?

Yes! Use the `run_task` tool and provide the Task ID. In the `overrides` field, you can pass a JSON object like `{"url": "https://newsite.com"}` to change the starting point dynamically.

How do I see the screenshot captured by a task?

Simply ask the agent to `get_run` and provide the Run ID. Once the status is 'finished', the response will include a `screenshot_url` that you can click to view the image.

Does the integration allow taking a quick screenshot without a saved task?

Yes. Use the `take_screenshot` action and provide the URL. It will create a simplified run that captures the page and returns the result URL once processed.

Browserbear MCP Server for CrewAI 10 tools — connect in under 2 minutes

Name: Browserbear
Availability: InStock
Author: Vinkius

docs.crewai.com/mcp/overview

Built by Vinkius GDPR 10 Tools Framework

Connect your CrewAI agents to Browserbear through Vinkius, pass the Edge URL in the `mcps` parameter and every Browserbear tool is auto-discovered at runtime. No credentials to manage, no infrastructure to maintain.

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.

python

from crewai import Agent, Task, Crew

agent = Agent(
    role="Browserbear Specialist",
    goal="Help users interact with Browserbear effectively",
    backstory=(
        "You are an expert at leveraging Browserbear tools "
        "for automation and data analysis."
    ),
    # Your Vinkius token. get it at cloud.vinkius.com
    mcps=["https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"],
)

task = Task(
    description=(
        "Explore all available tools in Browserbear "
        "and summarize their capabilities."
    ),
    agent=agent,
    expected_output=(
        "A detailed summary of 10 available tools "
        "and what they can do."
    ),
)

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

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 Browserbear MCP Server

Connect your Browserbear (Roborabbit) account to any AI agent and orchestrate your browser automation, web scraping, and visual monitoring workflows through natural conversation.

When paired with CrewAI, Browserbear becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call Browserbear tools autonomously, one agent queries data, another analyzes results, a third compiles reports, all orchestrated through Vinkius with zero configuration overhead.

What you can do

Task Oversight — List and retrieve detailed metadata for all your saved browser automation tasks.
Automation Execution — Trigger task runs with dynamic overrides (like URL or form data) and monitor their progress.
Visual Captures — Take high-quality screenshots of any URL with customizable dimensions and wait times.
Data Extraction — Retrieve scraped structured data and screenshot URLs directly into your workspace.
Run Management — List, inspect, and delete history of your automation runs.
Project Coordination — Access and organize your tasks across multiple projects and track account usage.

The Browserbear MCP Server exposes 10 tools through the Vinkius. Connect it to CrewAI 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 Browserbear to CrewAI via MCP

Follow these steps to integrate the Browserbear MCP Server with CrewAI.

Install CrewAI

Run pip install crewai

Replace the token

Replace [YOUR_TOKEN_HERE] with your Vinkius token from cloud.vinkius.com

Customize the agent

Adjust the role, goal, and backstory to fit your use case

Run the crew

Run python crew.py. CrewAI auto-discovers 10 tools from Browserbear

Why Use CrewAI with the Browserbear MCP Server

CrewAI Multi-Agent Orchestration Framework provides unique advantages when paired with Browserbear through the Model Context Protocol.

Multi-agent collaboration lets you decompose complex workflows into specialized roles, one agent researches, another analyzes, a third generates reports, each with access to MCP tools

CrewAI's native MCP integration requires zero adapter code: pass Vinkius Edge URL directly in the `mcps` parameter and agents auto-discover every available tool at runtime

Built-in task delegation and shared memory mean agents can pass context between steps without manual state management, enabling multi-hop reasoning across tool calls

Sequential and hierarchical crew patterns map naturally to real-world workflows: enumerate subdomains → analyze DNS history → check WHOIS records → compile findings into actionable reports

Browserbear + CrewAI Use Cases

Practical scenarios where CrewAI combined with the Browserbear MCP Server delivers measurable value.

Automated multi-step research: a reconnaissance agent queries Browserbear for raw data, then a second analyst agent cross-references findings and flags anomalies. all without human handoff

Scheduled intelligence reports: set up a crew that periodically queries Browserbear, analyzes trends over time, and generates executive briefings in markdown or PDF format

Multi-source enrichment pipelines: chain Browserbear tools with other MCP servers in the same crew, letting agents correlate data across multiple providers in a single workflow

Compliance and audit automation: a compliance agent queries Browserbear against predefined policy rules, generates deviation reports, and routes findings to the appropriate team

Browserbear MCP Tools for CrewAI (10)

These 10 tools become available when you connect Browserbear to CrewAI via MCP:

create_task

Create a new browser automation task

delete_run

Delete a task run record

get_account_usage

Retrieve account usage statistics

get_run

Get status and results of a task run

get_task

Get details of a specific task

list_projects

List all projects in the account

list_runs

List all task runs

list_tasks

List all browser automation tasks

run_task

Trigger a run for a specific task

take_screenshot

Take a quick screenshot of a URL

Example Prompts for Browserbear in CrewAI

Ready-to-use prompts you can give your CrewAI agent to start working with Browserbear immediately.

"List all my browser automation tasks."

"Take a screenshot of https://vinkius.com at 1280x800 resolution."

"Run task task_123 and override the starting URL to https://google.com."

Troubleshooting Browserbear MCP Server with CrewAI

Common issues when connecting Browserbear to CrewAI through the Vinkius, and how to resolve them.

MCP tools not discovered

Ensure the Edge URL is correct. CrewAI connects lazily when the crew starts. check console output.

Agent not using tools

Make the task description specific. Instead of "do something", say "Use the available tools to list contacts".

Timeout errors

CrewAI has a 10s connection timeout by default. Ensure your network can reach the Edge URL.

Rate limiting or 429 errors

Vinkius enforces per-token rate limits. Check your subscription tier and request quota in the dashboard. Upgrade if you need higher throughput.

Browserbear + CrewAI FAQ

Common questions about integrating Browserbear MCP Server with CrewAI.

How does CrewAI discover and connect to MCP tools?

CrewAI connects to MCP servers lazily. when the crew starts, each agent resolves its MCP URLs and fetches the tool catalog via the standard tools/list method. This means tools are always fresh and reflect the server's current capabilities. No tool schemas need to be hardcoded.

Can different agents in the same crew use different MCP servers?

Yes. Each agent has its own mcps list, so you can assign specific servers to specific roles. For example, a reconnaissance agent might use a domain intelligence server while an analysis agent uses a vulnerability database server.

What happens when an MCP tool call fails during a crew run?

CrewAI wraps tool failures as context for the agent. The LLM receives the error message and can decide to retry with different parameters, fall back to a different tool, or mark the task as partially complete. This resilience is critical for production workflows.

Can CrewAI agents call multiple MCP tools in parallel?

CrewAI agents execute tool calls sequentially within a single reasoning step. However, you can run multiple agents in parallel using process=Process.parallel, each calling different MCP tools concurrently. This is ideal for workflows where separate data sources need to be queried simultaneously.

Can I run CrewAI crews on a schedule (cron)?

Yes. CrewAI crews are standard Python scripts, so you can invoke them via cron, Airflow, Celery, or any task scheduler. The crew.kickoff() method runs synchronously by default, making it straightforward to integrate into existing pipelines.