Is an API Key required for OpenFEMA?

No, OpenFEMA data is public. However, using an API Key is recommended for heavy users to ensure higher rate limits and consistent access.

What types of disasters are included in the data?

The database includes all incidents resulting in a federal declaration, such as floods, hurricanes, fires, snowstorms, and severe storms.

How can I filter results by state?

Use the `filter` parameter with OData syntax, for example: `state eq 'CA'` to retrieve records only for California.

FEMA MCP Server for CrewAI 11 tools — connect in under 2 minutes

Name: FEMA
Availability: InStock
Author: Vinkius

docs.crewai.com/mcp/overview

Built by Vinkius GDPR 11 Tools Framework

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

Connect to the OpenFEMA public database through any AI agent and gain instant access to official data regarding disasters, emergency management, and federal assistance programs.

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

Disaster Tracking — List official FEMA disaster declarations since 1953 and fetch detailed metadata for specific incidents natively
Emergency Orchestration — List emergency management agencies by state to verify local coordination contacts flawlessly
Assistance Analysis — Query housing assistance program data and individual assistance registrations to analyze recovery efforts natively
Grant Inspection — Access hazard mitigation assistance projects and grant details to monitor community safety investments flawlessly
Regional Insights — List official FEMA regions and web center locations to understand federal jurisdictional boundaries synchronously
Public Data Access — Retrieve raw structured data from the official U.S. Federal Emergency Management Agency API without complex manual exports

The FEMA MCP Server exposes 11 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 FEMA to CrewAI via MCP

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

Why Use CrewAI with the FEMA MCP Server

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

FEMA + CrewAI Use Cases

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

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

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

FEMA MCP Tools for CrewAI (11)

These 11 tools become available when you connect FEMA to CrewAI via MCP:

get_disaster_applications

Get statistics on disaster assistance applications

get_emergency_agencies

List emergency management agencies by state

get_fema_regions

List official FEMA regions

get_fema_web_centers

List FEMA web center locations

get_hazard_mitigation_grants

Get data on hazard mitigation assistance projects

get_housing_assistance

Get data regarding FEMA housing assistance programs

get_individuals_program

Get data on individuals and households program registrations

get_me

Get current API status

get_public_assistance_applicants

List applicants for FEMA public assistance

get_registration_intake

Get data from individual and household program registrations

list_disaster_declarations

List recent official FEMA disaster declarations

Example Prompts for FEMA in CrewAI

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

"List recent disaster declarations in Florida."

"Get emergency management agency info for California."

"Show hazard mitigation projects in Texas."

Troubleshooting FEMA MCP Server with CrewAI

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

FEMA + CrewAI FAQ

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