Zillow MCP Server

MCP数据服务

提供方 HasData · 包名 @hasdata/zillow-mcp

数据服务 stdio · 本地进程 OAuth 授权 社区 / 第三方 Claude DesktopClaudeCursorVS Code
查看接入方式

HasData's hosted Zillow MCP server lets AI agents search homes for sale, rentals and sold listings, then retrieve property details, price history and Zillow estimates as structured JSON.

一句话选型结论

按资料字段整理

Zillow MCP Server 属于数据服务类 MCP 服务器,stdio · 本地进程,OAuth 授权,可直接接入 Claude Desktop、Claude、Cursor 等,有可直接执行的安装命令。接入前先确认权限范围;涉及写入、删除或付款的操作,建议先在测试环境验证。

分类数据服务 传输方式stdio · 本地进程 鉴权OAuth 授权 部署方式本地部署
GitHub 星标 未标注 仓库热度,无公开仓库时显示未标注
工具数 未标注 暴露给模型的工具数量
资源 / 提示词 0 / 0 资源与提示词模板数量
维护方 社区 / 第三方 核验等级 仅资料核对

工具与能力

数据服务
数量来自来源目录的标注,具体工具清单以官方文档为准
工具数量未标注暴露给模型可调用的工具个数
资源数量0可读取的资源条目
提示词数量0内置提示词模板数量

能力标签

zillow real%20estate hasdata

支持客户端

适用场景

zillowreal%20estatehasdata

安装与配置

stdio · 本地进程 OAuth 授权
客户端在本机拉起子进程,数据不出本机
npx -y @hasdata/zillow-mcp

这条命令只是入口,具体启动参数请按官方文档补齐,不要直接照搬到别的服务器。

  1. 1
    准备运行环境

    stdio 服务在本地起进程,需要先装好 node,再按安装命令拉取依赖。

  2. 2
    安装服务

    复制上面的安装命令执行;命令里带占位符的位置,换成自己的密钥或路径。

  3. 3
    写入客户端配置

    在客户端的 MCP 配置里填好启动命令和参数,保存后完全退出客户端再打开,让新配置生效。

  4. 4
    验证是否可用

    连接成功后随便调一个只读工具,确认能返回结果,再接入正式流程。

典型使用场景

3 类
按分类与标签整理的常见用法,具体以官方文档为准
数据库查询

用自然语言查库、取数,不用手写 SQL。

数据同步与清洗

把多来源数据拉到一处做整理。

报表取数

按口径快速拉出统计结果。

选择建议

选之前先看这几条
按条目字段给出的判断,不替你决定用不用

值得选的地方

  • 有现成的安装命令,不用自己找入口,照着跑就能起服务。
  • 已适配 Claude Desktop、Claude、Cursor,换客户端不用重新研究配置。

先想清楚的地方

  • stdio 方式要求本地装好运行时(如 Node.js),换机器要重新装一遍。
  • 使用前要准备好OAuth 授权对应的凭据,并按最小权限配置。
  • 资料没标注工具数量,实际能力要装好后确认。
  • 版本更新与行为细节以官方仓库为准。

更适合

  • 需要在数据服务场景里让模型直接调用外部能力的人。
  • 已经在用 Claude Desktop、Claude 的用户,接入路径最短。
  • 想先快速试一下、能接受在本地或自有环境跑服务的人。

不太适合

  • 完全不想在本地装环境的人。
  • 不方便管理密钥或第三方授权的人。
  • 需要厂商级 SLA 和技术支持的生产环境。

同类对比

6 个同类
同分类里挑最接近的几条,字段以各自详情页为准
MCP 服务器工具数传输方式部署方式安装命令最后核验
Zillow MCP Server当前 未标注 stdio · 本地进程 本地部署 有 未标注
Memory 9d25f64e 9 未标注 未标注 无 2026-05-17
Getzep MCP 9 stdio · 本地进程 本地部署 有 2026-05-17
anything-llm 未标注 stdio · 本地进程 本地部署 有 2026-04-11
Prisma MCP Server 未标注 stdio · 本地进程 本地部署 有 2026-05-17
Astr Bot 未标注 stdio · 本地进程 本地部署 有 2026-05-17

服务器档案

