resolve_parcel_district — ZoningVerdict MCP Tool Read-only
resolve_parcel_district
(resolve parcel district) is one of 12 tools on the
ZoningVerdict
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call resolve_parcel_district from your client
- Claude Code ZoningVerdict resolve_parcel_district run in your project directory
- Claude Desktop ZoningVerdict resolve_parcel_district ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor ZoningVerdict resolve_parcel_district ~/.cursor/mcp.json
- VS Code ZoningVerdict resolve_parcel_district .vscode/mcp.json
- Zed ZoningVerdict resolve_parcel_district ~/.config/zed/settings.json
- Windsurf ZoningVerdict resolve_parcel_district ~/.codeium/windsurf/mcp_config.json
- Cline ZoningVerdict resolve_parcel_district ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI ZoningVerdict resolve_parcel_district ~/.gemini/settings.json
- Grok ZoningVerdict resolve_parcel_district .mcp.json (in your project root)
- ChatGPT ZoningVerdict resolve_parcel_district Settings → Connectors → Advanced → Developer mode
- Claude.ai ZoningVerdict resolve_parcel_district Settings → Connectors → Add custom connector
- LangChain ZoningVerdict resolve_parcel_district pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http mcp https://zoningverdict.com/api/mcp?ref=mcp-registry
Other 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.