mcpField
M
mcp-zillow-listing-details

mcp-zillow-listing-details

Local
github.com/mambalabsdevBusiness & Marketing0Updated 1d ago

About mcp-zillow-listing-details

An MCP server that retrieves Zillow home details through an Apify actor. It accepts listing URLs, ZPIDs, street addresses, or ZIP codes and returns flat rows with listing facts and status.

Key features

  1. 01Look up homes by URL, ZPID, address, or ZIP
  2. 02Return price, Zestimate, facts, and status
  3. 03Read descriptions and listing agents
  4. 04Filter ZIP searches by listing status
  5. 05Limit results and set a charge cap

Use cases

  1. 01Review details for a specific Zillow home
  2. 02List homes for sale or rent in a ZIP code
  3. 03Check recently sold homes and prices

MCP support

Exposes the `read_zillow_listings` tool to MCP clients. It starts the Apify actor, waits for completion, and returns its dataset rows.

Configuration

Local server config is the same for every client. Copy it into your client’s MCP config file.

mcp.json · Universal config
{
"mcpServers": {
"com-mambabuilt-mcp-zillow-listing-details": {
"command": "npx",
"args": [
"-y",
"@mambalabsdev/mcp-zillow-listing-details"
],
"env": {
"APIFY_TOKEN": "<APIFY_TOKEN>"
}
}
}
}
Run commandnpx -y @mambalabsdev/mcp-zillow-listing-details
Environment variables to set
APIFY_TOKENSecretApify API token from https://console.apify.com/account/integrations

Local servers need a runtime on your machine (e.g. Node.js 18+). Config file locations differ by client; see your client’s docs.

Packages
npm@mambalabsdev/mcp-zillow-listing-details1.0.2

Tools

1

Saved tool list · updated 1d ago

ParameterTypeRequiredDescription
listingsarrayNoZillow home URLs, ZPIDs, or street addresses, up to 1,000 per run. An address must include a street number and a city or ZIP code, and it must match the home Zillow returns, or you get a free row.
zip_codesarrayNo5 digit US ZIP codes. Each returns the homes on Zillow's search pages for that ZIP code, up to Maximum listings.
max_listingsnumberNoThe most homes to return in this run, across every input in order, from 1 to 1,000. Default 100. Text or a number.
read_detailsbooleanNofalse (default) or true. With false, a ZIP code returns one search row per home at the search row price. With true, the actor reads each home's page at the listing row price, which adds the description and the listing agent.
listing_statusenumNofor_sale (default), for_rent, or recently_sold. Used only with ZIP codes.for_sale | for_rent | recently_sold
max_charge_usdstringNoOptional. The run stops before a charge that would pass this amount. Summary rows are always returned.

Details

From the project README

Zillow Listing Details MCP Server

npm version license

An MCP server for the Mamba Labs Zillow Listing Details actor on Apify. Read Zillow home details by URL, ZPID, address, or ZIP code.

What's Inside

What it does

Give Zillow home URLs, ZPIDs, street addresses, or ZIP codes. You get one flat row per home with price, Zestimate, facts, and status, plus description and the listing agent shown on MLS listings when the home page is read.

All of the work runs on Apify. This package is a thin client that starts the actor run, waits for it, and hands back the dataset rows.

Quick start

You need Node.js 18 or newer and an Apify account with an API token.

Add this to your Claude Desktop config (claude_desktop_config.json), Cursor, or any MCP client:

{
  "mcpServers": {
    "mamba-zillow-listing-details": {
      "command": "npx",
      "args": [
        "-y",
        "@mambalabsdev/mcp-zillow-listing-details"
      ],
      "env": {
        "APIFY_TOKEN": "your-apify-token"
      }
    }
  }
}

Restart the client. The read_zillow_listings tool appears.

Prerequisites

Example prompts

  • "What are the price, Zestimate, and listing agent of this Zillow home?"
  • "List the homes for sale in ZIP code 78701 with their facts."
  • "Which homes recently sold in 60614, and at what price?"

Tool

read_zillow_listings. One tool. Example arguments:

{
  "listings": [
    "97531684"
  ]
}

Inputs

Every buyer facing input of the actor. Omitted inputs take the actor's own defaults.

InputTypeRequiredDescription
listingsarraynoZillow home URLs, ZPIDs, or street addresses, up to 1,000 per run. An address must include a street number and a city or ZIP code, and it must match the home Zillow returns, or you get a free row.
zip_codesarrayno5 digit US ZIP codes. Each returns the homes on Zillow's search pages for that ZIP code, up to Maximum listings.
listing_statusstringnofor_sale (default), for_rent, or recently_sold. Used only with ZIP codes.
read_detailsbooleannofalse (default) or true. With false, a ZIP code returns one search row per home at the search row price. With true, the actor reads each home's page at the listing row price, which adds the description and the listing agent.
max_listingsnumbernoThe most homes to return in this run, across every input in order, from 1 to 1,000. Default 100. Text or a number.
max_charge_usdstringnoOptional. The run stops before a charge that would pass this amount. Summary rows are always returned.

Pricing

Pay per event on Apify, billed to your Apify account. Prices in USD.

EventFree planBronzeSilverGold
listing-row, one home page read$0.006$0.0057$0.0054$0.0051
search-row, one home from a ZIP code search$0.002$0.0019$0.0018$0.0017
apify-actor-start, per run start$0.007$0.007$0.007$0.007

Blocked homes, missing homes, unreadable pages, and refused input are free. Mamba Labs pays the platform costs of the run, Apify proxy traffic included.

Full actor documentation

apify.com/mambalabs/zillow-listing-details

License

MIT. See LICENSE.

Comments

Markdown supported

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.