zillow-mcp 0.1.0

package/.claude-plugin/marketplace.json

@@ -0,0 +1,36 @@
+{
+  "$schema": "https://anthropic.com/claude-code/marketplace.schema.json",
+  "name": "zillow-mcp",
+  "owner": {
+    "name": "Chris Hall",
+    "email": "chris.c.hall@gmail.com"
+  },
+  "metadata": {
+    "description": "MCP server for Zillow — search listings, fetch property details, Zestimate history, saved searches & homes, market reports. Routes through the user's signed-in zillow.com tab via the fetchproxy browser extension to dodge bot detection.",
+    "version": "0.1.0"
+  },
+  "plugins": [
+    {
+      "name": "zillow-mcp",
+      "displayName": "Zillow",
+      "source": "./",
+      "description": "MCP server for Zillow — search listings, get property details, Zestimate history, saved searches & homes, market reports",
+      "version": "0.1.0",
+      "author": {
+        "name": "Chris Hall"
+      },
+      "homepage": "https://github.com/chrischall/zillow-mcp",
+      "repository": "https://github.com/chrischall/zillow-mcp",
+      "license": "MIT",
+      "keywords": [
+        "zillow",
+        "real-estate",
+        "property",
+        "zestimate",
+        "housing",
+        "mcp"
+      ],
+      "category": "productivity"
+    }
+  ]
+}

package/.claude-plugin/plugin.json

@@ -0,0 +1,23 @@
+{
+  "name": "zillow-mcp",
+  "displayName": "Zillow",
+  "version": "0.1.0",
+  "description": "Zillow real-estate access for Claude — search listings, get property details, Zestimate history, your saved searches & homes, market reports",
+  "author": {
+    "name": "Chris Hall",
+    "email": "chris.c.hall@gmail.com"
+  },
+  "homepage": "https://github.com/chrischall/zillow-mcp",
+  "repository": "https://github.com/chrischall/zillow-mcp",
+  "license": "MIT",
+  "keywords": [
+    "zillow",
+    "real-estate",
+    "property",
+    "zestimate",
+    "housing",
+    "mcp"
+  ],
+  "skills": "./SKILL.md",
+  "mcp": "./.mcp.json"
+}

package/.mcp.json

@@ -0,0 +1,8 @@
+{
+  "mcpServers": {
+    "zillow": {
+      "command": "node",
+      "args": ["${CLAUDE_PLUGIN_ROOT}/dist/bundle.js"]
+    }
+  }
+}

package/README.md

