Featured

Deploy OpenClaw in 60 seconds — 20% off logoDeploy OpenClaw in 60 seconds — 20% off

Launch OpenClaw on Hostinger in about 60 seconds and keep your agent live 24/7. Our referral link gives you 20% off, no coupon code needed.

Launch on Hostinger
Run your Hermes agent on Hostinger, fully managed logoRun your Hermes agent on Hostinger, fully managed

Launch Hermes on Hostinger in one click, fully managed, no VPS knowledge needed. Use code ZACAARON10 for 10% off.

Launch on Hostinger
Crawl and scrape any site into clean data, 10% off logoCrawl and scrape any site into clean data, 10% off

Firecrawl crawls and scrapes any site into clean markdown for your agent. Get 1,000 free credits, and new users get 10% off their first purchase.

Try Firecrawl free
6,000+ web scrapers for your AI agent, start free logo6,000+ web scrapers for your AI agent, start free

Apify gives your agent live web data: 6,000+ prebuilt scrapers and actors, MCP-ready. Sign up free with $5 in usage credits.

Try Apify free
One API to scrape, enrich, and extract the internet. logoOne API to scrape, enrich, and extract the internet.

Context.dev gives your agents a single API to scrape, enrich, and extract live web data — no proxies, no parsers, no maintenance.

Start building free
SetupClaw: done-for-you OpenClaw for founders & exec teams logoSetupClaw: done-for-you OpenClaw for founders & exec teams

White-glove OpenClaw for founders and exec teams (4–50+ employees): we install, harden, integrate your tools, and maintain it — secured from day one.

Get it set up for you
SEO data APIs for your agent, $1 free credit logoSEO data APIs for your agent, $1 free credit

DataForSEO gives your agent live access to SERP results, keyword data, backlinks, and on-page SEO data through one API. New accounts get a $1 credit, good for up to 20,000 keyword or backlink lookups.

Try DataForSEO free
Reach 48,000+ AI builders

A flat monthly placement in front of developers actively installing AI tools. No lock-in, cancel anytime.

Advertise here

Works with

Claude CodeClaude DesktopCursorVS CodeClineCodex CLIOpenClaw+ any MCP client

Install to Claude Code

This server doesn't publish a one-line install command. Follow the setup in the source repository.

Summary

Provides access to IFRC GO Admin API for disaster relief emergency fund (DREF) data, including operations, appeals, and emergencies.

README.md

IFRC GO Admin API MCP Server

A Model Context Protocol (MCP) server that provides access to the International Federation of Red Cross and Red Crescent Societies (IFRC) GO Admin API for disaster relief emergency fund (DREF) data.

Features

  • DREF Operations: Access completed and ongoing disaster relief emergency fund operations
  • Appeals: Query humanitarian funding appeals
  • Emergencies: Get emergency event and disaster data
  • Search & Filter: Search by country, disaster type, and other criteria
  • Caching: Built-in response caching to reduce API load
  • Pagination: Handle large datasets efficiently

Prerequisites

  • Node.js 18.0.0 or higher
  • npm or yarn package manager
  • MCP-compatible client (Claude Desktop, etc.)

Installation

1. Install Dependencies

npm install

2. Build the Project

npm run build

3. Test the Server

npm start

Usage

Configure in Claude Desktop

Add to your Claude Desktop configuration file (~/Library/Application Support/Claude/claude_desktop_config.json on macOS):

{
  "mcpServers": {
    "ifrc-go-admin": {
      "command": "node",
      "args": ["/path/to/your/ifrc-go-admin-mcp-server/dist/index.js"]
    }
  }
}

Available Tools

  1. get_completed_drefs: Retrieve completed DREF operations
  2. get_ongoing_drefs: Get currently active DREF operations
  3. get_appeals: Access humanitarian appeals for funding
  4. get_emergencies: Query emergency events and disasters
  5. search_drefs_by_country: Find DREF operations by country ISO code
  6. search_drefs_by_disaster_type: Search by disaster type (flood, earthquake, etc.)
  7. get_dref_statistics: Get summary statistics about DREF operations

