About redfin-mcp
redfin-mcp connects Claude and other MCP clients to Redfin real-estate data, including listings, property details, and market reports. It routes requests through a signed-in browser session using ContextMint Bridge, and also provides local mortgage and affordability calculators.
Key features
- 01Search listings by location and criteria
- 02View property details, photos, and history
- 03Get market data and climate risks
- 04Compare properties and fetch them in bulk
- 05Calculate mortgages and affordability
- 06View saved homes and searches
Use cases
- 01Filter listings by budget and home type
- 02Compare prices and attributes of properties
- 03Review local market trends and property risks
- 04Check favorited homes and saved searches
MCP support
As an MCP server, it exposes Redfin search, property, and market-data tools to clients. Network requests pass through the user's signed-in browser session via ContextMint Bridge.
Configuration
Local server config is the same for every client. Copy it into your client’s MCP config file.
npx -y redfin-mcpREDFIN_WS_PORTOverride the fetchproxy WebSocket port (default 37149).REDFIN_COMMUNITIES_FILEPath to a JSON file that overrides the community vocabulary (JSON string array).REDFIN_OUTPUT_DIRDirectory redfin_sweep_area writes its optional output_path JSON files into (default ~/Downloads/redfin-mcp); paths outside it are refused.REDFIN_DEBUGSet to 1 for verbose fetchproxy transport logging to stderr.FETCHPROXY_WS_HOSTBind interface for the fetchproxy concentrator, a literal IP only (default 127.0.0.1). Keep on loopback; it exists for hosted deployments that run each MCP in its own network namespace.FETCHPROXY_IDENTITY_DIRAbsolute path where the fetchproxy long-term identity keypair is stored (default ~/.fetchproxy/identity/).Local servers need a runtime on your machine (e.g. Node.js 18+). Config file locations differ by client; see your client’s docs.
Tools
22Saved tool list · updated 2w ago
| Parameter | Type | Required | Description |
|---|---|---|---|
| limit | integer | No | Max listings to return (default 40; values above 350, the gis hard cap, are clamped to 350). |
| bounds | object | No | Optional lat/lng box: search this drawn-map area instead of the resolved region (works inside big cities where ZIP/neighborhood regions fall back). `location` is then only a label. |
| bounds.east | number | Yes | |
| bounds.west | number | Yes | |
| bounds.north | number | Yes | |
| bounds.south | number | Yes | |
| status | enum | No | Listing status. Only for_sale is supported; sold and for_rent return an error rather than for-sale results.for_sale | for_rent | sold |
| beds_min | integer | No | |
| location | string | Yes | Free-text location: city, ZIP, neighborhood, or address (e.g. "Brooklyn, NY", "94110", "Park Slope") |
| baths_min | integer | No | |
| price_max | integer | No | |
| price_min | integer | No | |
| home_types | array | No | Restrict to one or more property types. |
Details
From the project READMEredfin-mcp
Redfin real-estate access as an MCP server for Claude — search listings, fetch property details, market reports, and your saved homes/searches via natural language.
⚠️ Redfin does not publish a public consumer API. This server uses the same private
/stingray/...endpoints the redfin.com web app uses, routed through your own signed-in browser tab via the ContextMint Bridge extension (driven by fetchproxy). 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 Redfin's website. Use at your own discretion.
Tools
| Tool | Purpose | Auth-scoped |
|---|---|---|
redfin_search_properties | Search listings by location, price band, beds/baths, home type. Resolves free-text via Redfin's autocomplete then queries the gis API. Optional bounds searches a drawn-map box instead. | |
redfin_sweep_area | Exhaustive enumeration of a lat/lng box: recursive polygon tiling until no tile hits the 350-home gis cap, deduped and filtered locally, with a completeness summary and drift warnings. zips mode sweeps a list of ZIP regions instead (for areas where Redfin ignores drawn-map polygons). Listings come back inline; the optional output_path writes them to a new .json file inside REDFIN_OUTPUT_DIR (default ~/Downloads/redfin-mcp; never overwrites) | |
redfin_get_property | Full record for a property by URL, property_id alone, or property_id+listing_id. Address, beds/baths, sqft, year built, price, status, days on market, primary photo. | |
redfin_get_property_photos | Full photo gallery for a property — every CDN image at fullscreen/large/medium sizes plus thumbnails and captions. | |
redfin_get_market_report | Median sale/list prices, ZHVI YoY, average days on market, inventory for a region. | |
redfin_get_price_history | Listing-history and tax-roll events for a property — Listed/Sold/Pending entries plus annual assessed values and taxes paid. | |
redfin_compare_properties | Side-by-side comparison of 2–25 properties: address, price, beds/baths, sqft, $/sqft, year built, status, days on market. Optional aligned summary table. | |
redfin_bulk_get | Structured fetch of up to 200 properties in one call — per-row errors, retry-once-on-timeout, and an overall deadline (unsettled rows come back pending). | |
redfin_get_climate_risk | First Street Foundation flood / fire / heat risk factors for a property — FEMA zones, 30-year flood-chance series, insurance bands, cumulative-heat projections. | |
redfin_get_climate_risk_bulk | Climate risk for up to 100 properties in one call, input order preserved, with a cluster_summary of properties that share scores. | |
redfin_get_area_climate_baseline | Averaged climate-risk baseline from 2–10 sample properties in an area, plus the shared cluster_id when they agree. | |
redfin_get_comparable_rentals | Comparable rentals near a property — monthly rent, beds/baths, sqft, distance. Used for rent estimation. | |
redfin_calculate_affordability | Local affordability calculator — back-of-envelope max purchase price from income + DTI + rates (no network). | |
redfin_get_saved_homes | Your favorited homes — flattened across all collections, with primary photo URLs constructed from each home's CDN handles. | ✓ |
redfin_get_saved_searches | Your saved searches with region URLs and display text. | ✓ |
redfin_calculate_mortgage | Local PITI calculator — principal+interest, taxes, insurance, HOA, PMI (no network). | |
redfin_get_by_address | Resolve a free-text address to its Redfin canonical URL + home_id. Degrades to resolved: false when no listing matches. Autocomplete, then suffix variants, then a bounded search fallback. | |
redfin_resolve_addresses | Batch-resolve up to 100 addresses to Redfin URLs + home_ids, one row per input. | |
redfin_healthcheck | End-to-end bridge check — round-trips /robots.txt and reports which hop failed (bridge down vs. extension not linked / pair code pending vs. Redfin-side issue), plus the extension link state (bridge.session_state, pending_pair_code, extension_connected). Call when other tools time out. | |
redfin_register_session / redfin_set_active_session / redfin_get_session_context | Shared session registry — record which Redfin account the bridged tab is signed into, switch between registered sessions, and show the active one (local; no network). |
Acknowledgement of Terms
By using this MCP server, you acknowledge and agree to the following:
1. This server accesses your own Redfin session. Every request is dispatched through your own browser tab via the ContextMint Bridge extension — your cookies, your TLS, your session. It does not — and cannot — access anyone else's account.
2. Redfin's Terms of Use govern your use of this server, just as they govern your direct use of redfin.com. The clauses most relevant here:
You may not automatedly crawl or query the Services for any purpose or by any means (including, without limitation, screen and database scraping, spiders, robots, crawlers and any other automated activity with the purpose of obtaining information from the Services) unless you have received prior express written permission from the applicable Redfin Company.
And: "You agree to keep your password confidential, not use others' accounts, nor permit others to use your account."
You are agreeing to those terms — read by the maintainer 2026-05-23 — every time you invoke a tool in this server. Redfin's terms prohibit automated crawling without written permission, and IDX listing data is licensed for personal, non-commercial use only.
3. Personal, non-commercial use only. This project is not affiliated with, endorsed by, sponsored by, or in partnership with Redfin Corporation. It is a personal automation tool that calls the same /stingray/... endpoints redfin.com calls when you click around. Do not use it to bulk-extract listings, redistribute IDX data, train AI models, populate a competing real-estate product, or for any commercial purpose.
4. Stability is not guaranteed. This server reads private internal endpoints (/stingray/api/gis, /stingray/api/home/details/*, /stingray/api/region/.../market-trends, /myredfin/*) that Redfin 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 Redfin access — rate limiting, account suspension, IP blocks, AWS WAF challenges, or any enforcement action Redfin takes. If Redfin 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 Redfin's actual ToU.
Install
Option A — npx (after first publish)
Add to .mcp.json:
{
"mcpServers": {
"redfin": {
"command": "npx",
"args": ["-y", "redfin-mcp"]
}
}
}
Option B — from source
git clone https://github.com/chrischall/redfin-mcp
cd redfin-mcp
npm install
npm run build
{
"mcpServers": {
"redfin": {
"command": "node",
"args": ["/path/to/redfin-mcp/dist/bundle.js"]
}
}
}
One-time browser setup
redfin-mcp talks to your browser through the ContextMint Bridge extension, which is shared across every fetchproxy-based MCP (zillow-mcp, opentable-mcp, resy-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 (fetchproxy#extension) points to it. Its source is public at nullnet-app/contextmint-bridge: build it yourself, or check a release zip against the .sha256 file published beside it (shasum -a 256 -c contextmint-bridge-chrome-<version>.zip.sha256).
Open redfin.com and sign in. That's all the auth this server needs.
How it works
┌────────────────┐ stdio ┌──────────────────┐ WS ┌──────────────────┐ fetch() ┌─────────────┐
│ MCP client │◀────────▶│ dist/bundle.js │◀──────▶│ ContextMint │◀────────────▶│ redfin.com │
│ (Claude, etc.) │ │ (Redfin MCP) │ :37149 │ Bridge │ (real TLS, │ (your tab) │
└────────────────┘ └──────────────────┘ │ (separate) │ cookies) └─────────────┘
The MCP server runs in Node, but every HTTP call to redfin.com is dispatched into your live browser tab through the ContextMint Bridge extension. Each request rides your existing session — TLS fingerprint, cookies, and JS execution context 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.
Redfin's /stingray/... JSON endpoints respond with a {}&& anti-CSRF prefix before the JSON body; the client strips it transparently.
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)
License
MIT
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.