How do I install Zillow?

Zillow is a local plugin. Install it using npm package: zillow-mcp and add the generated configuration snippet to your AI app's MCP config file. Then restart your AI app.

What credentials does Zillow need?

Zillow requires the following credentials or environment variables: ZILLOW_WS_PORT. You can find setup instructions on the server detail page.

What AI apps work with Zillow?

Zillow uses the Model Context Protocol (MCP) and works with any MCP-compatible AI app, including Claude, ChatGPT / Codex, Gemini, Copilot, Cursor, and more.

Back to Browse

Zillow MCP Server

by Chris Hall

Developer ToolsLow Risk10.0LocalNew

Free

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

About

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

Security Report

10.0

Low Risk10.0Low Risk

Valid MCP server (1 strong, 1 medium validity signals). No known CVEs in dependencies. Package registry verified. Imported from the Official MCP Registry. Trust signals: trusted author (18/18 approved).

9 files analyzed · 1 issue found

Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.

Permissions Required

This plugin requests these system permissions. Most are normal for its category.

file_system

Check that this permission is expected for this type of plugin.

What You'll Need

Set these up before or after installing:

Override the fetchproxy WebSocket port (default 37149).Optional

Environment variable: ZILLOW_WS_PORT

How to Install

Add this to your MCP configuration file:

{
  "mcpServers": {
    "io-github-chrischall-zillow-mcp": {
      "env": {
        "ZILLOW_WS_PORT": "your-zillow-ws-port-here"
      },
      "args": [
        "-y",
        "zillow-mcp"
      ],
      "command": "npx"
    }
  }
}

Documentation

View on GitHub

From the project's GitHub README.

zillow-mcp

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 fetchproxy extension. Akamai / PerimeterX see a real browser session, not a Node process — but you should still 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

Tool	Purpose	Auth-scoped
`zillow_search_properties`	Search listings by location, status, price band, beds/baths, home type
`zillow_get_property`	Full record for a zpid (price, Zestimate, beds, schools, neighborhood, price history)
`zillow_get_zestimate_history`	Time series of Zestimate values (and rent Zestimate where available)
`zillow_get_saved_searches`	Your saved searches with new-listing counts and notification frequency	✓
`zillow_get_saved_homes`	Your favorited homes with current price + Zestimate	✓
`zillow_get_market_report`	Median sale/list/rent, days on market, inventory, ZHVI for a region
`zillow_calculate_mortgage`	Local PITI calculator — principal+interest, taxes, insurance, HOA, PMI (no network)

Install

Option A — npx (after publishing)

Add to .mcp.json:

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

Option B — from source

git clone https://github.com/chrischall/zillow-mcp
cd zillow-mcp
npm install
npm run build

{
  "mcpServers": {
    "zillow": {
      "command": "node",
      "args": ["/path/to/zillow-mcp/dist/bundle.js"]
    }
  }
}

One-time browser setup

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

git clone https://github.com/chrischall/fetchproxy
cd fetchproxy
npm ci
npm --workspace=@fetchproxy/extension-chrome run build

Then in Chrome: chrome://extensions → toggle Developer mode → Load unpacked → pick packages/extension-chrome/dist/.

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  │◀──────▶│  fetchproxy      │◀────────────▶│ zillow.com  │
│ (Claude, etc.) │          │  (Zillow MCP)    │ :37149 │  extension       │   (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 fetchproxy extension. Akamai sees a real browser making a real request from a real session — _abck, TLS fingerprint, cookies all match the page that's already on screen. No headless browser, no impersonation, no proxy farm.

Commands

npm test               # vitest, mocked transport, no network
npm run test:watch
npm run test:coverage
npm run build          # tsc --noEmit + esbuild bundle → dist/bundle.js
npm run dev            # node dist/bundle.js (after build)