Propstack MCP vs Zillow MCP
A side-by-side look at the Propstack MCP and Zillow MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Propstack MCP for real estate work as a local process; choose Zillow MCP for real estate as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Propstack MCP when
- You need dedicated capabilities in the Real Estate domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: API key required.
- You have the keys it needs:
PROPSTACK_API_KEY. - You want tools like
search_contacts, get_contact, create_contact.
Choose Zillow MCP when
- You need dedicated capabilities in the Real Estate domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: other.
- You want tools like
zillow_search_properties, zillow_sweep_area, zillow_get_property.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Real Estate | Real Estate |
| Quality signal | 65/100 · Great | 63/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | API key required | other |
| Pricing | BYOK (pay the provider) | Free |
| Required env vars | PROPSTACK_API_KEY | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 9 | 0 |
| Directory activity | 5 views 0 installs 0 upvotes | 1 views 0 installs 0 upvotes |
| Tools | 52 | 21 |
| Full listing | View Propstack MCP | View Zillow MCP |
Tools & capabilities
Propstack MCP tools 52
search_contactsSearch and filter contacts in Propstack CRM. Use this tool to: - Find contacts by name, email, or phone number - List recent leads (sort by created_at desc) - Find uncontacted leads (last_contact_at is null) - Filter by broker assignment, status, tags, or GDPR status - Search across all contact fields with 'q' parameter The 'q' parameter searches across: first name, last name, all emails, all addresses, and all phone numbers. Phone search ('phone_number') ignores formatting — both 015712345678 and 0157-123-456-78 will match. Returns paginated results. Use expand=true for full details including custom fields. Custom fields: pass 'custom_filters' as an object of custom-field-name → value to filter by agency-specific fields (use list_custom_fields to discover field names). Each entry becomes a cf_<name> query parameter, e.g. { marketing_channel: "Website" }. Data minimization (Art. 25 DSGVO): pass 'fields' with an array of contact field names to return only those fields per contact (e.g. ["first_name", "last_name", "email"]). Omit 'fields' to return the default set unchanged. Unknown field names produce an error listing the valid options.get_contactGet full details of a single contact by ID. Use this tool to: - View complete contact information before a call - Check relationships, documents, and owned properties - See sub-contacts (e.g. family members at same address) Use 'include' to load related data in one request.create_contactCreate a new contact in Propstack CRM. Use this tool to: - Register a new lead after a phone call - Create a contact from a web form submission - Add a new property owner Auto-upserts: if a contact with the same email or old_crm_id already exists, it will be updated instead of creating a duplicate. Use get_contact_sources first to find valid source IDs.update_contactUpdate an existing contact in Propstack CRM. Use this tool to: - Update contact details after a call - Change broker assignment - Add or remove tags (Merkmale) - Update GDPR status - Change contact rating or status Tag management options: - group_ids: replaces ALL tags with this list - add_group_ids: adds tags without removing existing ones - sub_group_ids: removes specific tags Only provide the fields you want to change.delete_contactDelete a contact from Propstack CRM (soft delete). The contact is moved to a 30-day recycle bin and can be restored. Use this tool for: - GDPR deletion requests (Art. 17 DSGVO) - Removing duplicate contacts - Cleaning up test dataget_contact_sourcesList all available contact/lead sources in Propstack. Returns the list of sources like "Immobilienscout 24", "Website", "Empfehlung", etc. with their IDs. Use this tool to look up valid source IDs before creating or updating contacts with client_source_id.search_contacts_by_phoneLook up a contact by phone number. This is the go-to tool for voice agent caller identification. When a call comes in, use this tool with the caller's phone number to instantly find the matching contact. Phone matching ignores formatting — all of these find the same contact: 015712345678, 0157-123-456-78, +49 157 12345678 Returns the matching contact(s) with key details. If no match is found, the caller is unknown and you should create a new contact.search_propertiesSearch and filter properties (Objekte) in Propstack CRM. Use this tool to: - Find properties by address, ID, or exposé ID (use 'q' for fulltext) - Filter by status, type, marketing type, or project - Find properties in a price/rent range - List properties by size, rooms, or construction year - Filter by custom fields via the 'custom_filters' object (see below) The 'q' parameter searches: unit_id, street, zip code, city, district, exposé ID. Range filter pattern: 11 numeric fields each have _from and _to variants. For example, price_from=200000 & price_to=400000 finds properties priced 200–400k. Available range fields: price, base_rent, total_rent, property_space_value, living_space, plot_area, number_of_rooms, number_of_bed_rooms, number_of_bath_rooms, floor, construction_year. Common queries: - "Apartments 300–400k in Berlin": q="Berlin", marketing_type=BUY, rs_type=APARTMENT, price_from=300000, price_to=400000 - "All available rentals": marketing_type=RENT, status=<available_id from get_property_statuses> - "Properties on market 90+ days": sort_by=created_at, order=asc - "What's in Project X?": project_id=<id> Custom fields: pass 'custom_filters' as an object of custom-field-name → value (use list_custom_fields to discover field names). Each entry becomes a cf_<name> query parameter, e.g. { energy_class: "A" }. Always returns total count. Use expand=true for custom fields. Data minimization (Art. 25 DSGVO): pass 'fields' with an array of property field names to return only those fields per property (e.g. ["id", "title", "price", "city"]). Omit 'fields' to return the default set unchanged. Unknown field names produce an error listing the valid options.get_propertyGet full details of a single property by ID. Use this tool to: - View complete property information for an exposé - Check images, floorplans, documents, and links - See custom fields, broker assignment, and project - Get multilingual texts (use locale parameter) Always fetches with new=1 (extra fields) and expand=1 (custom fields).create_propertyCreate a new property (Objekt) in Propstack CRM. Use this tool to: - List a new property from an acquisition call - Create a listing from an owner inquiry - Add a property to a project Use get_property_statuses to look up valid status IDs. Use the relationships_attributes array to link an owner contact on creation. rs_type values: APARTMENT, HOUSE, TRADE_SITE, GARAGE, SHORT_TERM_ACCOMODATION, OFFICE, GASTRONOMY, INDUSTRY, STORE, SPECIAL_PURPOSE, INVESTMENT. rs_category provides sub-types (e.g. PENTHOUSE, VILLA, MAISONETTE for APARTMENT/HOUSE).update_propertyUpdate an existing property in Propstack CRM. Use this tool to: - Update the price or rent - Change property status (e.g. mark as reserved or sold) - Edit description texts - Assign to a different broker or project - Update custom fields Only provide the fields you want to change. Use get_property_statuses to look up valid status IDs.get_property_statusesList all available property statuses in Propstack. Returns statuses like "Verfügbar", "Reserviert", "Verkauft" with their IDs, colors, and sort positions. Use this tool to look up valid status IDs before: - Filtering properties by status in search_properties - Setting a property's status in create_property or update_property- +40 more on the listing page
Zillow MCP tools 21
zillow_search_propertiesSearch Zillow listings by location (city, ZIP, neighborhood, or address) and optional filters (status, price band, beds/baths minimums, home types). Returns matching properties with price, beds/baths, sqft, Zestimate, status, image, and homedetails URL. Works with city/ZIP-level queries (filtered against your criteria) AND with full-address or street-only queries (returns the listings Zillow resolves to directly — filters are not applied in this single-round-trip path; use zillow_get_by_address for the cleanest one-shot address → zpid lookup). Throws LocationNotResolved if Zillow can't pin either a region or matching listings for the input (instead of silently falling back to your default search region). Heads up: Zillow renders ~40 listings per page server-side; this tool auto-paginates by default when `limit` exceeds that, walking subsequent pages and concatenating results (set `auto_paginate: false` to opt out and get the single-page response). For dense markets, price-band the search to enumerate fully. Does NOT return Zestimate history — use zillow_get_zestimate_history for that. Read-only; safe to call repeatedly.zillow_sweep_areaEnumerate EVERY Zillow listing matching the filters inside a location (resolved like zillow_search_properties) or an explicit bounding box, without silent truncation. Splits the area into map tiles and recursively quarters any tile whose Zillow-reported total exceeds what one query can return, dedupes by zpid and re-applies the numeric filters (drift guard). Returns a completeness summary (requests, tiles, unique listings, tiles still truncated at max depth, drift warnings such as Zillow ignoring the price filter or the viewport) plus the listings, or writes the listings to `output_path` as JSON for large areas (inside the output directory: ZILLOW_OUTPUT_DIR, default ~/Downloads/zillow-mcp). Sequential requests with a delay, paced by the same per-host requests-per-minute throttle as `zillow_bulk_get`; if Zillow's bot-wall blocks a request the sweep stops and returns `{ blocked: true, retry_after_s }` with what it had. Read-only against Zillow; the only write is the optional local output file.zillow_get_propertyFetch a property's full Zillow record by zpid (numeric Zillow Property ID, e.g. 12345) or by homedetails URL. Returns address (Zillow's slugged form), mls_street_address (canonical MLS form — prefer this when it disagrees), neighborhood, price, Zestimate, rent Zestimate, beds/baths, square footage, lot_size (sq ft) plus the derived lot_size_acres (round(lot_size / 43560, 2); both null — never 0 — for condos and listings with no lot), year built, schools, and an `extracted_features` block (lake_front, hot_tub, basement, furnished, dock, community) keyword-parsed from the description. Also returns `zest_vs_list_pct` — the list-vs-Zestimate spread, `(price − zestimate) / zestimate × 100` rounded to 1 decimal: POSITIVE means listed ABOVE the Zestimate, negative below (null when either input is missing). The raw `description` is omitted by default — pass `include_description: true` to keep it; in most cases the extracted features cover what callers need. Price-history and tax-history are also opt-in (`include_price_history: true` / `include_tax_history: true`) — bundle them in to skip a separate call. Provide exactly one of zpid or url. Read-only; safe to call repeatedly.zillow_get_zestimate_historyHistorical Zestimate values for a property by zpid or homedetails URL. Returns a time series of {date, value, rent?} entries (rent included when Zillow has a rent Zestimate for the property). Note: zillow_get_property returns only the *current* Zestimate as a scalar — call this tool when you need the trend. For some listings (commonly non-Showcase) Zillow renders the trend client-side and omits it from the server-rendered page; then `points` is empty and an explanatory `note` is returned — distinct from a genuine no-history. Read-only; safe to call repeatedly.zillow_get_saved_searchesThe signed-in user's saved searches on zillow.com (name, filters, new-listing count, notification frequency). Requires the user to be signed in at zillow.com in the bridged browser tab — throws SessionNotAuthenticatedError otherwise. An optional `session_id` (from `zillow_register_session`) is checked against the session registry — an unknown id errors — but it is a label only: the request always goes through whichever browser tab the extension is signed into. Read-only; safe to call repeatedly.zillow_get_saved_homesThe signed-in user's saved (favorited) homes on zillow.com, flattened across all of the user's collections. Returns address, price, Zestimate, status, and when each home was saved. An optional `session_id` (from `zillow_register_session`) is checked against the session registry — an unknown id errors — but it is a label only: the request always goes through whichever browser tab the extension is signed into. Requires the user to be signed in. Read-only; safe to call repeatedly.zillow_get_market_reportMarket report for a Zillow region: median sale/list prices, days on market, for-sale inventory, new listings, Zillow Home Value Index (ZHVI), and year-over-year ZHVI change. Provide either a `region_path` (e.g. "/home-values/6181/brooklyn-ny/") or a full Zillow home-values URL. Read-only; safe to call repeatedly.zillow_calculate_mortgageLocal-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 `down_payment` OR `down_payment_percent`; defaults to 20%. Property tax can be given as `property_tax_annual` or `property_tax_rate` (% of home price). PMI applies automatically when LTV > 80% and `pmi_rate` is provided.zillow_get_price_historyListing-price events for a property — listings, price changes, pending, sold, etc. — by zpid or homedetails URL. Returns two parallel arrays: `events` (raw Zillow shape with `event` strings and MLS attribution) and `events_normalized` (cross-MCP shared shape with a fixed `type` enum: Listed/PriceChange/Pending/Contingent/Sold/Withdrawn/Relisted/Delisted). The normalized form lets callers merge histories across real-estate MCPs without re-implementing taxonomy. Sourced from the same homedetails page as zillow_get_property. For some listings (commonly non-Showcase) Zillow omits the history from the server-rendered page; then `events` is empty and an explanatory `note` is returned — distinct from a genuine no-history.zillow_get_tax_historyYear-by-year property-tax record for a property: tax paid, assessed value, and the year-over-year change rates. Sourced from the homedetails page. Useful for spotting reassessment jumps or comparing tax burdens across properties. For some listings (commonly non-Showcase) Zillow omits the history from the server-rendered page; then `events` is empty and an explanatory `note` is returned — distinct from a genuine no-history.zillow_compare_propertiesSide-by-side analysis of 2-25 Zillow properties. **If you just want N property records, use `zillow_bulk_get` instead** — compare is for genuine side-by-side (its pivoted summary table is the value-add); bulk_get is the fetch-many endpoint and accepts up to 200 ids. (Issue #79 raised this cap from 8 to 25 — a 19-listing analysis now fits in one call instead of three.) Provide an array of zpids (or homedetails URLs). Returns the full per-property record per row (with `extracted_features` populated). Pass `include_summary: true` for an extra pivoted summary table (one row per field) — defaults off because `results[].property.*` already carries everything. The raw `description` is omitted from each row by default — pass `include_description: true` to keep it. Errors for individual properties are captured per-row — one bad zpid won't fail the whole call. Calls fan out concurrently (capped at 6 in flight, per issue #78, with retry-once-on-timeout per sub-request to absorb transient SW evictions), paced by the same throttle as `zillow_bulk_get`; a bot-wall block is retried with backoff and, if it persists, reported as `error_kind: "bot_challenge"` (distinct from a missing listing) with `{ blocked, retry_after_s }` on the envelope. The call is bounded by an overall deadline — unsettled rows come back as `error_kind: "pending"`.zillow_calculate_affordabilitySolve 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.- +9 more on the listing page
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Propstack MCP
{
"mcpServers": {
"ashev87-propstack-mcp": {
"command": "npx",
"args": [
"-y",
"propstack-mcp-server"
],
"env": {
"PROPSTACK_API_KEY": "YOUR_PROPSTACK_API_KEY_HERE"
}
}
}
}
Zillow MCP
{
"mcpServers": {
"zillow-mcp": {
"command": "npx",
"args": [
"-y",
"zillow-mcp"
]
}
}
}
Frequently asked questions
Propstack MCP is categorized under Real Estate and uses a local stdio subprocess. Zillow MCP belongs to Real Estate and uses a local stdio subprocess. Pick Propstack MCP for real estate work and Zillow MCP for real estate.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Propstack MCP is bring-your-own-key: usage is billed by the API provider you supply a key for. Auth: api key required. Zillow MCP is listed as free. Auth: other. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add ashev87-propstack-mcp and zillow-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Propstack MCP has a quality signal of 65/100 (Great) with 5 views, 0 installs and 9 GitHub stars. Zillow MCP has 63/100 (Good) with 1 views, 0 installs and 0 GitHub stars.