DaedalMap MCP Server: com.daedalmap/boundaries

This MCP server retrieves loc_id boundary metadata, polygons, scopes, comparisons, and bounded exports. It is described as a live remote MCP server and HTTP API for making geographic references interoperable.

🛠️ Key Features

Retrieve loc_id boundary metadata
Provide polygons, scopes, comparisons
Produce bounded exports

🚀 Use Cases

Identify reference systems
Transform coordinates or boundaries
Build crosswalks and assign stable loc_id values
Join geography-compatible loc_id data with other datasets, including DaedalMap maintained data

⚡ Developer Benefits

Hosted operation (“no setup”) via an MCP endpoint
Guided onboarding through help
Streamable HTTP MCP access
Support for making custom data loc_id compatible

⚠️ Limitations

Designed as a remote hosted MCP server; setup is not required for most callers
Specific tool names and exact tool behaviors are not provided beyond the documented capabilities

(Repo/tool count: 4; Topics: climate, demographics, disaster-data, earthquakes, fastapi, foss, geographic-data, geospatial, llm, local-first, maps, natural-language, open-data, open-source, python, rag, self-hosted.)

DaedalMap

Bring your data. Connect its geography.

DaedalMap is geographic interoperability infrastructure: a loc_id identity model, versioned boundary geometry, published crosswalks between geography systems, and maintained data packs. Resolve coordinates and reference codes to administrative matches, pull compatible shapes and data, and follow crosswalks into other systems such as census tracts, postal areas, watersheds, and electoral districts.

Use it through a remote MCP server, an HTTP API, a map app, downloadable files, or this repository, which is the open runtime behind all of them.

Connect an agent

The hosted MCP server needs no install or account for discovery:

text

https://app.daedalmap.com/mcp

Claude Code:

bash

claude mcp add --transport http daedalmap https://app.daedalmap.com/mcp

Codex:

bash

codex mcp add daedalmap --url https://app.daedalmap.com/mcp

Any client that supports streamable HTTP MCP can use the same URL. Start with get_tool_help with topic='geometry' for geography jobs, or get_catalog, then get_pack, then get_data for data. Setup for other clients is in the agent docs.

Discovery and small geography lookups are free. Larger point/reference batches and some data packs are metered: a paid call returns its exact price before any charge and is paid from account credit with an API key. get_catalog reports the access lane for each pack.

Tools

Job	Tools
Learn the model	`get_tool_help` with a topic or exact tool name
Find what exists	`get_catalog`, then `get_pack` for one selected data pack or geometry family
Query maintained data	`get_data` with a `pack_id`, exact metrics, and structured filters
Inspect one disaster event	`get_event` with an exact `event_id` returned by `get_data`
Coordinates to places	`resolve_point`, then `resolve_deep_point` when Admin 4-6 or one deeper family is needed
Identify a column of codes	`identify_dataset_geography`, `identify_reference_system`
Translate codes between systems	`convert_reference`
Inspect and relate places	`get_loc_id_info`, `compare_geographies`
Retrieve shapes	`get_geometry`

Each tool takes strict JSON arguments. The calling model turns a user's question into those arguments, and the server returns typed errors with recovery guidance when a call is malformed.

This table is the complete public roster, not a roadmap. Bulk export/job builders and direct upstream live-feed wrappers remain internal or paused and are intentionally absent from tools/list.

The loc_id model

loc_id is DaedalMap's geographic identity model. The administrative spine is the main hierarchy and default join path:

text

USA                      country
USA-CA                   state
USA-CA-037               county
USA-CA-037-221710        census tract

Other geography families, such as postal areas, watersheds, tribal areas, and marine regions, keep their own loc_id identities. Published crosswalks connect them to the spine and to each other, and each crosswalk row carries its relationship type, overlap weight, source, and vintage. A direct join works when both datasets declare the same identity; otherwise the connection runs through a crosswalk.

Schema details are in docs/DATA_SCHEMAS.md.

Coverage

Geometry: global baseline plus 8+ deeper countries. The same geography tools work worldwide down to Admin 2. Country releases add deeper administrative tiers and reference families for Australia, Brazil, Canada, France, Germany, Mexico, the United Kingdom, the United States, and more as releases publish.

Data: 20+ maintained data packs covering natural hazards (earthquakes, tsunamis, volcanoes, hurricanes, tornadoes, wildfires, floods, weather alerts), hazard risk and environmental burden, economic and business indicators, currency rates, population, and climate.

The catalogs are the authority for what is available now:

Geometry: app.daedalmap.com/api/v1/geometry/catalog
Data packs: app.daedalmap.com/api/v1/catalog

Downloads

The Downloads page has three kinds of file:

Program - the map app or local MCP runtime, to run DaedalMap on your machine.
Data pack - maintained records for a subject, with source and release evidence.
Geometry package - boundaries and reference geography for a country or family.

Run it yourself

This repository is the open runtime: the FastAPI server, MCP and HTTP API, and map frontend. Use it to self-host, run against your own data, or extend the engine.

powershell

cd county-map
pip install -r requirements.txt
Copy-Item .env.example .env

Set a data folder in .env:

env

INSTALL_MODE=local
RUNTIME_MODE=local
DATA_ROOT=C:/path/to/your/data

Leave DATA_ROOT blank to use the default app-data folder. No cloud storage, database, or account is needed. The repository does not ship a data folder; docs/DATA_INSTALLATION.md covers installing packs.

