Homesage.ai vs Xome
A side-by-side look at the Homesage.ai and Xome 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 Xome 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 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.
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 | Community listing | Community listing |
Tools & capabilities
Homesage.ai tools
No tool names declared yet. Check the project README from the listing page.
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.
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.
Xome
{
"mcpServers": {
"xome": {
"command": "npx",
"args": [
"-y",
"@pipeworx/mcp-xome"
]
}
}
}
Frequently asked questions
Homesage.ai is categorized under Real Estate and uses an install path we have not confirmed yet. Xome belongs to Real Estate and uses a local stdio subprocess. Pick Homesage.ai for real estate work and Xome 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. Xome 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 xome 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. Xome has 53/100 (Good) with 0 views, 0 installs and 1 GitHub stars.