find_parcels_at_point — GetParcelData MCP Tool Read-only
find_parcels_at_point
(find parcels at point) is one of 7 tools on the
GetParcelData
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call find_parcels_at_point from your client
- Claude Code GetParcelData find_parcels_at_point run in your project directory
- Claude Desktop GetParcelData find_parcels_at_point ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor GetParcelData find_parcels_at_point ~/.cursor/mcp.json
- VS Code GetParcelData find_parcels_at_point .vscode/mcp.json
- Zed GetParcelData find_parcels_at_point ~/.config/zed/settings.json
- Windsurf GetParcelData find_parcels_at_point ~/.codeium/windsurf/mcp_config.json
- Cline GetParcelData find_parcels_at_point ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI GetParcelData find_parcels_at_point ~/.gemini/settings.json
- Grok GetParcelData find_parcels_at_point .mcp.json (in your project root)
- ChatGPT GetParcelData find_parcels_at_point Settings → Connectors → Advanced → Developer mode
- Claude.ai GetParcelData find_parcels_at_point Settings → Connectors → Add custom connector
- LangChain GetParcelData find_parcels_at_point pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http parcels https://api.getparceldata.com/mcpOther tools on this server
This list was read from the server itself, by connecting to it and calling tools/list on 14 November 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.