4,000+ servers built on vurb.ts
Vinkius

Browse AI MCP Server for CrewAIGive CrewAI instant access to 12 tools to Create Monitor, Get Robot Details, Get Run Status, and more

MCP Inspector GDPR Free for Subscribers

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

Ask AI about this MCP Server for CrewAI

The Browse AI MCP Server for CrewAI is a standout in the Data Management category — giving your AI agent 12 tools to work with, ready to go from day one.

Built for AI Agents by Vinkius

Vinkius delivers Streamable HTTP and SSE to any MCP client

ClaudeClaude
ChatGPTChatGPT
CursorCursor
GeminiGemini
WindsurfWindsurf
VS CodeVS Code
JetBrainsJetBrains
VercelVercel
+ other MCP clients
python
from crewai import Agent, Task, Crew

agent = Agent(
    role="Browse AI Specialist",
    goal="Help users interact with Browse AI effectively",
    backstory=(
        "You are an expert at leveraging Browse AI 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 Browse AI "
        "and summarize their capabilities."
    ),
    agent=agent,
    expected_output=(
        "A detailed summary of 12 available tools "
        "and what they can do."
    ),
)

crew = Crew(agents=[agent], tasks=[task])
result = crew.kickoff()
print(result)
Browse AI
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 Browse AI MCP Server

Connect your Browse AI account to any AI agent and take full control of your no-code web scraping and automated monitoring workflows through natural conversation.

When paired with CrewAI, Browse AI becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call Browse AI 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

  • Robot Orchestration — List and manage all web scraping robots in your account programmatically, retrieving detailed configuration and high-fidelity extraction history
  • Automated Task Execution — Programmatically trigger new robot runs with custom parameters (e.g., origin URL) to coordinate high-fidelity data collection in real-time
  • Website Monitoring Intelligence — Create and manage monitoring schedules to track changes on any website and maintain a perfectly coordinated data pipeline
  • Event Architecture — Access and monitor robot webhooks for instant notifications and retrieve detailed log metadata directly through your agent
  • Financial Visibility — Programmatically track your account subscription status and credit usage to coordinate your automated data quotas efficiently

The Browse AI MCP Server exposes 12 tools through the Vinkius. Connect it to CrewAI in under two minutes — credentials fully managed, no infrastructure to provision, no vendor lock-in. Your configuration, your data, your control.

All 12 Browse AI tools available for CrewAI

When CrewAI connects to Browse AI through Vinkius, your AI agent gets direct access to every tool listed below — spanning data-extraction, no-code, web-monitoring, and more. Every call runs in a secure, isolated environment with full audit visibility. Beyond a simple connection, you get real-time monitoring of agent activity, enterprise governance, and optimized token usage.

create

Create monitor on Browse AI

Add new schedule

get

Get robot details on Browse AI

Get robot info

get

Get run status on Browse AI

Check task progress

get

Get usage quotas on Browse AI

Check credit balance

get

Get user profile on Browse AI

Get account info

list

List active monitors on Browse AI

List scheduled scrapers

list

List bulk operations on Browse AI

List bulk task runs

list

List robot history on Browse AI

List past runs

list

List robot webhooks on Browse AI

Get event configs

list

List robots on Browse AI

List scraping robots

remove

Remove webhook on Browse AI

Delete robot webhook

trigger

Trigger robot run on Browse AI

Start scraping task

Connect Browse AI to CrewAI via MCP

Follow these steps to wire Browse AI into CrewAI. The entire setup takes under two minutes — your credentials stay safe behind Vinkius.

01

Install CrewAI

Run pip install crewai
02

Replace the token

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

Customize the agent

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

Run the crew

Run python crew.py. CrewAI auto-discovers 12 tools from Browse AI

Why Use CrewAI with the Browse AI MCP Server

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

01

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

02

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

03

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

04

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

Browse AI + CrewAI Use Cases

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

01

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

02

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

03

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

04

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

Example Prompts for Browse AI in CrewAI

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

01

"List all available scraping robots in my account."

02

"Trigger robot 'rob_123' to scrape 'https://vinkius.com/pricing'."

03

"Check the status and results for task 'task_456'."

Troubleshooting Browse AI MCP Server with CrewAI

Common issues when connecting Browse AI to CrewAI through Vinkius, and how to resolve them.

01

MCP tools not discovered

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

Agent not using tools

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

Timeout errors

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

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.

Browse AI + CrewAI FAQ

Common questions about integrating Browse AI MCP Server with CrewAI.

01

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.
02

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.
03

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.
04

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.
05

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.

Explore More MCP Servers

View all →