Can the agent bypass Cloudflare screens when scraping?

Yes. If standard scraping (`scrape_html`) encounters a block, you can prompt the agent to 'Retry using premium proxies' (`scrape_premium`). This engages ScraperAPI's massive pool of residential IP addresses to mimic normal human traffic perfectly.

How can I extract pricing data directly from Amazon?

Instead of attempting to parse Amazon's chaotic HTML structure, just ask your agent: 'Get the Amazon product details for ASIN B0BQK...'. The agent uses `scrape_amazon` to return structured JSON data, neatly outputting the item's price and stock availability.

Does the scraping tool consume my LLM context window linearly?

Not if you use async jobs. For heavy pages, tell the agent 'Create an async job to scrape this URL'. It will return a Job ID (`create_async_job`), freeing up the chat. You can then ask the agent to 'check on the async job' (`get_async_job`) whenever you're ready.

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

Name: ScraperAPI
Availability: InStock
Author: Vinkius

docs.crewai.com/mcp/overview

Built by Vinkius GDPR 10 Tools Framework

Connect your CrewAI agents to ScraperAPI through Vinkius, pass the Edge URL in the `mcps` parameter and every ScraperAPI 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="ScraperAPI Specialist",
    goal="Help users interact with ScraperAPI effectively",
    backstory=(
        "You are an expert at leveraging ScraperAPI 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 ScraperAPI "
        "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 ScraperAPI MCP Server

Connect your ScraperAPI account to any AI agent to bypass IP bans, CAPTCHAs, and complex anti-bot systems. Allow your agent to scrape the web dynamically using a pool of millions of proxies.

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

Render JavaScript — Command your AI to fetch data from SPAs (Single Page Applications) like React or Vue sites flawlessly
Structured E-commerce & SEO — Extract parsed Amazon product pages via ASIN or pull Google SERP attributes in structured JSON formats directly to your chat
Premium Unblocking — Access high-quality residential proxies automatically when dealing with ultra-secure or aggressive Cloudflare-protected targets
Asynchronous & Visual Scraping — Spawn background scraping jobs for slow-loading pages or ask the AI to generate full-page screenshot URLs upon request

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

Follow these steps to integrate the ScraperAPI 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 ScraperAPI

Why Use CrewAI with the ScraperAPI MCP Server

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

ScraperAPI + CrewAI Use Cases

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

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

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

ScraperAPI MCP Tools for CrewAI (10)

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

create_async_job

Returns a job ID. Creates an asynchronous scraping job

custom_scrape

Performs a scrape with custom ScraperAPI parameters

get_account_stats

Retrieves API usage statistics

get_async_job

Retrieves the status and result of an async job

get_screenshot_link

Generates a URL to capture a full-page screenshot

scrape_amazon

Retrieves structured Amazon product details

scrape_google_serp

Retrieves structured Google Search results

scrape_html

Automatically rotates proxies. Scrapes standard HTML from a URL

scrape_js_rendered

Scrapes a URL with JavaScript rendering enabled

scrape_premium

Scrapes a URL using high-quality residential proxies

Example Prompts for ScraperAPI in CrewAI

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

"Scrape an Amazon product page for this ASIN: B08J5F3G18 and list its price."

"Run a Google SERP check for the keyword 'best LLM orchestration frameworks'."

"Take a screenshot of https://netflix.com homepage so I can check its layout."

Troubleshooting ScraperAPI MCP Server with CrewAI

Common issues when connecting ScraperAPI 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.

ScraperAPI + CrewAI FAQ

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