Zillow Mcp

io.github.chrischall由 GitHub 帳號 chrischall 發布v1.3.2更新於 Nov 7, 2026

Zillow real-estate for Claude — search, property details, Zestimates, saved searches & homes

概覽

AI 產生的概覽

為助理提供 Zillow 房地產資料:物件搜尋、物件詳情、Zestimate 估值、價格與稅務歷史、收藏物件和市場報告。

可以做什麼
  • 依地區、狀態、價格、房數/衛浴數與房型搜尋物件,或以地圖分塊徹底掃描某區域並附完整性摘要
  • 取得完整物件紀錄、照片庫、Zestimate 歷史、價格歷史與稅務歷史;將單筆或批次地址解析為 zpid
  • 並排比較最多 12 筆物件,並取得區域市場報告(成交/掛牌/租金中位數、在售天數、庫存)
  • 讀取已登入帳號的已儲存搜尋與收藏物件
  • 在本機完成房貸、可負擔性與租買比較計算,不需連網
  • 檢視並標記目前的 Zillow 工作階段,並對瀏覽器橋接做健康檢查
適用情境
適合在 Chrome 中已登入 zillow.com 時,讓助理研究物件、追蹤價格與 Zestimate、比較候選物件或取得市場統計資料。它針對 Zillow 網站的非正式個人使用,而非官方 API 存取。
執行需求
以 Node.js 本機程序執行(npx zillow-mcp 或建置後的 bundle)。需要在 Chrome 安裝 ContextMint Bridge 瀏覽器擴充功能,並保持 zillow.com 已登入分頁;目前不支援 Safari。選用環境變數:FETCHPROXY_IDENTITY_DIR、FETCHPROXY_WS_HOST、FETCHPROXY_WS_PORT、ZILLOW_OUTPUT_DIR、ZILLOW_COMMUNITIES_FILE、ZILLOW_LOCALITY_ALIASES_FILE、ZILLOW_DEBUG。
安裝前請注意
它透過你自己已登入的瀏覽器工作階段呼叫 Zillow 的私有網頁端點,README 稱這屬於對網站的非正式使用,需自行斟酌;Zillow 可能以驗證碼阻擋請求。請求會帶上你的 Cookie 與瀏覽器身分。它會在 FETCHPROXY_IDENTITY_DIR 下保存長期身分金鑰對,並開啟本機 WebSocket 埠。掃描輸出檔只能寫入 ZILLOW_OUTPUT_DIR 內。已儲存搜尋與收藏物件會讓助理看到你的帳號資料。

安裝

在 SourceWeft 中

  1. 開啟 儀表板中的 Zillow Mcp,將其新增到工作區。
  2. 為需要使用其工具的對話啟用該服務。

Desktop only,透過 STDIO。 STDIO 服務會啟動本機處理程序,因此需要 SourceWeft 桌面主機。

其他 MCP 客戶端

參照 儲存庫 中的啟動說明。

README

zillow-mcp

[CI] [npm] [license]

Zillow real-estate access as an MCP server for Claude — search listings, fetch property details, Zestimate history, your saved searches & homes, and market reports via natural language.

⚠️ Zillow does not publish a public consumer API. The official Bridge API is gated to MLS partners. This server uses the same private endpoints the zillow.com web app uses, routed through your own signed-in browser tab via the ContextMint Bridge browser extension. Every request acts on behalf of your existing session — your cookies, your TLS, your JS context — exactly as if you'd clicked it in the browser yourself. Treat this as informal use of Zillow's website. Use at your own discretion.

Why this exists

The four existing Zillow MCPs all sit on one of two foundations:

  • The Bridge API — requires MLS membership, IDX vendor relationship, or "approved technology partnership" (10+ business-day approval). Consumers can't get in.
  • A paid scraper (RapidAPI, Apify) — adds a third party to the trust path and rate-limits.

None of them can see what you have saved, favorited, or recently viewed — because both Bridge and third-party scrapers are out-of-session. zillow-mcp uses your already-signed-in zillow.com tab.

Tools