数据服务
字段来自项目仓库与公开索引,中文说明由本站标注
提供方HasData上游标注的维护方 HasData
分类数据服务本站按上游分类展示
连接方式stdio · 本地进程客户端在本机拉起子进程,数据不出本机
鉴权方式OAuth 授权远程服务建议用最小权限凭据
维护方社区 / 第三方核验等级 仅资料核对
包名 / 运行时@hasdata/zillow-mcp · node本地安装时用到的包标识与运行时
部署类型本地部署上游给出的部署形态
最近核验未标注上游最后核验时间

详细介绍

18.3 KB
来自项目仓库与上游目录的原文,未做删改

Zillow MCP Server

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 nothing to host.

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

1,000 free credits every month, no card required, which is 100 Zillow calls at the base rate.```
https://mcp.hasdata.com/mcp?apis=zillow


- Prompts and resources

## Contents

- What you need
- Quick start
- Example prompts
- Tools
- Errors and failure paths
- Pricing, free tier and limits
- Tool selection
- How it compares
- FAQ
- HasData links
- Development
- Contributing
- License

## What you need

An MCP client and a HasData API key from the dashboard, free to create with no card, and the free tier covers about 100 calls a month at the 10-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. 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/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.

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

Claude Desktop

Settings, then Connectors, then Add custom connector, then paste https://mcp.hasdata.com/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" }
    }
  }
}

Cursor

~/.cursor/mcp.json for every project, or .cursor/mcp.json for one:```json
{
"mcpServers": {
"zillow": {
"url": "https://mcp.hasdata.com/mcp?apis=zillow",
"headers": { "x-api-key": "HASDATA_API_KEY" }
}
}
}


Windsurf

`~/.codeium/windsurf/mcp_config.json`. Windsurf calls the field `serverUrl`, not `url`:```json
{
  "mcpServers": {
    "zillow": {
      "serverUrl": "https://mcp.hasdata.com/mcp?apis=zillow",
      "headers": { "x-api-key": "HASDATA_API_KEY" }
    }
  }
}

VS Code

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


## 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 10 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, 10 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, 10 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, 40 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, 10 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

| Tool | What it returns |
| --- | --- |
| `hasdata_zillow_listing_getRealEstateListings` | Each listing with address, Zillow URL/zpid, price, Zestimate, beds/baths, sqft, home type, status, days on Zillow, coordinates, thumbnail, and listing agent. 10 credits a call |
| `hasdata_zillow_property_getPropertyDetails` | Address, list price, Zestimate and Rent Zestimate, price and tax history, beds/baths, living area, lot size, year built, home type, HOA, days on Zillow, listing…. 10 credits a call |

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`

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

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 15 instead of 10

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": 318100, "estimatedSaleRange": "$302K - $334K", "rentZestimate": 2286 },
"address": { "street": "6116 Speyside Dr", "county": "Travis County" },
"agentInfo": { "agentName": "Marie Coleman", "brokerName": "eXp Realty" },
"priceHistory": [{ "date": "2026-08-24", "price": 320000, "event": "listedForSale" }],
"schools": { "elementarySchool": { "name": "Bluebonnet Trail", "district": "Manor ISD" } }
}


## Prompts and resources

The server ships 2 prompts, ready-made workflows a client can offer instead of making the user compose a tool call.

| Prompt | What it does |
| --- | --- |
| `zillow_listings` | Find homes for sale, for rent or sold in an area. |
| `zillow_property` | Get the full details of one Zillow property. |

Alongside them the server exposes 11 resources, one per parameter whose accepted values are a fixed list. Reading one is cheaper than learning the vocabulary from a rejected call, and it costs no credits. Each URI is `hasdata://zillow/`.

| Parameter | Values | What it selects |
| --- | ---: | --- |
| `type` | 3 | The type of listing. |
| `sort` | 11 | The sorting option for the search results. |
| `homeTypes__` | 7 | An array of home types to filter the listings. |
| `listingPublishOptions__` | 7 | An array of listing publish options. Use `ownerPosted` for listings by owner and `agentListed` for listings by agent. |
| `propertyStatus__` | 3 | An array of property statuses. |
| `tours__` | 2 | An array of tour options. |
| `otherAmenities__` | 8 | An array of other amenities. |
| `views__` | 4 | An array of views. |
| `pets__` | 3 | An array of pet options. |
| `basement__` | 2 | An array of basement options. |
| `daysOnZillow` | 9 | The number of days a listing has been on Zillow. |

