Realestateapi vs HasData Zillow
A side-by-side look at the Realestateapi and HasData Zillow MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Realestateapi for real estate work as a local process; choose HasData Zillow 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 Realestateapi when
- You need dedicated capabilities in the Real Estate domain.
- You prefer a local stdio subprocess transport.
- You want tools like
realestateapi_property_search, realestateapi_property_detail, realestateapi_skip_trace.
Choose HasData Zillow when
- You need dedicated capabilities in the Real Estate domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
HASDATA_API_KEY. - You want tools like
hasdata_zillow_listing_getRealEstateListings, hasdata_zillow_property_getPropertyDetails.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Real Estate | Real Estate |
| Quality signal | 59/100 · Good | 63/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | None listed | HASDATA_API_KEY |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 11 |
| Directory activity | 1 views 0 installs 0 upvotes | 1 views 0 installs 0 upvotes |
| Tools | 3 | 2 |
| Full listing | View Realestateapi | View HasData Zillow |
Tools & capabilities
Realestateapi tools 3
realestateapi_property_searchSearch properties by city/state/filters (off-market, absentee-owner, value range) — returns matching properties with address, owner, beds/baths, and estimated value. Example: realestateapi_property_search({ city: "Austin", state: "TX", absentee_owner: true, value_max: 400000, size: 25, _apiKey: "your-key" })realestateapi_property_detailGet full property detail by id or address — returns owner, estimated value, last sale, characteristics (beds/baths/sqft/year/lot), and mortgage. Example: realestateapi_property_detail({ address: "123 Main St, Austin, TX 78701", _apiKey: "your-key" })realestateapi_skip_traceSkip-trace owner contact info for an address — returns the owner name plus phone numbers and emails. Regulated PII: pure passthrough, nothing is stored. Example: realestateapi_skip_trace({ address: "123 Main St, Austin, TX 78701", _apiKey: "your-key" })
HasData Zillow tools 2
hasdata_zillow_listing_getRealEstateListingsGet Zillow Real Estate Listings Searches Zillow for-sale, for-rent, and sold listings by keyword with rich filters (price, beds, baths, home type, year built, lot/square footage, HOA, listing status, amenities, views, pet policy, days on Zillow) and pagination. Returns each listing with address, Zillow URL/zpid, price, Zestimate, beds/baths, sqft, home type, status, days on Zillow, coordinates, thumbnail, and listing broker. Use for real-estate market dashboards, rental pricing analysis, agent lead lists, inventory tracking, and collecting URLs for the Zillow Property endpoint.hasdata_zillow_property_getPropertyDetailsGet Zillow Property Details Fetches the full Zillow property page by URL/zpid, with optional agent email extraction. Returns address, list price, Zestimate and Rent Zestimate, price and tax history, beds/baths, living area, lot size, year built, home type, HOA, days on Zillow, listing description, features/amenities, photos, school assignments, walk/transit scores (building pages only), and listing agent/broker (plus email when enabled). Use for valuation models, CMA generation, investor underwriting, rental yield analysis, and enriching buyer/seller agent assistants with authoritative property data.
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.
Realestateapi
{
"mcpServers": {
"realestateapi": {
"command": "npx",
"args": [
"-y",
"@pipeworx/mcp-realestateapi"
]
}
}
}
HasData Zillow
{
"mcpServers": {
"hasdata-zillow": {
"command": "npx",
"args": [
"-y",
"@hasdata/zillow-mcp"
],
"env": {
"HASDATA_API_KEY": "YOUR_HASDATA_API_KEY_HERE"
}
}
}
}
Frequently asked questions
Realestateapi is categorized under Real Estate and uses a local stdio subprocess. HasData Zillow belongs to Real Estate and uses a local stdio subprocess. Pick Realestateapi for real estate work and HasData Zillow 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.
Realestateapi has no declared pricing — check the project's own site. HasData Zillow 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 realestateapi and hasdata-zillow as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Realestateapi has a quality signal of 59/100 (Good) with 1 views, 0 installs and 0 GitHub stars. HasData Zillow has 63/100 (Good) with 1 views, 0 installs and 11 GitHub stars.