ToolPurposeAuth-scoped
zillow_search_propertiesSearch listings by location, status, price band, beds/baths, home type. Optional map_bounds viewport; include_meta reports Zillow's own total vs fetched, so truncation is visible
zillow_sweep_areaExhaustive enumeration of an area: recursive map tiling until no tile is truncated, deduped, with a completeness summary and drift warnings; optional JSON output file (a download link when hosted)
zillow_get_propertyFull record for a zpid (price, Zestimate, beds, schools, neighborhood, price history)
zillow_get_by_addressResolve a free-text address (with optional city/state/zip) to its Zillow zpid + canonical URL
zillow_resolve_addressesBatch-resolve many free-text addresses (or structured rows) to zpids + canonical URLs
zillow_bulk_getFetch full records for many zpids/URLs at once, with partial-result + bot-wall handling
zillow_get_property_photosFull photo gallery for a property — every image embedded in the homedetails page with multi-width jpeg + webp variants and captions
zillow_get_zestimate_historyTime series of Zestimate values (and rent Zestimate where available)
zillow_get_price_historyListing history (Listed/Sold/Pending/etc.) with price + days on market
zillow_get_tax_historyAnnual tax-roll history — taxes paid and assessed value year-over-year
zillow_compare_propertiesSide-by-side comparison of up to 12 properties, with an aligned summary table
zillow_calculate_affordabilityLocal affordability calculator — max purchase price from income/DTI/rates
zillow_estimate_rent_vs_buyLocal rent-vs-buy break-even with appreciation + opportunity cost
zillow_get_saved_searchesYour saved searches with new-listing counts and notification frequency✓
zillow_get_saved_homesYour favorited homes with current price + Zestimate + primary photo✓
zillow_get_market_reportMedian sale/list/rent, days on market, inventory, ZHVI for a region
zillow_calculate_mortgageLocal PITI calculator — principal+interest, taxes, insurance, HOA, PMI (no network)
zillow_healthcheckRound-trip a public Zillow URL through the bridge to localize bridge/extension/Zillow-side failures
zillow_register_sessionRecord which Zillow account the signed-in tab belongs to, in the local session registry (a label only)
zillow_set_active_sessionMark a registered session as the current account label — does not change which account requests use (every call goes through the signed-in browser tab)
zillow_get_session_contextInspect the active session + the registered-session list

Input and output contract

Changes to tool inputs and outputs, so you can adjust any scripts or prompts that call these tools:

  • zillow_compare_properties reports bot-wall rows like zillow_bulk_get does. A row that Zillow keeps blocking with a captcha now comes back as error_kind: "bot_challenge" instead of a generic error kind, so you can tell it apart from a missing listing. The response can also include blocked (how many rows stayed blocked), retry_after_s (how many seconds to wait before retrying just those rows) and pending (how many rows did not finish before the overall deadline; those rows have error_kind: "pending").

  • A zpid must be a number. Every tool that takes a zpid (zillow_get_property, zillow_bulk_get, zillow_compare_properties, zillow_get_property_photos, zillow_get_zestimate_history, zillow_get_price_history, zillow_get_tax_history) accepts a positive whole number, or a string of digits only such as "12345". Any other string, such as "12345_zpid" or a URL, is now rejected as invalid input. Pass a homedetails URL in the url or urls field instead.

  • Pass zpids or urls, not both. zillow_bulk_get and zillow_compare_properties now return an error when a call includes both lists. Before, the urls list was silently ignored. To fetch both kinds, make two calls.

Upgrading

next release

  • zillow_sweep_area on a hosted deployment (mcp-host, where the server and the caller share no filesystem). Running locally, nothing changes.
    • With output_path, the file is no longer written to the server's disk, which you could not reach. It goes to the host's file store as a zip, and the reply carries a download link. The reply has output_url (the signed link to the zip), output_expires_at (when the link stops working, 1 hour by default) and output_file (the file's name inside the zip, the base name of your output_path). It has no output_path.
    • If the host has no file store, an output_path call is refused before any request is made. Leave output_path out to get the listings inline.
    • Without output_path, the listings still come back inline. If they are larger than 10 MiB, they come back as a link instead (the same three fields plus a note, with no results), because the host would reject a reply that large. With no file store the call fails with a "too large" error that tells you to narrow the area.

Acknowledgement of Terms

By using this MCP server, you acknowledge and agree to the following:

1. This server accesses your own Zillow session. Every request is dispatched through your own browser tab (logged in or not) via the ContextMint Bridge extension. It does not — and cannot — access anyone else's account.

2. Zillow's Terms of Use govern your use of this server, just as they govern your direct use of zillow.com. The clauses most relevant here:

You may not use any robot, spider, scraper or other automated means to access the Services for any purpose without our express written permission… nor may you conduct automated queries (including screen and database scraping, spiders, robots, crawlers, bypassing CAPTCHAs or similar precautions).

You are agreeing to those terms — read by the maintainer 2026-05-23 — every time you invoke a tool in this server. Zillow's terms broadly prohibit automated access without written permission; this is an unofficial tool and Zillow has not granted it permission.

3. Personal, non-commercial use only. This project is not affiliated with, endorsed by, sponsored by, or in partnership with Zillow Group. It is a personal automation tool that drives the same Zillow website you would drive by hand — one search at a time, your own saved homes, your own market reports. Do not use it to bulk-extract listings, train models, populate a competing real-estate product, or for any commercial purpose.

4. Stability is not guaranteed. This server reads private internal endpoints (/async-create-search-page-state/, __NEXT_DATA__ blobs, /myzillow/...) that Zillow may change without notice. It may break. It may stop working. That's by design — the surface is not theirs to maintain on our behalf.

5. You accept full responsibility for any consequences of using this server in connection with your Zillow access — rate limiting, account warnings, suspension, IP blocks, captcha walls, or any enforcement action Zillow Group takes. If Zillow objects to your use, stop using this server.

This section is the maintainer's good-faith summary of the terms — it is not legal advice and does not modify or supersede Zillow's actual ToS.

Install

Option A — npx (after publishing)

Add to .mcp.json:

json
{  "mcpServers": {    "zillow": {      "command": "npx",      "args": ["-y", "zillow-mcp"]    }  }}

Option B — from source

bash
git clone https://github.com/chrischall/zillow-mcpcd zillow-mcpnpm installnpm run build
json
{  "mcpServers": {    "zillow": {      "command": "node",      "args": ["/path/to/zillow-mcp/dist/bundle.js"]    }  }}

One-time browser setup

zillow-mcp talks to your browser through the ContextMint Bridge extension, which is shared across every fetchproxy-based MCP (resy-mcp, opentable-mcp, …). Install it once from the ContextMint Bridge releases:

  • Chrome: download the Chrome zip, unzip it, then chrome://extensions → toggle Developer mode → Load unpacked → pick the unzipped folder.
  • Safari: not available yet — it will ship inside the ContextMint app, which has no public download. Use Chrome for now.

ContextMint Bridge is the fetchproxy browser extension under its new name, from the same maintainer — fetchproxy's own README (Install → Extension) points to it. Its source is public at nullnet-app/contextmint-bridge: build it yourself (see that repo's README), or check a release zip against the .sha256 file published beside it before loading it — shasum -a 256 -c contextmint-bridge-chrome-<version>.zip.sha256.

