resolve_point — DaedalMap Disaster and Geospatial Data MCP Tool Read-only
resolve_point
(resolve point) is one of 13 tools on the
DaedalMap Disaster and Geospatial Data
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call resolve_point from your client
- Claude Code DaedalMap Disaster and Geospatial Data resolve_point run in your project directory
- Claude Desktop DaedalMap Disaster and Geospatial Data resolve_point ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor DaedalMap Disaster and Geospatial Data resolve_point ~/.cursor/mcp.json
- VS Code DaedalMap Disaster and Geospatial Data resolve_point .vscode/mcp.json
- Zed DaedalMap Disaster and Geospatial Data resolve_point ~/.config/zed/settings.json
- Windsurf DaedalMap Disaster and Geospatial Data resolve_point ~/.codeium/windsurf/mcp_config.json
- Cline DaedalMap Disaster and Geospatial Data resolve_point ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI DaedalMap Disaster and Geospatial Data resolve_point ~/.gemini/settings.json
- Grok DaedalMap Disaster and Geospatial Data resolve_point .mcp.json (in your project root)
- ChatGPT DaedalMap Disaster and Geospatial Data resolve_point Settings → Connectors → Advanced → Developer mode
- Claude.ai DaedalMap Disaster and Geospatial Data resolve_point Settings → Connectors → Add custom connector
- LangChain DaedalMap Disaster and Geospatial Data resolve_point pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http county-map https://app.daedalmap.com/mcpOther tools on this server
This list was read from the server itself, by connecting to it and calling tools/list on 24 September 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.