Zillow Property Info Scraper
Under maintenance
Pricing
$0.10 / 1,000 outputs
Zillow Property Info Scraper
Under maintenance
This actor takes multiple property addresses (one per line) and fetches detailed information for each using Zillow’s internal APIs. Whether you’re analyzing comps, scouting investment properties, or automating real estate workflows, this tool is designed to save you hours of manual research.
5.0 (2)
Pricing
$0.10 / 1,000 outputs
1
Total users
3
Monthly users
3
Runs succeeded
>99%
Last modified
3 days ago
You can access the Zillow Property Info Scraper programmatically from your own applications by using the Apify API. You can also choose the language preference from below. To use the Apify API, you’ll need an Apify account and your API token, found in Integrations settings in Apify Console.
{ "mcpServers": { "apify": { "command": "npx", "args": [ "mcp-remote", "https://mcp.apify.com/sse?actors=aknahin/zillow-property-info-scraper", "--header", "Authorization: Bearer <YOUR_API_TOKEN>" ] } }}Configure MCP server with Bulk Zillow Scraper: Get Zestimate & Home Details
You have a few options for interacting with the MCP server:
Use
mcp.apify.comviamcp-remotefrom your local machine to connect and authenticate using OAuth or an API token (as shown in the JSON configuration above).Set up the connection directly in your MCP client UI by providing the URL
https://mcp.apify.com/sse?actors=aknahin/zillow-property-info-scraperalong with an API token (or use OAuth).Connect to
mcp.apify.comvia Server-Sent Events (SSE), as shown below:
{ "mcpServers": { "apify": { "type": "sse", "url": "https://mcp.apify.com/sse?actors=aknahin/zillow-property-info-scraper", "headers": { "Authorization": "Bearer <YOUR_API_TOKEN>" } } }}You can connect to the Apify MCP Server using clients like Tester MCP Client, or any other MCP client of your choice.
If you want to learn more about our Apify MCP implementation, check out our MCP documentation. To learn more about the Model Context Protocol in general, refer to the official MCP documentation or read our blog post.
