redfin-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| redfin_search_propertiesA | Search Redfin listings by location (city, ZIP, neighborhood, or full street address) and optional filters. Resolves the location via Redfin's autocomplete then queries the gis API; full street addresses short-circuit to the single matched home (no gis call). Returns matching properties with price, beds/baths, sqft, year built, address, and the Redfin home URL. |
| redfin_sweep_areaA | Enumerate EVERY for-sale Redfin listing inside a bounding box without silent truncation. Redfin's gis API returns at most 350 homes per call and ignores server-side filters, so this tool searches drawn-map polygons, recursively quarters any tile that hits the cap, dedupes by property_id and re-applies the caller's filters locally. Homes outside the box and tiles where Redfin drifted to another region are left out. Alternatively pass |
| redfin_get_propertyA | Fetch a property's full Redfin record. Provide one of: (a) |
| redfin_get_saved_homesA | The signed-in user's favorited homes on redfin.com. Returns |
| redfin_get_saved_searchesA | The signed-in user's saved searches on redfin.com, derived from the saved-searches page HTML. Returns |
| redfin_get_market_reportA | Market report for a Redfin region: median list/sold prices, $/sqft, sale-to-list ratio, total homes for sale + sold, all with year-over-year and month-over-month change. Provide either (a) |
| redfin_calculate_mortgageA | Local-only mortgage payment calculator. Returns a full PITI breakdown (principal + interest, property tax, insurance, HOA, PMI) and total interest over the life of the loan. No network call — fully deterministic, safe to use for scenario comparison without burning a fetch. Provide either |
| redfin_get_price_historyA | Listing-price events for a property — listings, price changes, pending, sold, etc. Each entry has a date, event description, price, days-on-market at that point, and the data-source attribution (MLS, county records, etc.). Also returns the tax-history series from public records. Provide either |
| redfin_compare_propertiesA | Fetch and compare 2 to 25 Redfin properties side-by-side. Provide an array of targets, each either a |
| redfin_get_climate_riskA | First Street Foundation climate risk scores for a property. COVERS: flood (factor 1–10, FEMA zones, 30-year annual chance series), fire (factor 1–10, relative risk, insurance price band, provider count), heat (factor 1–10, cumulative-risk projections at 0/5/10/15/20-year horizons). DOES NOT COVER: landslide. This is the Helene-relevant risk vector in the NC mountains market and many parts of California / the Pacific Northwest. First Street has no landslide product — for that vector check the NC Geological Survey landslide hazard maps (NC-specific) or USGS landslide hazard data (national). Surfaced on every response as |
| redfin_get_climate_risk_bulkA | Fetch climate risk for up to 100 property URLs in a single call. Same per-property shape as |
| redfin_get_area_climate_baselineA | Fetch climate risk for a small set of representative URLs in an area, then return their averaged baseline values plus the shared cluster_id when present. Use this as a cheap area-level read BEFORE fanning out a per-property call: if all sample properties agree (same cluster_id, same fire/flood/heat factors), the baseline applies to the whole cluster and N redundant fetches are avoidable. Pass 2–10 URLs you believe represent the area; returns the aggregate plus the per-URL responses for transparency. Server-side concurrency (~5 fetches in flight) with retry-once-on-timeout per URL; the whole call is bounded by an overall deadline, and any sample still unsettled then comes back as |
| redfin_get_comparable_rentalsA | Find nearby rental comparables for a given property: nearby active rental listings with similar bed/bath/sqft, including monthly rent, distance, and the Redfin URL. Useful for estimating what a property could rent for, or for finding rentals near a home you're considering. Inputs are the rent estimate range + lat/lng + propertyId. |
| redfin_calculate_affordabilityA | Solve for the maximum home price you can afford under the standard 28/36 DTI rule. Inputs: monthly income, recurring monthly debts (car loans, student loans, etc.), down payment, interest rate, and optional property-tax rate / insurance / HOA / loan term. Output: max home price, the binding constraint (front-end vs back-end), and the full PITI breakdown at that price. Same math across the realty MCP cohort (@chrischall/realty-core). No network — pure local math. |
| redfin_get_property_photosA | The full photo gallery for a Redfin property — every image in mediaBrowserInfo. Each entry returns CDN URLs at multiple sizes (fullscreen, large, medium, lightbox) plus a thumbnail and the photo's caption when set. Provide either |
| redfin_get_by_addressA | Resolve a free-text address (with optional city/state/zip) to its Redfin canonical home URL and home_id. Walks a 3-rung ladder: (1) autocomplete as-typed, (2) autocomplete with suffix expansion (Rd ↔ Road, Ln ↔ Lane, etc.), (3) search fallback (#75) — when autocomplete misses entirely and city/state are provided, resolves the locality to a region, fires a bounded gis search, and fuzzy-matches the input street tokens against returned homes. |
| redfin_healthcheckA | Round-trips a small public www.redfin.com URL (/robots.txt) through ContextMint Bridge (your signed-in browser tab) and returns diagnostics: the bridge's role (host/peer/null), port, version, the extension link (linked / pair pending / not attached / never answered), the elapsed round-trip time, and a plain-English hint distinguishing 'bridge never came up' from 'extension not connected' from 'this browser can't serve a capability' from 'real www.redfin.com-side problem'. Read-only, no auth required. Call this when a real tool fails and you want to know which hop broke. |
| redfin_bulk_getA | Fetch up to 200 Redfin property records in a single tool call. Provide an array of targets, each one of: a |
| redfin_resolve_addressesA | Resolve up to 100 free-text street addresses to Redfin canonical home URLs + home_ids in a single tool call. Each input is either a string (full address) or a structured |
| redfin_register_sessionA | Record (or refresh) which Redfin account the signed-in session belongs to, keyed by |
| redfin_set_active_sessionA | Mark a previously registered |
| redfin_get_session_contextA | List every registered account label plus the current |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 22 tools
Several tools overlap in purpose: redfin_get_property, redfin_bulk_get, and redfin_compare_properties all fetch property records; redfin_get_by_address and redfin_resolve_addresses both resolve addresses; and climate risk is split across single, bulk, and area-baseline tools. Descriptions clarify batch/limit differences, but an agent must read carefully to pick correctly. Session label tools are distinct but add conceptual noise.
All tools use a consistent redfin_ prefix and snake_case, with most following a verb_noun pattern (get_property, calculate_mortgage, search_properties). Minor deviations exist: redfin_bulk_get reverses the order and redfin_healthcheck lacks a clear verb, but the set remains highly readable.
22 tools is on the heavy side for a single-domain client, and several batch variants plus session-label tools may not each earn an independent place. The count is borderline but still within a plausible range given the breadth of Redfin features covered.
The surface covers core property retrieval, search, market reports, climate risk, mortgage/affordability calculators, saved homes/searches, and session diagnostics. Gaps are minor: no official sold-listing search and no transactional write operations, but workarounds exist and the domain is largely addressed.