zillow-mcp

# Zillow MCP Server

<!-- mcp-name: com.hasdata/zillow -->

A hosted Model Context Protocol (MCP) server that gives Claude, Cursor, Windsurf and any other MCP client two read-only Zillow tools. Search for-sale, for-rent and sold listings with rich filters, and read a single property in full, all as structured JSON, with no Zillow account and nothing to host.

It reads public listing pages on Zillow.com that a signed-out visitor can see.

```
https://mcp.hasdata.com/api/mcp?apis=zillow
```

[![Glama score](https://glama.ai/mcp/servers/HasData/zillow-mcp/badges/score.svg)](https://glama.ai/mcp/servers/HasData/zillow-mcp)
[![tool contract](https://github.com/HasData/zillow-mcp/actions/workflows/contract.yml/badge.svg)](https://github.com/HasData/zillow-mcp/actions/workflows/contract.yml)
[![MCP](https://img.shields.io/badge/MCP-remote%20%7C%20streamable%20HTTP-6366f1?style=flat-square)](https://modelcontextprotocol.io)
[![Tools](https://img.shields.io/badge/tools-2-10b981?style=flat-square)](#tools)
[![License](https://img.shields.io/badge/license-MIT-blue?style=flat-square)](LICENSE)

## Contents

- [What you need](#what-you-need)
- [Quick start](#quick-start)
- [Example prompts](#example-prompts)
- [Tools](#tools)
- [Errors and failure paths](#errors-and-failure-paths)
- [Pricing, free tier and limits](#pricing-free-tier-and-limits)
- [Tool selection](#tool-selection)
- [How it compares](#how-it-compares)
- [FAQ](#faq)
- [HasData links](#hasdata-links)
- [Development](#development)
- [Contributing](#contributing)
- [License](#license)

## What you need

An MCP client and a HasData API key from the [dashboard](https://app.hasdata.com/sign-up?utm_source=github&utm_medium=syndication&utm_campaign=zillow-mcp), free to create with no card, and the trial covers about 200 calls at the 5-credit rate. This is a remote server, so the simplest path is a URL and an `x-api-key` header, with no container to run and no Zillow account anywhere in the flow. A client that only speaks stdio reaches it through a thin launcher, published as `@hasdata/zillow-mcp` on npm and `hasdata-zillow-mcp` on PyPI, shown below.

## Quick start

The server URL is the same for every client. We run it hands-on in Claude Code and Claude Desktop. The other blocks follow each client's own documented format for a remote server.

| Field | Value |
| :--- | :--- |
| URL | `https://mcp.hasdata.com/api/mcp?apis=zillow` |
| Transport | HTTP, streamable |
| Auth header | `x-api-key: HASDATA_API_KEY` |

Clients with OAuth support can add the same URL as a connector and sign in without putting a key in a config file.

<details>
<summary><b>Claude Code</b></summary>

```bash
claude mcp add --transport http zillow "https://mcp.hasdata.com/api/mcp?apis=zillow" \
  --header "x-api-key: HASDATA_API_KEY"
```

</details>

<details>
<summary><b>Claude Desktop</b></summary>

Settings, then Connectors, then Add custom connector, then paste `https://mcp.hasdata.com/api/mcp?apis=zillow` and sign in.

For the config-file route, Claude Desktop loads only local (stdio) servers, so it reaches a remote server through a stdio launcher. The `@hasdata/zillow-mcp` package is that launcher, and it reads the key from the environment. Add this to `claude_desktop_config.json`:

```json
{
  "mcpServers": {
    "zillow": {
      "command": "npx",
      "args": ["-y", "@hasdata/zillow-mcp"],
      "env": { "HASDATA_API_KEY": "YOUR_KEY" }
    }
  }
}
```

For Python instead of Node, swap the launcher for the PyPI package, which `uvx` runs without a manual install:

```json
{
  "mcpServers": {
    "zillow": {
      "command": "uvx",
      "args": ["hasdata-zillow-mcp"],
      "env": { "HASDATA_API_KEY": "YOUR_KEY" }
    }
  }
}
```

</details>

<details>
<summary><b>Cursor</b></summary>

`~/.cursor/mcp.json` for every project, or `.cursor/mcp.json` for one:

```json
{
  "mcpServers": {
    "zillow": {
      "url": "https://mcp.hasdata.com/api/mcp?apis=zillow",
      "headers": { "x-api-key": "HASDATA_API_KEY" }
    }
  }
}
```

</details>

<details>
<summary><b>Windsurf</b></summary>

`~/.codeium/windsurf/mcp_config.json`. Windsurf calls the field `serverUrl`, not `url`:

```json
{
  "mcpServers": {
    "zillow": {
      "serverUrl": "https://mcp.hasdata.com/api/mcp?apis=zillow",
      "headers": { "x-api-key": "HASDATA_API_KEY" }
    }
  }
}
```

</details>

<details>
<summary><b>VS Code</b></summary>

`.vscode/mcp.json` in the workspace:

```json
{
  "servers": {
    "zillow": {
      "type": "http",
      "url": "https://mcp.hasdata.com/api/mcp?apis=zillow",
      "headers": { "x-api-key": "HASDATA_API_KEY" }
    }
  }
}
```

</details>

## Example prompts

Prompts, not code. Paste one in and the agent picks the tool itself. Each is annotated with the calls it takes, because every successful call costs 5 credits.

> Search for-sale homes in Austin, TX with at least three beds under $600k, sorted newest first, and give me the ten most recent with price and days on market.

*One call, 5 credits. Price, beds, area and days on market come back on the search result.*

> Take the top result and pull its full detail: price history, tax history, the price estimate, and the assigned schools.

*One call, 5 credits. Those live on the property page, which the details tool reads by URL.*

> Find for-rent condos in Austin that allow cats, then pull the rental estimate on the three cheapest.

*Four calls, 20 credits. One search, then one property call for each of the three.*

> For this property URL, give me the list price, the price estimate, and the last three sales in its price history.

*One call, 5 credits.*

A search result is enough to rank and shortlist. Price history, tax history, the estimate, schools and the agent come from the property call, so a prompt that shortlists then inspects three homes is one search plus three property calls.

## Tools

Two tools, read-only. Samples below are trimmed from real calls, and the numbers move as the market moves. Read them as shapes. Each tool name links to its endpoint reference, which carries the full field list.

The samples are the payload, not the whole response. A `tools/call` result carries one text block, and that text is itself JSON holding `url`, `status`, `text` and `json`, with the scraped data under `json`. From a raw JSON-RPC response the path is `result.content[0].text`, parsed, then `.json`. A chat client unwraps that for you and code talking to the endpoint directly does not.

### Get Zillow real estate listings

[`hasdata_zillow_listing_getRealEstateListings`](https://docs.hasdata.com/apis/zillow/listing?utm_source=github&utm_medium=syndication&utm_campaign=zillow-mcp)

A page of listings by location keyword, filtered.

| Parameter | Type | Required | Notes |
| :--- | :--- | :--- | :--- |
| `keyword` | string | yes | The location to search, such as `Austin, TX` |
| `type` | string | yes | `forSale`, `forRent` or `sold` |
| `price_min_` / `price_max_` | number | | Price band |
| `beds_min_` / `beds_max_` / `baths_min_` / `baths_max_` | number | | Bed and bath bands |
| `homeTypes__` | array | | `house`, `condo`, `townhome`, `multiFamily`, `apartment`, `lot`, `manufactured` |
| `daysOnZillow` | number/string | | `1`, `7`, `14`, `30`, `90`, `6m`, `12m` and up |
| `sort` | string | | `newest`, `priceLowToHigh`, `priceHighToLow`, `squareFeet` and more |
| `page` | number | | Result page |

The reference also documents square-footage, lot-size, year-built and HOA bands, plus `otherAmenities__`, `views__`, `pets__`, `listingType`, `propertyStatus__`, `listingPublishOptions__` and more.

Returns `searchInformation` with `totalResults`, a `properties` array, and `pagination` whose `nextPage` is the URL of the following page. Each property carries `id`, `url`, `homeType`, `status`, `price`, `currency`, a `rentZestimate` rental estimate, `daysOnZillow`, `area` in square feet, `addressRaw` and a structured `address`, `latitude`, `longitude`, `beds`, `baths`, `listingDetails`, `mediaDetails` and `photos`.

```json
{
  "id": "60134551",
  "url": "https://www.zillow.com/homedetails/6116-Speyside-Dr-Austin-TX-78754/60134551_zpid/",
  "homeType": "SINGLE_FAMILY",
  "status": "FOR_SALE",
  "price": 320000,
  "currency": "$",
  "rentZestimate": 2286,
  "daysOnZillow": 0,
  "area": 2277,
  "address": { "street": "6116 Speyside Dr", "city": "Austin", "state": "TX", "zipcode": "78754" },
  "beds": 4,
  "baths": 3
}
```

### Get Zillow property details

[`hasdata_zillow_property_getPropertyDetails`](https://docs.hasdata.com/apis/zillow/property?utm_source=github&utm_medium=syndication&utm_campaign=zillow-mcp)

One property in full, by its URL.

| Parameter | Type | Required | Notes |
| :--- | :--- | :--- | :--- |
| `url` | string | yes | A Zillow property URL, the `url` field from a listing result |
| `extractAgentEmails` | boolean | | Attempt to pull the listing agent's email. Adds 5 credits, so the property call costs 10 instead of 5 |

Returns the full page: `price`, `currency`, `fees`, `beds`, `baths`, `area`, `yearBuilt`, `homeType`, `mlsId`, a structured `address` and `geo`, the `description` and `highlights`, `photos`, `schools`, `daysOnZillow`, `views`, `saves`, an `agentInfo` block, and `priceHistory`, `taxHistory` and `mortgage` arrays. Zillow's own price estimate arrives in a `zestimate` object holding `zestimate`, an `estimatedSaleRange` and a `rentZestimate`. Read it as an estimate, not as a confirmed value.

> `area` is an object here, `{ livingArea, livingAreaUnits }`, not the flat number the search tool returns. Read `area.livingArea` for the square footage on a property page, or a numeric comparison like `area > 2000` silently fails against an object.

```json
{
  "id": 60134551,
  "status": "FOR_SALE",
  "price": 320000,
  "currency": "USD",
  "yearBuilt": 2002,
  "beds": 4,
  "baths": 3,
  "area": { "livingArea": 2277, "livingAreaUnits": "Square Feet" },
  "fees": { "monthlyHoaFee": "$500 annually" },
  "zestimate": { "zestimate": 31810