A side-by-side look at the Zillow API and Zillow Leads Property Data MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Zillow API for real estate work over a hosted endpoint; choose Zillow Leads Property Data for real estate over a hosted endpoint. You can also run both side by side in one mcpServers block.
APIFY_API_TOKEN.Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Real Estate | Real Estate |
| Quality signal | 40/100 · Fair | 37/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Remote HTTP/SSE | Remote HTTP/SSE |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | APIFY_API_TOKEN | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 0 |
| Directory activity | 0 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View Zillow API | View Zillow Leads Property Data |
No tool names declared yet. Check the project README from the listing page.
No tool names declared yet. Check the project README from the listing page.
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.
{
"mcpServers": {
"zillow-api": {
"url": "https://mcp.apify.com/?tools=actors,docs,johnvc/zillow-api"
}
}
}
{
"mcpServers": {
"zillow-leads-property-data": {
"url": "https://mcp.apify.com"
}
}
}