Both lists are served without an API key, so a client can read them before a user has signed up.

## Errors and failure paths

Your client almost never sees an HTTP error code from a tool call. The MCP layer answers 200 and puts the failure inside the result, with `isError` set to `true` and the reason as text. The agent reads a message where you might expect a status line.

**A wrong key surfaces as tool output, not as a failed connection.** `tools/list` accepts any non-empty key and returns both tools, so the client completes its handshake and shows green. The first tool call then comes back with `isError: true` and the text `HasData API error: 401 Unauthorized`. Watch for that string, because nothing earlier in the flow reports the problem.

**A missing key is the one real HTTP error.** Authorization runs before any tool, and the connection itself fails with 401. CORS headers are present, and a browser client reads the status and not an opaque network failure.

**An argument that breaks a tool's schema is rejected before it becomes a scrape.** The server answers with `isError: true` and the text `MCP error -32602: Input validation error`, naming the offending field. Nothing is fetched and nothing is charged.

**A search with no matches returns a successful result with an empty `properties` array**, not an error. A location and filter set with no inventory still comes back with `requestMetadata.status` set to `ok`. Test for the array length before you iterate.

**A property that has been delisted returns 400** with `requestMetadata.status` set to `error`. A URL from an old search can point at a listing that is gone.

Results that carry data also carry a `requestMetadata.id` worth quoting in support.

## Pricing, free tier and limits

Each Zillow tool costs **10 credits per successful call**. Turning on `extractAgentEmails` adds 5 credits to the property call, 15 instead of 10, so leave it off unless you need the email. Response size does not change the price.

The free tier is **1,000 credits every month with no card**, which is 100 Zillow calls at the base rate. It renews with the billing cycle, so a low-volume agent runs on the free tier indefinitely.

Paid plans start at **$59 a month** for 200,000 credits, which is 20,000 calls. The unit price falls with volume, from **$1.48 per 1,000 calls** on the entry plan to **$0.60** on Basic and **$0.41** across the Growth tiers. Current figures live on the pricing page.

Your plan also sets concurrency. The free tier allows 1 request at a time, Startup 5, Basic 15, and the Growth tiers run from 50 to 500. Handle the overflow case defensively in anything unattended.

A request that comes back non-200 is not billed. A successful call that finds nothing is still a call.

## Tool selection

