Zillow MCP server: let your AI agent search homes for rent or sale

#What your agent gets

Wield exposes Zillow through wield-mcp, a local MCP server. Your agent finds the recipe with find_recipe and runs it with run.

The search works like Zillow's map list. It returns apartment buildings with the price range for each unit type. It also returns single homes and apartments with price, beds, baths, square feet, status, coordinates and link. Paid showcase and builder placements are left out by default.

You give a US city and state, for example Austin, TX. You choose rent or buy. You can set a maximum price, which is in US dollars and per month for rent. For the full params and example prompts, read the Zillow how-to page.

#How a request flows

1. You ask your agent: "Find homes to rent in Austin, TX with a monthly price under 2,500 dollars."
2. The agent calls find_recipe, then run with zillow.com/search-homes.
3. wield-mcp hands the run to the Wield extension through a local bridge.
4. The extension sends one request from a zillow.com tab. The request carries your own browser session.
5. The results return to your agent. Nothing passes through wield.run.

#What leaves your computer

One request goes to www.zillow.com per run, sent from your own browser tab. Wield logs the method, host, path, status and timing on your computer, and never logs bodies or query values. Telemetry is off by default. Passwords and cookies never leave your computer.

#Zillow terms, in plain words

Zillow's terms prohibit automated queries and scraping. This recipe runs one search page at a time, which you start, from your own browser. Read Zillow's terms yourself. Wield's recipes note known restrictions, and this one is listed above.

#Limits and what is not working yet

• Bot protection stops automated agents. In our benchmark, Zillow returned HTTP 403 to the cloud browser agent in all 9 runs. Wield does not solve bot checks. If a check appears in your own browser, the run stops with site_challenge, and you solve it in your own tab.
• US listings only. The recipe covers US cities. It does not cover Zillow pages for other countries.
• One page per call. Each run returns one page of results. Use page to read more.
• Paid placements are hidden. Showcase and builder placements are dropped unless you set include_paid.

#FAQ

#Is there an official Zillow MCP server?

Not that we know of as of 7 November 2026. Wield is a local MCP server that runs a public recipe for Zillow's search. It is not a Zillow product.

#Which AI apps work with it?

Any MCP client. npx -y wield-mcp init sets up Claude Desktop, Claude Code, Cursor and Codex. Other MCP clients work through the standard stdio config. See AI apps that work with Wield.

#Does it need a login?

No. The search needs no Zillow account. Wield never reads, copies or sends your cookies or passwords.

#How fast is it compared with a browser agent?

In our benchmark, as of 7 November 2026 (preliminary, still running), the Wield recipe passed 9 of 9 runs with a median of 896 ms and no model cost. A Browser Use agent driving Claude Sonnet 5.5 passed 0 of 9 runs. Bot protection blocked it in all 9, so its median of 14.8 s reflects blocked runs only. The full method is on the benchmark page.