Does GDACS have an MCP server?
GDACS maintains an official MCP server.
Read-only disaster alert data (earthquakes, floods, cyclones, volcanoes, wildfires, droughts); no sign-in needed.
- Access
- Remote server
- Endpoint
- https://api.gdacs.org/mcp
- Category
- Other Tools and Integrations
A remote server run by GDACS itself — nothing to install. Documented at registry.modelcontextprotocol.io.
Hosted by the vendor — no install, connect over HTTP with OAuth or a token.
Add it from the terminal, then restart your session:
claude mcp add --transport http gdacs https://api.gdacs.org/mcpAdd --scope user to make it available in every project.
- Open Settings → Connectors
- Click Add custom connector
- Paste
https://api.gdacs.org/mcp - Finish the sign-in prompt, then enable it in the chat's tools menu
Add to .cursor/mcp.json in your project, or ~/.cursor/mcp.json for
every project:
{
"mcpServers": {
"gdacs": {
"url": "https://api.gdacs.org/mcp"
}
}
}A green dot in Settings → MCP means it connected.
Add to .vscode/mcp.json:
{
"servers": {
"gdacs": {
"type": "http",
"url": "https://api.gdacs.org/mcp"
}
}
}Then pick the server from the tools menu in Copilot's agent mode.
- Enable Developer mode under Settings → Apps & Connectors → Advanced
- Choose Create and paste
https://api.gdacs.org/mcp - Complete sign-in, then enable the connector in a new chat
Does GDACS have an official MCP server?
Yes. GDACS maintains an official MCP server, hosted at https://api.gdacs.org/mcp.
How do I connect GDACS to Claude?
Add https://api.gdacs.org/mcp as a custom connector under Settings → Connectors in Claude Desktop or claude.ai, or run "claude mcp add --transport http gdacs https://api.gdacs.org/mcp" in Claude Code.
Do I need to install anything to use the GDACS MCP server?
No. It is a remote server hosted by GDACS, so your MCP client connects to it over HTTP. You authenticate with the vendor rather than installing a package.
How is this verdict verified?
Published to the MCP Registry under GDACS's verified namespace org.gdacs; the only evidence is the registry entry and the endpoint api.gdacs.org/mcp, which sits on the same host as GDACS's public data API and answers MCP initialize as JRC.GDACS.DATA_API. No GDACS documentation page for it was found. GitHub metadata is refreshed every six hours.
Published to the MCP Registry under GDACS's verified namespace org.gdacs; the only evidence is the registry entry and the endpoint api.gdacs.org/mcp, which sits on the same host as GDACS's public data API and answers MCP initialize as JRC.GDACS.DATA_API. No GDACS documentation page for it was found.
- github data refreshed 2026-09-29, then every 6 hours
- vendor docs verified on 2026-09-29
Spotted something out of date? Tell us — corrections ship same-day.