Loading...
New York City and Nashville: zoning verdicts, comps from recorded deeds, verbatim hearing testimony, ownership networks — served to Claude, Codex, or any MCP client. One URL, sign-in with your Zonable account, read-only, no pasted keys.
Recorded deeds, issued permits, enacted ordinances, and verbatim hearing testimony — every answer carries its citations and its evidence tier, from codified law to inferred pattern.
Every result says what was searched, how current it is, and what could NOT be checked. A zero means "checked and clear" only when the search actually ran — the connector refuses to fabricate.
Deterministic buildable-capacity computations with their binding constraint, margins, and flags — plus measured approval odds with sample sizes, so entitlement risk is a number, not a mood.
The connector describes every tool to your assistant live — these are the families. Which tools your account sees rides your market (it scopes with your sign-in, not a config file).
Resolve any address, pull the full record card — lot dimensions, districts, overlays with their definitions, sales, timeline, signals.
The codified envelope plus COMPUTED verdicts: NYC max-buildable with its binding constraint, Nashville two-unit checks with margins and flags.
Comps from recorded deeds (three modes: as-is, new-build exit, land), Nashville ARV with claim-checking, area deal scans, candidate screening.
Verbatim hearing testimony, imposed conditions, votes and dispositions across thousands of transcribed public meetings — quotable, cited.
Deed chains, LLC piercing as far as the record allows, portfolios, shared-agent links — with honest notes where a chain stops.
How boards ACTUALLY decide: measured approval rates with n, rezoning precedents, variance odds — statistics over the record, never vibes.
Track parcels with a thesis; every return visit reports what changed — permits, sales, cases — against why you cared.
SQL over the civic data lake for the analytical questions a single lookup cannot answer.
These appear in Claude's “Add from Zonable” attachment menu — each one chains the tools the way an expert would. They live server-side, so they are always current.
Screen a property as a deal — capacity verdict, comps, the record, the flags.
Full underwrite: exit value, entitlement risk priced by measured odds.
The diligence sweep — checked-and-clear vs could-not-check, honestly split.
Can this use go here — envelope, pathways, precedent.
Rank candidate lots like-for-like, with comparability caveats.
Who really owns it — chains, networks, where the record stops.
What was said and decided — the hearing arc for a case, address, or topic.
Prepare for a hearing — the body’s record on this topic, who speaks, what gets imposed.
Deal blast / listing copy — every claim backed by the record it cites.
Create your Zonable account first — the connector signs in with it (OAuth) the first time your assistant uses a tool. The full setup guide has the step-by-step with screenshots.
Settings → Plugins → + → Add marketplace, then install Zonable
ZonableAI/zonable-pluginThe plugin bundles the connector plus the expert skills (paid Claude plans). After installing, open the plugin's Connectors tab, click Install, and approve the sign-in — that step attaches the live record. Prefer no plugin? Settings → Connectors → Add custom connector → https://api.zonable.com/mcp.
An actual exchange (condensed) — every number below is from Nashville's recorded permits, not a demo script.
A 58-unit mixed-use building with ground-floor commercial space and structured parking — the condo regime is recorded as The Jesse, now in per-unit finish-out.
…plus what could NOT be checked (environmental layers unavailable that day), stated as unchecked — never as clear.
Create an account, install the plugin (or add the connector URL), approve the sign-in — and your assistant answers property questions from recorded deeds, issued permits, and sworn testimony instead of guesses.