Example Queries for AI Assistants

  • "Show me recent earthquake-related DREF operations"
  • "What are the ongoing emergency appeals in Bangladesh?"
  • "Compare funding amounts for cyclone vs flood disasters this year"
  • "List all completed DREF operations in West Africa"

Development

Scripts

  • npm run build - Compile TypeScript to JavaScript
  • npm run dev - Watch mode for development
  • npm start - Start the production server
  • npm test - Test server startup

API Exploration

Before implementing, explore the API endpoints:

# Test basic connectivity
curl "https://goadmin.ifrc.org/api/v2/dref/?limit=1"

# Check completed DREFs
curl "https://goadmin.ifrc.org/api/v2/completed_dref/?limit=5"

# Search by country
curl "https://goadmin.ifrc.org/api/v2/dref/?country__iso=BD"

Adding New Endpoints

  1. Update Types: Add TypeScript interfaces for new data structures
  2. Extend API Client: Add methods to IFRCAPIClient class
  3. Register Tools: Add tool definitions in ListToolsRequestSchema handler
  4. Implement Handlers: Add case in CallToolRequestSchema handler

Pagination Best Practices

Following IFRC API documentation guidelines:

  • Default limit is 50 records per page
  • Maximum limit is 1000 records per page
  • Stop pagination when returned records < limit
  • Check for empty array [] to confirm no more data
  • Use offset-based pagination with limit/offset parameters

Rate Limiting Considerations

The server includes basic caching (5-minute timeout) to be respectful of IFRC's infrastructure. For production use:

  • Implement exponential backoff for retries
  • Add request rate limiting
  • Monitor API usage and respect any documented limits
  • Consider using webhooks for real-time updates if available

Error Handling

The server includes comprehensive error handling:

  • HTTP errors from the API
  • Invalid parameters
  • Network timeouts
  • Cache management

Authentication

Currently, the IFRC GO Admin API appears to be publicly accessible. If authentication is required:

  1. Add API key management to the IFRCAPIClient class
  2. Include authentication headers in requests
  3. Handle authentication errors appropriately

Data Schema Examples

DREF Operation

{
  "id": 12345,
  "title": "Bangladesh: Cyclone Mocha",
  "country": "Bangladesh", 
  "disaster_type": "Cyclone",
  "amount_requested": 500000,
  "amount_funded": 500000,
  "disaster_start_date": "2023-05-14",
  "status": "completed"
}

Emergency Event

{
  "id": 67890,
  "name": "Morocco Earthquake September 2023",
  "countries": ["Morocco"],
  "disaster_type": "Earthquake", 
  "num_affected": 300000,
  "disaster_start_date": "2023-09-08"
}

Project Structure

ifrc-go-admin-mcp-server/
├── src/
│   └── index.ts          # Main MCP server implementation
├── dist/                 # Compiled JavaScript output
├── package.json          # Project configuration
├── tsconfig.json         # TypeScript configuration
└── README.md             # This file

Contributing

  1. Fork the repository
  2. Create a feature branch
  3. Make your changes
  4. Add tests for new functionality
  5. Submit a pull request

Humanitarian Use Guidelines

This server provides access to sensitive humanitarian data. Please:

  • Use responsibly and respect the humanitarian context
  • Don't overwhelm the IFRC API with excessive requests
  • Consider data privacy when analyzing beneficiary information
  • Contribute improvements back to the humanitarian community

Support

For issues related to:

  • MCP Server: Open an issue in this repository
  • IFRC GO API: Contact IFRC technical support
  • Data Questions: Refer to IFRC GO documentation

License

MIT License - See LICENSE file for details.

Acknowledgments

  • International Federation of Red Cross and Red Crescent Societies
  • Model Context Protocol development team
  • Open source humanitarian technology community

See related servers & alternatives →

Related MCP servers

Browse all →

Related guides

Hand-picked reading to help you choose and use Other servers.