Homesage.ai vs Realestateapi
A side-by-side look at the Homesage.ai and Realestateapi MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Homesage.ai for real estate work; choose Realestateapi 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 Homesage.ai when
- You need dedicated capabilities in the Real Estate domain.
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.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Real Estate | Real Estate |
| Quality signal | 44/100 · Fair | 53/100 · Good |
| Install command | Not confirmed yet | Confirmed |
| Transport | — | Local subprocess (stdio) |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | None listed | None listed |
| Verified owner |
Tools & capabilities
Homesage.ai tools
No tool names declared yet. Check the project README from the listing page.
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: "yo…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" })
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.
Homesage.ai
No confirmed install command for Homesage.ai yet — follow the setup steps linked from its listing page rather than a guessed package name.
Realestateapi
{
"mcpServers": {
"realestateapi": {
"command": "npx",
"args": [
"-y",
"@pipeworx/mcp-realestateapi"
]
}
}
}
Frequently asked questions
Homesage.ai is categorized under Real Estate and uses an install path we have not confirmed yet. Realestateapi belongs to Real Estate and uses a local stdio subprocess. Pick Homesage.ai for real estate work and Realestateapi 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. Homesage.ai has no confirmed install command yet — follow its own setup instructions.
Homesage.ai has no declared pricing — check the project's own site. Realestateapi 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 homesage-ai and realestateapi as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Homesage.ai has a quality signal of 44/100 (Fair) with 3 views, 0 installs and 0 GitHub stars. Realestateapi has 53/100 (Good) with 0 views, 0 installs and 0 GitHub stars.