DaedalMap Reverse Geocoding (coordinates to loc_id) MCP server

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.

Website | App | Agent docs | Geometry | Data packs | Downloads | Convert a file | llms.txt

Connect an agent

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

https://app.daedalmap.com/mcp

Claude Code:

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

Codex:

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

Any client that supports streamable HTTP MCP can use the same URL. Start with howgeometryworks for geography jobs, or getcatalog, then getpack, then query_dataset for data. Setup for other clients is in the agent docs.

Discovery and small geography lookups are free. Larger batches, exports, and some data packs are metered, and paid calls return an x402 payment challenge before any charge. get_catalog reports the access lane for each pack.

Tools

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.

The loc_id model

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

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

Shortened. The full README is on GitHub.