2,500+ MCP servers ready to use
Vinkius

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

Built by Vinkius GDPR 10 Tools Framework

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

Vinkius supports streamable HTTP and SSE.

python
from crewai import Agent, Task, Crew

agent = Agent(
    role="ZenRows Specialist",
    goal="Help users interact with ZenRows effectively",
    backstory=(
        "You are an expert at leveraging ZenRows 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 ZenRows "
        "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)
ZenRows
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 ZenRows MCP Server

Connect your ZenRows account to any AI agent and harness the power of industrial-grade web scraping through natural conversation.

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

  • Universal Scraping — Retrieve raw HTML from any website while ZenRows automatically rotates proxies and handles CAPTCHAs
  • JavaScript Rendering — Scrape dynamic SPAs and complex web apps by using a headless browser to capture the full rendered state
  • Anti-Bot Bypass — Effortlessly bypass sophisticated protections like Cloudflare, DataDome, and PerimeterX with specialized bypass technology
  • Markdown Conversion — Automatically convert web pages into clean Markdown, ideal for LLM ingestion and RAG applications
  • Structured Data — Use auto-parse to extract JSON data from major e-commerce, search, and social platforms without manual selectors
  • Visual Previews — Generate real-time screenshots of target pages to verify rendering or monitor visual changes
  • Geographic Targeting — Execute scrapes using high-anonymity residential proxies from specific countries for localized content

The ZenRows 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 ZenRows to CrewAI via MCP

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

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 10 tools from ZenRows

Why Use CrewAI with the ZenRows MCP Server

CrewAI Multi-Agent Orchestration Framework provides unique advantages when paired with ZenRows 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

ZenRows + CrewAI Use Cases

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

01

Automated multi-step research: a reconnaissance agent queries ZenRows 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 ZenRows, analyzes trends over time, and generates executive briefings in markdown or PDF format

03

Multi-source enrichment pipelines: chain ZenRows 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 ZenRows against predefined policy rules, generates deviation reports, and routes findings to the appropriate team

ZenRows MCP Tools for CrewAI (10)

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

01

get_screenshot

Generates a URL that returns a screenshot of the target page

02

scrape_antibot

Enables js_render and antibot=true. Scrape with full anti-bot bypass for heavily protected sites

03

scrape_autoparse

Scrape with automatic structured data extraction

04

scrape_custom

g. wait, css_extractor, session_id). Execute a scrape using advanced custom parameters

05

scrape_geo

g. "us", "gb") for localized content. Scrape using a proxy from a specific country

06

scrape_html

ZenRows automatically rotates proxies and handles CAPTCHAs. Scrape raw HTML using ZenRows anti-bot proxy pool

07

scrape_js

Enables js_render=true. Slower and more expensive than static scraping. Scrape JS-rendered HTML using ZenRows headless browser

08

scrape_markdown

Automatically removes boilerplate like navigation and ads. Scrape and convert page content to clean Markdown

09

scrape_premium

Sets premium_proxy=true for higher anonymity. Scrape using ZenRows premium residential proxies

10

scrape_wait

g. "#results") to wait for before capturing the HTML. Scrape with JS render waiting for a specific CSS selector

Example Prompts for ZenRows in CrewAI

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

01

"Scrape 'https://example.com' and return the content in Markdown."

02

"Bypass Cloudflare and scrape the rendered HTML of 'https://protected-site.com'."

03

"Get a screenshot of 'https://news-portal.com/breaking-news'."

Troubleshooting ZenRows MCP Server with CrewAI

Common issues when connecting ZenRows to CrewAI through the 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.

ZenRows + CrewAI FAQ

Common questions about integrating ZenRows 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.

Connect ZenRows to CrewAI

Get your token, paste the configuration, and start using 10 tools in under 2 minutes. No API key management needed.