Install
claude mcp add --transport http zillow "https://mcp.hasdata.com/api/mcp?apis=zillow" --header "x-api-key: HASDATA_API_KEY"Who it's for
For people already using Claude, Cursor, or Windsurf who need to search Zillow homes by for-sale, for-rent, or sold status, then read one home in full. This is a hosted MCP with two read-only tools; results are structured JSON. No Zillow account is required, and you do not host the service yourself.
Not for people who do not yet have a HasData API key. The key is created free in the HasData console, with no card required; the trial covers about 200 calls (counted at 5 credits each). This is a remote service. The shortest path is one URL plus an x-api-key request header. It only reads public home pages a logged-out visitor can see on Zillow.com; it cannot see content that appears only after login.
First try in 3 minutes
Follow only the official path: connect Claude over HTTP to the hosted endpoint. Do not treat the npx local launcher as the primary install.
claude mcp add --transport http zillow "https://mcp.hasdata.com/api/mcp?apis=zillow" --header "x-api-key: HASDATA_API_KEY"
Prerequisites: an MCP client on this machine, and an API key from the HasData console. The console is at
https://app.hasdata.com/sign-up?utm_source=github&utm_medium=syndication&utm_campaign=zillow-mcp
The config location is the client entry written by this claude mcp add command. The service name is zillow, and the request header is x-api-key. Replace HASDATA_API_KEY with the real key from your console; do not invent another secret placeholder.
The first call uses the read-only search described in the source: filter homes by for-sale, for-rent, or sold, with the rich filters the source mentions, and get structured JSON back. The source does not give tool function names or a field table, so do not invent search/get names. Success is that the client is connected to
https://mcp.hasdata.com/api/mcp?apis=zillow
and one for-sale / for-rent / sold search returns JSON home records, not a missing-key or header-field error.
Read-only is not zero risk: this call hits the remote HasData service, which then reads public Zillow pages. The trial is billed at about 5 credits per call, about 200 calls.
Use cases
Case 1: search a batch of homes by for-sale, for-rent, or sold status. For people who first pin the status, then inspect structured results. The evidence says filters are rich but does not name every filter field, so only use parameters the client actually exposes that map to these three statuses.
Case 2: read one property in full. For people who already have a target home and only want a complete JSON. The evidence only says “read a single property in full, all as structured JSON”; it does not say whether the input is a Zillow URL or an internal ID. If that is missing, stay with the client's description of that tool; do not invent parameters.
Limits
A HasData API key is required; a Zillow account is not. It only reads public home pages visible to a logged-out visitor. The trial is free, no card required, about 200 calls at about 5 credits each. Remote service, no container needed. The stdio path npx -y @hasdata/zillow-mcp and the HASDATA_API_KEY environment variable are not the main path. The evidence only documents two read-only tools: search the three home statuses, and read one home in full; there are no tool function names and no undo path.
https://github.com/HasData/zillow-mcp