boundary-map — Geocode AI MCP Resource
boundary-map
is one of 1 resource on the
Geocode AI
MCP server. Connect the server and your client can attach it as context.
by client
How to attach boundary-map from your client
- Claude Code Geocode AI Resource/boundary-map run in your project directory
- Claude Desktop Geocode AI Resource/boundary-map ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Geocode AI Resource/boundary-map ~/.cursor/mcp.json
- VS Code Geocode AI Resource/boundary-map .vscode/mcp.json
- Zed Geocode AI Resource/boundary-map ~/.config/zed/settings.json
- Windsurf Geocode AI Resource/boundary-map ~/.codeium/windsurf/mcp_config.json
- Cline Geocode AI Resource/boundary-map ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Geocode AI Resource/boundary-map ~/.gemini/settings.json
- Grok Geocode AI Resource/boundary-map .mcp.json (in your project root)
- ChatGPT Geocode AI Resource/boundary-map Settings → Connectors → Advanced → Developer mode
- Claude.ai Geocode AI Resource/boundary-map Settings → Connectors → Add custom connector
- LangChain Geocode AI Resource/boundary-map pip install langchain-mcp-adapters
Read from the server itself, by connecting to it and calling resources/list on 11 November 2026.
A listing does not declare its resources, so asking is the only way to know them, and this
is what the server actually offers rather than what its listing claims. Names only are
stored; connect the server for each resource's type and contents.