Zillow MCP Server Comparison: 6 Tested, 3 Actually Work
A recent benchmark tested six Zillow MCP servers to retrieve two‑bedroom rentals in Denver under $2,500. Only three—HasData, Apify (afanasenko), and Apify (maxcopell)—returned complete listings reliably. The others failed or returned incorrect data. The article details setup, results, and cost impl…
The goal was simple: pull a list of two‑bedroom rentals in Denver, Colorado, priced below $2,500, and then fetch the full record for each listing. Zillow offers no official API for this, nor does it host an MCP (Machine‑Readable Content) server, so the task required picking a third‑party MCP provider.
Testing Methodology
On September 9, 2026, six MCP services were wired into Claude Code. Each service was queried three times with the exact same search parameters: place name "Denver, CO" and type "forRent". The official MCP TypeScript SDK was used as the client, with a generous 240‑second timeout. A call was marked as failed if the tool returned an error, an error disguised as a normal result, or an empty list. Latency was measured as the median of successful calls.
Results Overview
- HasData Zillow MCP – Hosted, API key required. 3/3 calls succeeded, returning 41 rentals with 21 fields each and a median latency of 5.4 s.
- Apify, afanasenko actor – Hosted, token required. 3/3 calls succeeded, 15 rentals with 77 fields each, median latency 7.2 s.
- Apify, maxcopell actor – Hosted, token required. 2/3 calls succeeded, 40 rentals with 17 fields each, median latency 13.0 s.
- APIllow – Local, uvx, key required. 3/3 calls succeeded, but returned only 5 sale listings, median latency 16.5 s.
- @striderlabs/mcp-zillow – Local, open source. 3/3 calls returned zero results, median latency 4.2 s.
- chrischall/zillow-mcp – Local, npm package. 0/6 calls succeeded due to missing logged‑in Zillow session.
Detailed Server Walk‑Through
HasData provides a hosted, streamable HTTP endpoint. Adding it to Claude Code is a one‑liner: claude mcp add --transport http zillow "https://mcp.hasdata.com/api/mcp?apis=zillow" --header "x-api-key:$HASDATA_API_KEY". The search tool accepts a place name and type; the benchmark query was {"keyword": "Denver, CO", "type": "forRent"}. The response contains 41 rentals, each with 21 fields such as price, beds, baths, area, address, and a direct listing URL. A subsequent call to get_listing fetches 33 additional fields, totaling a 159 KB payload. Billing is 200 free calls per month, then $59 for 40,000 calls.
Apify – afanasenko actor exposes its actors via a single endpoint. The actor offers three tools: search by ZIP or place, search by Zillow URL, and lookup by Zillow ID. Using the Zillow rentals URL returned 15 listings with 77 fields each, including Zestimates, HOA, tax, and price history. Each call spawns a fresh actor run, so latency includes spin‑up time. The free tier covers one actor run; subsequent runs cost $5.25 per set of three searches.
Apify – maxcopell actor follows a two‑step protocol. The first call submits a Zillow search URL containing searchQueryState and an extraction method, returning run metadata. The second call, get-dataset-items, fetches the actual listings. With the correct path, the pair of calls returned 40 rentals with 17 fields each, 168 KB total, in 12.4–14.5 s. This actor requires the user to manage the two‑step workflow.
APIllow is a Zillow‑only vendor with a Python package. Its search tools return sale listings rather than rentals, so the benchmark query produced five houses for sale. The server uses a job queue, causing delays up to 17 s, and bills per property returned. After 50 free properties, the plan costs $9.99 for 3,333 properties.
@striderlabs/mcp-zillow is an open‑source server built with Playwright and a stealth plugin. The npm package fails to install due to missing src/index.ts. After cloning and building, the server starts instantly but returns zero results for Denver rentals, indicating Zillow’s headless Chromium is delivering an empty page.
chrischall/zillow-mcp is the most downloaded Zillow MCP package on npm, yet it fails in a headless environment because it relies on a logged‑in Zillow session via a browser extension. Without a signed‑in Chrome instance, every call returns “no confirmed browser session.”
Takeaway for Rental Agents
For agents needing a quick, reliable source of Denver rentals under $2,500, HasData is the most consistent: one call returns 41 listings, and a second call fetches the full record. The Apify (afanasenko) actor is the best option when deeper data per listing is required, offering 77 fields per rental, though at a higher cost per run. The Apify (maxcopell) actor delivers the most listings per call but requires handling a two‑step protocol.
The other three services either returned incorrect data (APIllow), zero results (striderlabs), or failed due to session requirements (chrischall). If you run Claude Desktop on a machine where you also browse Zillow, chrischall may become viable, but it is not headless‑friendly.
All vendors charge for usage, and the cost scales with the number of calls. A typical agent would incur one search call plus one record call per listing, so budgeting for monthly usage is essential.
Before committing to a provider, re‑run the benchmark, as vendors frequently update their APIs and pricing.
Why it matters
Reliable access to up‑to‑date rental listings is critical for real‑estate agents, and choosing the right MCP server can save time, money, and avoid data inaccuracies.
Key points
- HasData returns 41 listings with 21 fields in 5.4 s per call
- Apify (afanasenko) offers 77 fields per listing but costs $5.25 per three searches
- Apify (maxcopell) returns 40 listings with 17 fields, requiring a two‑step workflow
- APIllow returns sale listings, not rentals, and bills per property
- Open‑source servers either fail or return empty results
- Agents should re‑run benchmarks before committing to a provider
Frequently asked questions
What is an MCP server?
MCP stands for Machine‑Readable Content; it’s a server that exposes structured data from a website via an API.
Why does HasData need an API key?
HasData hosts its own Zillow MCP and uses the key to authenticate requests and manage usage limits.
Can I use chrischall/zillow-mcp on a headless server?
No, it requires a logged‑in Zillow session via a browser extension, so it only works in a browser environment.
