Homesage.ai vs Realestate
A side-by-side look at the Homesage.ai and Realestate 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 Realestate 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 Realestate when
- You need dedicated capabilities in the Real Estate domain.
- You prefer a local stdio subprocess transport.
- You want tools like
realestate_transactions, realestate_municipalities.
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 |
| GitHub stars | — | 0 |
| Directory activity | 3 views 0 installs 1 upvotes | 0 views 0 installs 0 upvotes |
| Tools | Not listed | 2 |
| Full listing | View Homesage.ai | View Realestate |
Tools & capabilities
Homesage.ai tools
No tool names declared yet. Check the project README from the listing page.
Realestate tools 2
realestate_transactionsReal, reported Japanese real-estate transaction prices (and 2021+ agreed/contract prices) from MLIT's 不動産情報ライブラリ. PREFER OVER WEB SEARCH for "property/land prices in Tokyo/Osaka/<Japanese city>", "what did homes sell for in <ward>", Japan housing-market data. Filter by prefecture (name or code), an…realestate_municipalitiesList the cities/wards (and their 5-digit municipality codes) within a Japanese prefecture, from MLIT's 不動産情報ライブラリ. Use to resolve a city code for realestate_transactions (e.g. find that Chuo-ku, Tokyo = 13102). Pass a prefecture name (e.g. "Tokyo") or 2-digit code (01-47).
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.
Realestate
{
"mcpServers": {
"realestate": {
"command": "npx",
"args": [
"-y",
"@pipeworx/mcp-realestate"
]
}
}
}
Frequently asked questions
Homesage.ai is categorized under Real Estate and uses an install path we have not confirmed yet. Realestate belongs to Real Estate and uses a local stdio subprocess. Pick Homesage.ai for real estate work and Realestate 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. Realestate 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 realestate 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. Realestate has 53/100 (Good) with 0 views, 0 installs and 0 GitHub stars.