Zillow Api MCP Server

Connect Zillow Api to Claude, Cursor or any other MCP client and it stops being a tab you switch to. Run comps, pull Zestimates, and scan for-sale, sold & rental listings across 160M+ U.S. homes with one REST call — photos, taxes, schools, and full price history included. Free tier, no card. This repo is a resource hub for the modern. The zillow api mcp server is what makes that connection.

What the server does

There is no public, self-serve Zillow API today for property-level data. Zillow Group's original consumer-developer program, ZWSID, shipped in 2008 and ran for thirteen years before being retired on September 30, 2021. The notice gave existing keys a short wind-down window; after that, every legacy library — pyzillow, python-zillow, aelaguiz/python_zillow, the various Ruby and PHP ports — started returning 403s.

Installation

Because this one is hosted, setup is mostly authentication — you point your client at the endpoint and approve access. Nothing runs on your machine, so there is no runtime to keep patched.

Available tools

The toolset is worth reading before you wire it up, because it tells you what the integration is really for:

• Project — Targets

Credentials and setup notes

Configuration is passed through the environment: ZILLAPI_KEY. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.

Worth knowing first

• Your data travels to the provider's service, so the usual questions apply about what you send and what they retain.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.

Where it fits

Among the developer tooling options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Zillow Api's toolset — Project — is a fair guide to whether it matches your workflow. It is maintained by nikhonit; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.