Stream Estate vs HouseData — Zillow data
A side-by-side look at the Stream Estate and HouseData — Zillow data MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
S
Stream EstateReal Estate · Remote HTTP/SSEFrench real estate listings, market data and property alerts (Stream Estate API v2).37FairAuth: not declaredH
HouseData — Zillow dataReal EstateZillow data for agents: listings, records, Zestimate history, market stats. 19 tools, pay per call.38FairAuth: not declaredVerdict: choose Stream Estate for real estate work over a hosted endpoint; choose HouseData — Zillow data for real estate. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
SChoose Stream Estate when
- You need dedicated capabilities in the Real Estate domain.
- You prefer a remote HTTP/SSE transport.
HChoose HouseData — Zillow data when
- You need dedicated capabilities in the Real Estate domain.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | S Stream Estate | H HouseData — Zillow data |
|---|---|---|
| Category | Real Estate | Real Estate |
| Quality signal | 37/100 · Fair | 38/100 · Fair |
| Install command | Confirmed | Not confirmed yet |
| Transport | Remote HTTP/SSE | — |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Paid service |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | — | — |
| Directory activity | 0 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View Stream Estate | View HouseData — Zillow data |
Tools & capabilities
Stream Estate tools
No tool names declared yet. Check the project README from the listing page.
HouseData — Zillow data 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.
Stream Estate
{
"mcpServers": {
"stream-estate-3": {
"url": "https://next.docs.stream.estate/en/docs/guides/mcp"
}
}
}
HouseData — Zillow data
No confirmed install command for HouseData — Zillow data yet — follow the setup steps linked from its listing page rather than a guessed package name.
Frequently asked questions
Stream Estate is categorized under Real Estate and uses a remote HTTP/SSE transport. HouseData — Zillow data belongs to Real Estate and uses an install path we have not confirmed yet. Pick Stream Estate for real estate work and HouseData — Zillow data 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. HouseData — Zillow data has no confirmed install command yet — follow its own setup instructions.
Stream Estate has no declared pricing — check the project's own site. HouseData — Zillow data is listed as a paid service. 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 stream-estate-3 and housedata-zillow-data as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Stream Estate has a quality signal of 37/100 (Fair) with 0 views, 0 installs and 0 GitHub stars. HouseData — Zillow data has 38/100 (Fair) with 0 views, 0 installs and 0 GitHub stars.