Homesage.ai vs Propraven
A side-by-side look at the Homesage.ai and Propraven 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 Propraven 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 Propraven when
- You need dedicated capabilities in the Real Estate domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
PROPRAVEN_API_KEY. - You want tools like
parcel_lookup, parcel_search, parcel_compare.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Real Estate | Real Estate |
| Quality signal | 44/100 · Fair | 52/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 | PROPRAVEN_API_KEY |
| Verified owner |
Tools & capabilities
Homesage.ai tools
No tool names declared yet. Check the project README from the listing page.
Propraven tools 8
parcel_lookupResolve one parcel by ID, address, or APNparcel_searchText search by owner, address fragment, APN or city (+ state/city filters, keyset `cursor`)parcel_compareFree card (+ hazards) for 2–25 parcels, for agent-side rankingowner_pierceParcels titled under an owner name (optional `state` filter, best-effort `ticker`)hazard_scoreFlood / wildfire / seismic / windstorm / air-quality / crime blocksvaluation_estimateMarket value, AVM, assessed values, last sale, $/sqftpermits_historyPermit timeline (≤100 newest, with true-count basis)sales_historyDeed / transfer timeline
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.
Propraven
{
"mcpServers": {
"propraven": {
"command": "npx",
"args": [
"-y",
"@propraven/mcp"
],
"env": {
"PROPRAVEN_API_KEY": "YOUR_PROPRAVEN_API_KEY_HERE"
}
}
}
}
Frequently asked questions
Homesage.ai is categorized under Real Estate and uses an install path we have not confirmed yet. Propraven belongs to Real Estate and uses a local stdio subprocess. Pick Homesage.ai for real estate work and Propraven 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. Propraven 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 propraven 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. Propraven has 52/100 (Good) with 0 views, 0 installs and 0 GitHub stars.