Open zillow.com and sign in. That's all the auth this server needs.

How it works

┌────────────────┐  stdio   ┌──────────────────┐   WS   ┌──────────────────┐    fetch()    ┌─────────────┐│ MCP client     │◀────────▶│  dist/bundle.js  │◀──────▶│  ContextMint     │◀────────────▶│ zillow.com  ││ (Claude, etc.) │          │  (Zillow MCP)    │ :37149 │  Bridge          │   (real TLS, │ (your tab)  │└────────────────┘          └──────────────────┘        │  (separate)      │   cookies)    └─────────────┘

The MCP server runs in Node, but every HTTP call to zillow.com is dispatched into your live browser tab through the ContextMint Bridge extension. Each request rides your existing session — _abck, TLS fingerprint, and cookies all match the page that's already on screen. No headless browser stand-in, no separate identity, no third-party proxy: just your real browser, acting on its own behalf, with the MCP server picking what to ask for.

Commands

bash
npm test               # vitest, mocked transport, no networknpm run test:watchnpm run test:coveragenpm run build          # tsc --noEmit + esbuild bundle → dist/bundle.jsnpm run dev            # node dist/bundle.js (after build)

License

MIT

來源:README.md,提交 d06f1be

工具

0
SourceWeft 尚未在沙箱中啟動過該軟體包,因此其工具未知。

版本歷史

19
  1. v1.3.2最新Nov 7, 2026
  2. v1.3.1Nov 4, 2026
  3. v1.2.5Oct 29, 2026
  4. v1.2.4Oct 16, 2026
  5. v1.2.3Oct 10, 2026
  6. v1.2.2Oct 10, 2026
  7. v1.2.1Oct 7, 2026
  8. v1.2.0Oct 6, 2026
  9. v1.1.8Oct 5, 2026
  10. v1.1.7Oct 5, 2026
  11. v1.1.6Oct 3, 2026
  12. v1.1.5Oct 3, 2026
  13. v1.1.4Sep 28, 2026
  14. v1.1.3Sep 25, 2026
  15. v1.1.2Sep 23, 2026
  16. v1.1.1Sep 23, 2026
  17. v1.1.0Sep 20, 2026
  18. v1.0.0Sep 19, 2026
  19. v0.13.4Sep 16, 2026

評分

已滿足適用檢查項的 50%

該評分衡量此收錄條目的完整程度,依據註冊中心條目、端點與公開來源計算得出。它不是對伺服器本身的評價,也不表示伺服器安全或目前可用:可連通性是帶日期的檢查結果,評分也不包含安裝量或使用者評價。

  • 近 30 天內可連通25 分

    請保持端點能夠回應 MCP 握手;SourceWeft 每 30 天探測一次。

  • 已宣告認證方式10 分

    請在註冊中心條目中宣告憑證請求標頭,或保持端點能夠回應探測,以便判定其認證方式。

  • 已列出工具15 分

    請讓伺服器在無憑證時回應 tools/list,或發布可在沙箱中無憑證啟動的軟體包。

  • 描述必需15 分
  • 圖示10 分
  • 文件15 分
  • 授權條款10 分