Daedal Map

What xyver/daedal-map MCP server does

The xyver/daedal-map MCP server is a map-first geographic query engine and open runtime. It helps agents work with geographic references instead of requiring every workflow to begin as a manually assembled GIS process. Supported workflows include identifying reference systems, transforming coordinates or boundaries, creating crosswalks between geographies, and assigning stable loc_id values.

The runtime can combine user-provided data with prepared geographic data or maintained DaedalMap data packs. The hosted inventory covers disasters, demographics, economics, health, climate, and related global indicators. Examples in the supplied coverage include earthquakes, hurricanes, floods, wildfires, volcanoes, population, CO2, health statistics, balance of payments, and Sustainable Development Goals data.

How it works

The hosted service exposes a streamable HTTP MCP endpoint at https://app.daedalmap.com/mcp, along with an HTTP API. Agents can start with the help operation for onboarding, discover available packs with get_catalog, and inspect geometry coverage with read_geometry_catalog. The entry point and general workflow remain stable as coverage expands.

Geographic data is organized around compatible references and stable identifiers. A developer can bring in a dataset, make its geography compatible with loc_id, and then join it to another prepared dataset or a DaedalMap pack. The runtime supports local data mode and a cloud-data mode that uses local metadata caching and DuckDB httpfs to query Parquet data from object storage. A hosted installation with local data is not described as a supported first-class combination.

Setup and configuration

For hosted use, no local setup is required. The documented MCP endpoint is ready for clients that support streamable HTTP, and the public app can be used by guests. Account and billing surfaces are separate from the public runtime.

For local or self-hosted use, the repository is the developer entry point. The quick-start instructions install dependencies from requirements.txt, copy .env.example to .env, and configure the runtime with DEPLOYMENT, INSTALL_MODE, RUNTIME_MODE, and optionally DATA_ROOT. The smallest local configuration uses local installation and local data. If DATA_ROOT is empty, the application uses its default local app-data location.

No model API key is needed for local data operations. OPENAI_API_KEY or ANTHROPIC_API_KEY is only needed for the built-in local chat interface. Hosted object-storage, account, and control-plane settings are deployment-specific and are not required for the basic local path.

Tools and capabilities

The xyver/daedal-map MCP server supports these documented capabilities:

• Guide onboarding with help.
• Identify geographic reference systems.
• Transform coordinates and boundaries.
• Build geographic crosswalks.
• Assign stable loc_id values.
• List available data packs with get_catalog.
• Inspect geometry availability with read_geometry_catalog.
• Query local data, hosted data, or compatible user-provided datasets.

The hosted runtime currently describes more than 40 curated sources. Disaster records include geographic relationships and cross-disaster links, while the map renders different event types with points, tracks, radial waves, or polygon fills depending on the source.

Limitations and notes

The public repository is the open runtime and self-hosting surface, not the hosted account, billing, or administration system. Scheduled collector infrastructure and private verifier endpoints are outside the public repository. Hosted commercial lanes may require an x402 challenge before charging, while free execution lanes remain available for the documented geography workflows.

The repository and downloadable launcher are separate installation paths intended to converge on the same runtime family. The supplied material does not specify a single executable command for starting the MCP server from the repository, so local deployment details may require following the project files and runtime documentation directly.