The `apis` query parameter decides which tools your agent sees. Fewer tools means less context spent on tool definitions, and fewer chances for the model to reach for the wrong one.```
?apis=zillow                     the two tools in this repo
?apis=zillow,redfin              add Redfin real estate
?apis=zillow,google_maps         add Google Maps places

The parameter takes provider names like zillow and individual API names like zillow_listing. Misspelled names are ignored. If every name is wrong the request fails with 400, and the body lists both what it did not recognise and every valid value. Drop the parameter and the same endpoint exposes all 57 HasData tools.

How it compares

Zillow's own API programs are for members and partners moving their own inventory, such as the Bridge Interactive and Mortgage APIs, not a self-serve way to read the public market. For searching listings and reading arbitrary properties, scraping the public pages is the route, and this server does that behind a stable schema.

Zillow partner APIs This server
Purpose Move your own or MLS inventory Read the public market
Access Membership or partner approval One key and one URL
Search across the market Restricted Yes, with rich filters
Setup Business onboarding None
Output Partner feeds Structured JSON, price and beds pre-parsed

What this server does not do. No posting, no lead submission, no account data. It reads what a signed-out visitor can see on Zillow.com.

FAQ

Is there an official Zillow MCP server?

Zillow does not publish one. This one is maintained by HasData and reads public Zillow.com pages.

What is a Zillow MCP server?

A server that exposes Zillow listing data as tools an AI client can call. The client sends a tool call over the Model Context Protocol, the server fetches the data and returns structured JSON, and the model works with the result. This one exposes two tools and runs remotely.

Do I need a Zillow account or API key?

No. The only credential is your HasData key. The tools read public Zillow.com pages.

Why does a search result not show price history or schools?

Because Zillow does not put them on the search card. They live on the property page, which the details tool reads by URL. Search to shortlist, then call the property tool for depth.

What does the price estimate mean?

The zestimate object holds Zillow's own estimated value, a range around it, and a rental estimate. It is a model output, not an appraisal or a confirmed sale price. Treat it as an estimate.

Can I use this together with other HasData APIs?

Yes. The apis parameter takes a list, and ?apis=zillow,redfin gives your agent Zillow plus Redfin. Drop the parameter and you get everything.

Is HasData affiliated with Zillow?

No. HasData is an independent service and is not affiliated with, endorsed by, or sponsored by Zillow Group, Inc. Zillow is a trademark of its respective owner.

Compliance and personal data

HasData accesses publicly available data only. A platform's terms may restrict automated access, and you are responsible for your own compliance. Where the data you collect includes personal information, such as a listing agent's contact details, make sure you have a lawful basis for it under GDPR, CCPA or the equivalent rules in your jurisdiction.

HasData links

Product page and request builder · Zillow Scraper API
Server documentation · MCP server docs
Every HasData tool in one server · HasData/hasdata-mcp
Client walkthroughs · MCP clients and integrations
Everything else we scrape · Zillow Scraper API and 54 more
Plans and credit costs · Plans and credit costs
Keys and usage · HasData dashboard
Node launcher on npm · @hasdata/zillow-mcp
Python launcher on PyPI · hasdata-zillow-mcp

Development

This repository is configuration and documentation for a remote server. There is no build step and nothing to containerize.

The tests in test/ assert the tool contract, the part that can break without a commit here. They check that ?apis=zillow returns exactly two tools, that every tool still declares its required parameters, that no name changed, and that the key in use is actually accepted. That last check calls a tool for real and costs 10 credits, which is the price of a canary that can fail for the right reason.```bash

macOS and Linux

HASDATA_API_KEY=your_key_here npm test

Windows PowerShell

$env:HASDATA_API_KEY="your_key_here"; npm test
```

The same suite runs in CI on every push and once a week on a schedule, because the upstream tool list can change without anyone touching this repository. A failure means the tool list moved, the key stopped working, or the endpoint was unreachable, and the assertion message says which.

Contributing

Corrections to the tool tables and the response samples are the most useful contribution, because those are the parts that drift. Include the call you made and the response you got. Pull requests from forks run the suite without a key, and the live checks skip instead of going red.

License

MIT. See LICENSE.

常见问题

8 问
答案由本站依据条目字段整理,不引用上游原文
Zillow MCP Server 怎么安装?

在客户端按下面的安装命令接入:npx -y @hasdata/zillow-mcp。对应的包名是 @hasdata/zillow-mcp。装完在客户端配置里引用同一个包或端点。

Zillow MCP Server 怎么在 Claude Desktop、Claude、Cursor 里配置?

它的传输方式是stdio · 本地进程,在客户端的 MCP 配置里填好启动命令和参数,保存后完全退出客户端再打开,配置才会生效。

Zillow MCP Server 收费吗?

本站不代收费用,也没有标注具体价格。是否收费取决于服务本身和背后的接口额度,正式使用前按官方说明确认。

Zillow MCP Server 需要 API Key 吗?

资料标注需要OAuth 授权认证,使用前准备好对应凭据,并按最小权限配置。

Zillow MCP Server 支持哪些客户端?

资料标注支持 Claude Desktop、Claude、Cursor、VS Code、Windsurf、Gemini CLI;其他客户端只要能配置 MCP Server,也能用同样的命令或地址接入。

Zillow MCP Server 能提供哪些能力?

资料显示能力标签包括 zillow、real%20estate、hasdata。具体工具清单以官方文档为准。

Zillow MCP Server 需要什么运行环境?

运行时为 node;属于本地进程,需要在本机装好运行环境。

Zillow MCP Server 是本地还是远程?

它是本地进程(stdio),由客户端在本机拉起。传输方式为stdio · 本地进程。

热门专题

按标签挑服务器
全部专题 →

服务器信息以作者仓库与官方文档为准;分类、传输方式与鉴权方式的中文说明为中文整理,最近核验 未标注。