powershell

python app.py

The app opens at http://localhost:7000, and the same MCP server is at http://localhost:7000/mcp. Discovery routes:

GET /api/v1/guide
GET /api/v1/catalog
GET /api/v1/packs/{pack_id}
POST /api/v1/query/dataset

Model API keys are optional. OPENAI_API_KEY or ANTHROPIC_API_KEY powers the built-in chat panel only; MCP clients bring their own model. A self-hosted instance returns commercial_access_unavailable on paid lanes unless you configure a commercial verifier.

Runtime modes

`INSTALL_MODE`	`RUNTIME_MODE`	Use
`local`	`local`	Your machine, your data folder
`local`	`cloud`	Your machine, Parquet read from object storage you configure
`cloud`	`cloud`	A server deployment reading object storage

In cloud data mode the runtime caches small metadata files locally and queries Parquet in object storage through DuckDB httpfs. Details are in docs/LOCAL_AND_HOSTED.md.

Documentation

docs/CONTEXT.md - technical router for the codebase
docs/API_AND_MCP.md - HTTP routes and MCP surfaces
docs/DATA_SCHEMAS.md - schemas and loc_id conventions
docs/DATA_PREPARATION.md - convert and validate your own data
docs/DATA_INSTALLATION.md - install data locally
docs/PACK_AUTHORING.md - build research packs and corpora
docs/RESEARCH_MCP.md - research with the hosted MCP
docs/RUNTIME_MODES.md - Explore, Research, Ops, and Tutorial
docs/SECURITY_AND_SELF_HOSTING.md - self-hosting securely

Contact

Questions, feedback, and self-hosting issues: support@daedalmap.com

License

MIT. Data packs and geometry carry their own source licenses, listed in each catalog entry.

tool_name	string	optional	Exact tool name from tools/list. Do not combine with topic.
topic	string	optional	Workflow overview. Do not combine with tool_name.
question	string	optional	Optional question used only with a topic overview.

catalog	string	optional	Catalog family. The geography facade defaults to geometry; other facades default to data.
detail	string	optional	Use lite to select a pack, full for expanded metric/query inventories, or download for the complete raw catalog URL.
country_scope	string	optional	Optional ISO3 focus for catalog='geometry' with detail='lite'.
loc_id	string	optional	Optional DaedalMap loc_id for catalog='data'. Combine with time_range to discover packs confirmed for both place and time. For place details without pack filtering, use get_loc_id_info.
time_range	object	optional	Optional inclusive discovery window for catalog='data'. At least one bound is required.

catalog	string	optional	Metadata family. When omitted, geometry facades default to geometry and known geometry-family ids are inferred; all other calls default to data.
pack_id	string	required	Pack identifier from get_catalog. Newly catalog-admitted packs require no MCP schema change.
detail	string	optional	Use lite to decide and start, full for detailed MCP query metadata, or download for the complete raw metadata file.
country_scope	string	optional	Optional ISO3 country for a geometry family. Omit it to learn which countries publish the family; provide it for country-specific versions, vintages, levels, and artifacts.
release_unit	string	optional	Optional non-country geometry release unit such as GLOBAL or MARINE. Do not combine with country_scope.

loc_id	string	optional	DaedalMap loc_id, e.g. 'USA-CA'.
loc_ids	array	optional	DaedalMap loc_ids to inspect together, including every loc_id from a resolve_point stack. Default public cap is deployment-configurable.
include_hierarchy	boolean	optional	When true, include strict stored parent and ancestor data. This never invents a parent edge across mixed releases. Default false.
include_references	boolean	optional	When true, include known external or side-chain references attached to each loc_id. Default false.
systems	array	optional	Optional reference systems to include when include_references is true, such as zcta, nws_fire, overlay_tribal, or overlay_nws_public_zone.
iso3	string	optional	Optional country hint for crosswalk artifacts. Defaults to the loc_id country when possible.
target_admin_level	any	optional	Admin level for crosswalk-backed reverse reference lookup. Inferred when omitted.
min_share	number	optional	Optional minimum target-area share for reverse overlap references.
limit_per_system	integer	optional	Maximum overlap references to return per bridge/system. Default 10.
batch_id	string	optional	Optional caller-supplied batch id for tracing.
request_id	string	optional	Optional caller-supplied request id for tracing.

left_loc_id	string	optional	First DaedalMap loc_id.
right_loc_id	string	optional	Second DaedalMap loc_id.
as_of	string	optional	ISO date or year applied to both identities.
left_as_of	string	optional	Optional ISO date or year for the left identity; overrides as_of.
right_as_of	string	optional	Optional ISO date or year for the right identity; overrides as_of.
include_successors	boolean	optional	Include direct successors and present-day descendants for maintained historical identities. Default true.
items	array	optional	Bounded geography pairs to compare in one call.
batch_id	string	optional	Optional caller-supplied batch id for tracing.
request_id	string	optional	Optional caller-supplied request id for tracing.

DaedalMap Administrative Boundaries (loc_id to polygon)

DaedalMap MCP Server: com.daedalmap/boundaries

🛠️ Key Features

🚀 Use Cases

⚡ Developer Benefits

⚠️ Limitations

Topics

get_tool_help

get_catalog

get_pack

get_loc_id_info

compare_geographies

get_geometry