Xome vs Zillow Property Data (APIllow)
A side-by-side look at the Xome and Zillow Property Data (APIllow) MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Z
Zillow Property Data (APIllow)Real EstateZillow property data for AI agents: search listings and get 50+ fields for any US property.37FairAuth: not declaredVerdict: choose Xome for real estate work as a local process; choose Zillow Property Data (APIllow) for real estate. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Xome when
- You need dedicated capabilities in the Real Estate domain.
- You prefer a local stdio subprocess transport.
- You want tools like
xome_search, xome_property_detail.
ZChoose Zillow Property Data (APIllow) when
- You need dedicated capabilities in the Real Estate domain.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | Z Zillow Property Data (APIllow) | |
|---|---|---|
| Category | Real Estate | Real Estate |
| Quality signal | 53/100 · Good | 37/100 · Fair |
| Install command | Confirmed | Not confirmed yet |
| Transport | Local subprocess (stdio) | — |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 1 | — |
| Directory activity | 0 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | 2 | Not listed |
| Full listing | View Xome | View Zillow Property Data (APIllow) |
Tools & capabilities
Xome tools 2
xome_searchBrowse listings by state (+ optional county): property facts (beds/baths/sqft/year built/lot size/occupancy), sale type, `auction_status`/`bid_deadline`. Not the bid/sale price — see `xome_property_detail`.xome_property_detailFull detail for one listing: property facts, the exact sale event (date + courthouse venue address), sale terms, and the bid/sale **price** with an explicit status label.
Zillow Property Data (APIllow) tools
No tool names declared yet. Check the project README from 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.
Xome
{
"mcpServers": {
"xome": {
"command": "npx",
"args": [
"-y",
"@pipeworx/mcp-xome"
]
}
}
}
Zillow Property Data (APIllow)
No confirmed install command for Zillow Property Data (APIllow) yet — follow the setup steps linked from its listing page rather than a guessed package name.
Frequently asked questions
Xome is categorized under Real Estate and uses a local stdio subprocess. Zillow Property Data (APIllow) belongs to Real Estate and uses an install path we have not confirmed yet. Pick Xome for real estate work and Zillow Property Data (APIllow) 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. Zillow Property Data (APIllow) has no confirmed install command yet — follow its own setup instructions.
Xome has no declared pricing — check the project's own site. Zillow Property Data (APIllow) has no declared pricing — check the project's own site. 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 xome and zillow-property-data-apillow as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Xome has a quality signal of 53/100 (Good) with 0 views, 0 installs and 1 GitHub stars. Zillow Property Data (APIllow) has 37/100 (Fair) with 0 views, 0 installs and 0 GitHub stars.