Can it read documentation sites that are split into multiple pages?

Yes! You can use the `crawl` tool. For example: 'Crawl the getting started guide at https://example.com/docs'. The agent will fetch the starting page and automatically follow inner links to gather up to 10 pages of context.

How does it handle ads and cluttered websites?

The `read` tool uses the same underlying technology as Firefox's 'Reader View' (@mozilla/readability). It intelligently strips out standard website boilerplate—like navbars, sidebars, footers, and ads—leaving only the title and the clean main article text converted to Markdown.

Is there a limit on how many URLs I can batch process?

Yes, to ensure conversational AI latency remains reasonable, the `batch_read` tool accepts a maximum of 10 URLs in a single request. All 10 URLs are fetched simultaneously in parallel for maximum speed.

Web Scraper MCP Server for CrewAI 5 tools — connect in under 2 minutes

Name: Web Scraper
Availability: InStock
Author: Vinkius

docs.crewai.com/mcp/overview

Built by Vinkius GDPR 5 Tools Framework

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

Connect the Web Scraper utility to any AI agent to give it direct access to the public internet. Instead of letting the AI hallucinate facts, allow it to read real-time articles, parse documentation, and fetch clean text from any URL you provide.

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

Reader View — Convert any cluttered webpage into pristine, readable Markdown by stripping out ads, navbars, and boilerplate using Mozilla Readability logic
Site Crawling — Instruct the AI to crawl a starting URL (like a documentation hub or wiki) up to 10 pages deep automatically
Batch Processing — Fetch up to 10 different URLs in parallel to compare articles or summarize multiple sources at once
Metadata Extraction — Quickly pull SEO titles, descriptions, OG tags, canonical links, and all outbound hyperlinks without downloading the entire page body

The Web Scraper MCP Server exposes 5 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 Web Scraper to CrewAI via MCP

Follow these steps to integrate the Web Scraper 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 5 tools from Web Scraper

Why Use CrewAI with the Web Scraper MCP Server

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

Web Scraper + CrewAI Use Cases

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

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

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

Web Scraper MCP Tools for CrewAI (5)

These 5 tools become available when you connect Web Scraper to CrewAI via MCP:

batch_read

All URLs are fetched in parallel. Maximum 10 URLs per batch. Fetch multiple web pages in parallel

crawl

Maximum 10 pages to keep response size manageable. Crawl a website starting from a URL

extract

Returns: title, description, OG tags, lang, author, robots, canonical, link count. For the full page content, use the read tool instead. Extract structured metadata from a web page: title, description, OG tags, and more

list_links

Internal links share the same hostname as the source page. Extract all hyperlinks from a web page

read

Uses @mozilla/readability (Firefox Reader View) to extract the main article content, then converts to Markdown. Works best for articles, docs, blogs, and Wikipedia. Fetch any public web page and return its full content as clean Markdown

Example Prompts for Web Scraper in CrewAI

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

"Read https://en.wikipedia.org/wiki/Artificial_intelligence and summarize its history."

"Extract the links from https://news.ycombinator.com/"

"Compare these two links: url1.com and url2.com"

Troubleshooting Web Scraper MCP Server with CrewAI

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

Web Scraper + CrewAI FAQ

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