Geocoding MCP server
{
"mcpServers": {
"daedalmap-geocoding": {
"type": "http",
"url": "https://app.daedalmap.com/mcp/geography"
}
}
}{
"mcpServers": {
"daedalmap-geocoding": {
"type": "http",
"url": "https://app.daedalmap.com/mcp/geography"
}
}
}{
"mcpServers": {
"daedalmap-geocoding": {
"type": "http",
"url": "https://app.daedalmap.com/mcp/geography"
}
}
}{
"servers": {
"daedalmap-geocoding": {
"type": "http",
"url": "https://app.daedalmap.com/mcp/geography"
}
}
}{
"mcpServers": {
"daedalmap-geocoding": {
"type": "http",
"url": "https://app.daedalmap.com/mcp/geography"
}
}
}What it does
DaedalMap is a geographic query engine that resolves coordinates and geographic identifiers to stable location IDs, coordinate transformations, boundary data, and geographic crosswalks. It's designed for developers and analysts who need to make geographic data interoperable, join datasets by location, or query events and indicators for specific places and time windows.
- Query disasters (earthquakes, hurricanes, floods, wildfires) for a specific location and time range to understand hazard context.
- Transform coordinates between reference systems and assign stable identifiers to make local datasets joinable with maintained geographic data packs.
- Compare population, economic, and climate indicators alongside disaster events in the same geographic workflow without assembling separate GIS pipelines.
Tools this server exposes
| Tool | Does |
|---|---|
| help | Provides guided onboarding and documentation for available geographic tools. |
| get_catalog | Lists available data packs across disasters, demographics, economics, and climate. |
| read_geometry_catalog | Shows current geometry coverage and available boundary data. |
This entry comes from the registry but points to no public repository, so there is nothing to check: no commit history, no source, no tool list. It is listed for completeness and left out of search engines.
Before you enable it
An MCP server runs with whatever access you give it. Start with a development account rather than production, and check which tools the server exposes before you let an agent call them unattended.