Do I need an API key?

No! ReliefWeb's API is completely free and open. No authentication required. Just subscribe and start searching. Data is updated continuously.

What kind of reports are available?

ReliefWeb hosts 300,000+ reports including situation reports, assessments, press releases, maps, infographics and evaluations from UN agencies, NGOs, governments and research organizations.

Can I search reports by country?

Yes! Use get_reports with the country parameter to filter reports by country name. You can also filter by disaster type, theme, format, date range and organization simultaneously.

ReliefWeb MCP Server for CrewAI 9 tools — connect in under 2 minutes

Name: ReliefWeb
Availability: InStock
Author: Vinkius

docs.crewai.com/mcp/overview

Built by Vinkius GDPR 9 Tools Framework

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

Connect to ReliefWeb and explore the world's largest humanitarian information database through natural conversation — no API key needed.

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

Report Search — Search humanitarian reports, situation updates and assessments with filters for country, disaster, theme, format, organization and date range
Disaster Data — Browse tracked disasters including earthquakes, floods, cyclones, droughts and conflicts
Countries — Get country information and associated humanitarian data
Organizations — Find UN agencies, NGOs and government bodies publishing humanitarian data
Job Postings — Search humanitarian job opportunities worldwide
Themes & Formats — Explore report categories (Health, Shelter, Food, Protection) and formats (Situation Report, Assessment, Map)

The ReliefWeb MCP Server exposes 9 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 ReliefWeb to CrewAI via MCP

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

Why Use CrewAI with the ReliefWeb MCP Server

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

ReliefWeb + CrewAI Use Cases

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

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

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

ReliefWeb MCP Tools for CrewAI (9)

These 9 tools become available when you connect ReliefWeb to CrewAI via MCP:

get_countries

Returns country names, ISO codes and associated disaster counts. Useful for finding country IDs to use in report searches. Search countries in the ReliefWeb database

get_disasters

Returns disaster names, types (earthquake, flood, cyclone, etc.), start dates and affected countries. Search disasters (earthquakes, floods, cyclones, etc.)

get_formats

Returns format names and IDs (Situation Report, Assessment, Press Release, Map, etc.) for filtering reports by type. Get report formats

get_jobs

Returns job titles, organizations, locations, types and posting dates. Search humanitarian job postings

get_organizations

Returns organization names, types and report counts. Search humanitarian organizations

get_report

Returns full report metadata including title, body, source, themes, countries, disasters and file attachments. Get a specific report by ID

get_reports

Supports free-text query, date range filtering, and filtering by country, disaster type, theme, format, source, organization and language. Returns report titles, dates, sources, themes and links. Search humanitarian reports

get_sources

Returns source names and types. Get report sources

get_themes

Returns theme names and IDs for filtering reports by topic (Health, Shelter, Food, Protection, etc.). Get report themes

Example Prompts for ReliefWeb in CrewAI

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

"Find situation reports about earthquakes in Turkey."

"What disasters are currently active?"

"Show me humanitarian job postings in South Sudan."

Troubleshooting ReliefWeb MCP Server with CrewAI

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

ReliefWeb + CrewAI FAQ

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