How is Spider different from Firecrawl?

Spider is built in Rust and optimized for raw speed and volume — it can crawl 100K+ pages per second, making it 10-20x faster than Firecrawl for large-scale operations. Spider also offers lower per-page costs at high volume, built-in stealth mode with fingerprint rotation, and multiple request modes (HTTP, Smart, Chrome). Firecrawl excels at simplicity and LLM-specific features like JSON extraction.

What output formats does Spider support?

Spider supports Markdown, HTML, raw HTML, plain text, JSON (structured extraction), screenshots, and PDF output. You can specify the desired format via the return_format parameter in each request.

How does Spider pricing work?

Spider offers 500 free credits to get started (no credit card required). Paid plans are usage-based with credits consumed per page scraped. The Starter plan begins at $15/month with 12,000 credits. Enterprise plans offer custom pricing with dedicated infrastructure and unlimited concurrency.

Spider MCP Server for CrewAI 3 tools — connect in under 2 minutes

Name: Spider
Availability: InStock
Author: Vinkius

docs.crewai.com/mcp/overview

Built by Vinkius GDPR 3 Tools Framework

Connect your CrewAI agents to Spider through the Vinkius — pass the Edge URL in the `mcps` parameter and every Spider 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="Spider Specialist",
    goal="Help users interact with Spider effectively",
    backstory=(
        "You are an expert at leveraging Spider 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 Spider "
        "and summarize their capabilities."
    ),
    agent=agent,
    expected_output=(
        "A detailed summary of 3 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 Spider MCP Server

Connect your AI agent to Spider.cloud — the fastest web scraping API in the market, built in Rust for maximum performance.

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

What you can do

Scrape Pages — Extract content from any URL as Markdown, HTML, or plain text. Spider handles JavaScript rendering, anti-bot protection, and proxy rotation
Crawl Sites — Recursively crawl entire websites at speeds exceeding 100K pages/second. Follow internal links and extract structured data at scale
Search & Scrape — Search the web and scrape results in a single API call. Combines discovery with extraction for maximum efficiency

Why Spider over alternatives?

10-20x faster than Firecrawl for large crawls (Rust engine vs Node.js)
Lower cost per page at high volume
Built-in stealth mode with fingerprint rotation and residential proxies

The Spider MCP Server exposes 3 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 Spider to CrewAI via MCP

Follow these steps to integrate the Spider 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 3 tools from Spider

Why Use CrewAI with the Spider MCP Server

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

Spider + CrewAI Use Cases

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

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

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

Spider MCP Tools for CrewAI (3)

These 3 tools become available when you connect Spider to CrewAI via MCP:

spider_crawl

Spider.cloud Rust engine follows internal links and scrapes each page. Configure depth and page limits to control scope. Crawl an entire website at blazing speed — up to 100K+ pages/second. Returns content from multiple pages following internal links

spider_scrape

cloud Rust-powered engine to scrape a single URL. Handles JavaScript rendering, anti-bot protection, and proxy rotation automatically. Supports multiple output formats: markdown (default), html, text. Scrape a single web page at high speed using Spider.cloud. Returns clean content in Markdown, HTML, or plain text format

spider_search

Combines search + scrape in one API call for maximum efficiency. Search the web and scrape results in a single high-performance request via Spider.cloud

Example Prompts for Spider in CrewAI

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

"Scrape the homepage of spider.cloud and show me what they offer."

"Crawl docs.python.org and get the first 5 pages."

"Search for 'machine learning frameworks comparison 2026' and scrape the top 3 results."

Troubleshooting Spider MCP Server with CrewAI

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

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

Spider + CrewAI FAQ

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