When should I use the JavaScript (JS) Token versus the Normal Token?

Use the Normal Token for fast, static HTML extraction. Switch to the JavaScript Token when the target site uses frameworks like React or Angular, where content is rendered dynamically in the browser. The 'scrape_js_rendered' tool requires the JS Token to function.

Can my agent bypass CAPTCHAs while scraping Google or LinkedIn?

Yes. Crawlbase is built to handle CAPTCHAs and blocks natively. When you use specialized tools like 'scrape_google_serp' or 'scrape_linkedin', the agent routes your requests through Crawlbase's advanced proxy infrastructure to ensure successful data extraction.

How do I get a structured JSON response instead of raw HTML?

Use the 'scrape_json_format' tool or the specialized scraper tools (Amazon, LinkedIn, etc.). These trigger Crawlbase's auto-extraction pipelines, which analyze the page structure and return specific data fields in a clean JSON format.

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

Name: Crawlbase
Availability: InStock
Author: Vinkius

docs.crewai.com/mcp/overview

Built by Vinkius GDPR 10 Tools Framework

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

Connect your Crawlbase (formerly ProxyCrawl) account to any AI agent and take full control of your web scraping and anonymous crawling workflows through natural conversation.

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

Standard Scraper — Identify bounded routing spaces inside the headless engine to extract explicitly attached HTML content via datacenter proxies
JS Rendering — Discover disconnected physical limits tracking exactly what JS-rendered frames expose to extract exact single-page UI bounds
Structured JSON Extraction — Analyzes specific global bounds driving auto-extraction pipelines to force raw HTTP outputs into structured JSON format strictly
Screenshot Capture — Dispatch automated validation checks to generate valid proxy endpoints returning configured Crawlbase screenshot URLs
Specialized Scraping — Leverage dedicated algorithms for Amazon products, LinkedIn profiles, Facebook pages, and Twitter (X) graph profiles natively
Search Engine Discovery — Explain explicitly mapped proxy lists targeting Google domains to parse SERP limits and bypass CAPTCHAs limitlessly
Custom Proxy Management — Provision highly-available request payloads generating custom proxies with specific headers and crawling logic

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

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

Why Use CrewAI with the Crawlbase MCP Server

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

Crawlbase + CrewAI Use Cases

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

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

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

Crawlbase MCP Tools for CrewAI (10)

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

custom_scrape

Provision a highly-available Request Payload generating Custom proxies

get_screenshot_link

Dispatch an automated validation check routing explicit Web Snapshot domains

scrape_amazon

Inspect deep internal arrays mitigating specific E-Commerce constraints

scrape_facebook

Enumerate explicitly attached structured rules exporting active Social Pages

scrape_google_serp

Identify precise active arrays spanning rented Context domains for Search

scrape_html

crawlbase.com` datacenter proxies. Identify bounded routing spaces inside the Headless Crawlbase Engine

scrape_js_rendered

Retrieve explicit Cloud logging tracing explicit Payload IDs limitlessly

scrape_json_format

Perform structural extraction of properties driving active Fields

scrape_linkedin

Retrieve the exact structural matching verifying Blueprint constraints

scrape_twitter

Fetch elaborate explicit mapped limits via Crawlbase X extraction

Example Prompts for Crawlbase in CrewAI

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

"Scrape the price and features from this Amazon product: [Amazon URL]"

"Get Google search results for 'best machine learning platforms 2024'"

"Take a screenshot of https://example.com"

Troubleshooting Crawlbase MCP Server with CrewAI

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

Crawlbase + CrewAI FAQ

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