@@ -0,0 +1,103 @@
+# 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](https://www.bridgeinteractive.com/developers/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](https://github.com/chrischall/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 and filters | |
+| `zillow_get_property` | Full record for a zpid (price, Zestimate, beds, schools, history) | |
+| `zillow_get_zestimate_history` | Time series of Zestimate values | |
+| `zillow_get_saved_searches` | Your saved searches with new-listing counts | ✓ |
+| `zillow_get_saved_homes` | Your favorited homes | ✓ |
+| `zillow_get_market_report` | Median price, days on market, ZHVI for a region | |
+| `zillow_calculate_mortgage` | Local PITI calculator (no network) | |
+
+## 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-mcp
+cd zillow-mcp
+npm install
+npm 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 [fetchproxy](https://github.com/chrischall/fetchproxy) extension, which is shared across every fetchproxy-based MCP (resy-mcp, opentable-mcp, …). Install it once:
+
+```bash
+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
+
+```bash
+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)
+```
+
+## License
+
+MIT

package/SKILL.md

@@ -0,0 +1,76 @@
+---
+name: zillow-mcp
+description: Look up real-estate listings, property details, Zestimates, saved searches/homes, and market reports on Zillow via MCP. Triggers on phrases like "find homes in", "what's the Zestimate for", "show my saved Zillow homes", "what's my saved Zillow search seeing", "what does Zillow say about", "Zillow market report for", or any request involving Zillow properties, prices, or your saved Zillow activity. Requires zillow-mcp installed and the fetchproxy extension active (see Setup below).
+---
+
+# zillow-mcp
+
+MCP server for Zillow — natural-language access to listings, property records, Zestimates, your saved searches/homes, and market reports. Routes through your signed-in zillow.com tab via the fetchproxy browser extension, so Akamai sees a real browser session instead of a Node process.
+
+- **npm:** [npmjs.com/package/zillow-mcp](https://www.npmjs.com/package/zillow-mcp)
+- **Source:** [github.com/chrischall/zillow-mcp](https://github.com/chrischall/zillow-mcp)
+
+> ⚠️ Zillow does not publish a public consumer API. This server uses the same private endpoints the zillow.com web app calls, dispatched through your own signed-in browser tab via the fetchproxy extension. Use at your own discretion.
+
+## Setup
+
+### 1. Install zillow-mcp
+
+`.mcp.json` (project) or `~/.claude/mcp.json` (global):
+
+```json
+{
+  "mcpServers": {
+    "zillow": {
+      "command": "npx",
+      "args": ["-y", "zillow-mcp"]
+    }
+  }
+}
+```
+
+### 2. Install the fetchproxy extension (one-time, shared across all fetchproxy-based MCPs)
+
+```bash
+git clone https://github.com/chrischall/fetchproxy
+cd fetchproxy
+npm ci
+npm --workspace=@fetchproxy/extension-chrome run build
+```
+
+Then in Chrome: `chrome://extensions` → Developer mode → Load unpacked → pick `packages/extension-chrome/dist/`.
+
+### 3. Open zillow.com and sign in.
+
+That's it. No API keys, no env vars.
+
+## Tools
+
+### Public data
+
+- **`zillow_search_properties`** — Search by location + filters (price, beds, home type, status). Returns matching listings with price, Zestimate, beds/baths, sqft, image, and homedetails URL.
+- **`zillow_get_property`** — Full property record by `zpid` or homedetails URL. Returns address, price, Zestimate, rent Zestimate, beds, baths, sqft, year built, schools, price history.
+- **`zillow_get_zestimate_history`** — Time series of Zestimate values for a property.
+- **`zillow_get_market_report`** — Median sale/list/rent price, days on market, inventory, ZHVI for a Zillow region (e.g. `/home-values/6181/brooklyn-ny/`).
+- **`zillow_calculate_mortgage`** — Local PITI calculator. No network call. Provide home price, interest rate, optional down payment / taxes / insurance / HOA / PMI; returns a full monthly breakdown.
+
+### Signed-in user data (the unique value vs. Bridge-API competitors)
+
+- **`zillow_get_saved_searches`** — Your saved searches, with new-listing counts and notification frequency.
+- **`zillow_get_saved_homes`** — Homes you've favorited.
+
+## Trigger examples
+
+- "Find me 2-bedroom condos under $1.5M in Brooklyn" → `zillow_search_properties`
+- "What's the Zestimate on 123 Main St?" → resolve to zpid, then `zillow_get_property`
+- "How has the Zestimate for zpid 12345 changed?" → `zillow_get_zestimate_history`
+- "What's new on my saved Zillow searches?" → `zillow_get_saved_searches`
+- "Pull up my saved homes on Zillow" → `zillow_get_saved_homes`
+- "Brooklyn real-estate market trends" → `zillow_get_market_report`
+- "Monthly payment on a $500k home, 20% down, 6.5% rate" → `zillow_calculate_mortgage`
+
+## Gotchas
+
+- **Sign-in required for saved-* tools.** If the user isn't signed into zillow.com in the bridged Chrome tab, those tools fail with `SessionNotAuthenticatedError`. Public tools work either way, but signed-in sessions are more reliable against captcha walls.
+- **Captcha interstitial.** Zillow occasionally serves a captcha to fresh sessions. Solving it in the Chrome tab once unblocks subsequent fetches.
+- **No write surface yet.** All tools are read-only. Saving a home / search / contact form are not implemented in v0.1.