Codealive MCP vs Homes MCP — MCP Server Comparison | AllMCPs
Side-by-Side Model Context Protocol Comparison
Codealive MCP vs Homes MCP
In-depth architectural comparison of the Codealive MCP and Homes MCP MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.
At a Glance & Executive Verdict
Codealive MCP
Developer Tools · Local stdio
Quality: 48/100 (Fair) | Auth: No auth required
Homes MCP
Developer Tools · Local stdio
Quality: 56/100 (Good) | Auth: No auth required
Verdict Summary: Choose Codealive MCP if you need specialized Developer Tools tools running via a local process. Choose Homes MCP if your workspace requires Developer Tools integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.
Which MCP Server Should You Choose?
Choose Codealive MCP when:
You need dedicated capabilities in the Developer Tools domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
No explicit tool names declared in metadata yet. Check project README on main listing page.
Homes MCP Tools (19)
homes_search_properties
Search listings by free-text location (city/ZIP/neighborhood). Slugifies the input into homes.com's URL routing and parses the JSON-LD `CollectionPage.mainEntity.itemListElement[]`. Filters by `property_type`, `listing_type`, `sort`, and a `price_min`/`price_max` band. Returns address, price, beds/…
homes_get_by_address
Resolve one US street address to its canonical homes.com property URL + opaque hash. Walks structured typeahead → slug → city/zip search-fallback with whole-token street + unit verification. Returns `matched_via`; degrades to `{ resolved: false }`.
homes_resolve_addresses
Bulk `homes_get_by_address` (up to 100 addresses, input order preserved, per-row outcomes). Prefer for batches ≥ 3.
homes_get_property
Ready-to-Paste Client Configurations
Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).
Codealive MCP is categorized under Developer Tools and uses a local stdio subprocess. In contrast, Homes MCP belongs to Developer Tools using local stdio subprocess. Select Codealive MCP when you need capabilities focused on developer tools and Homes MCP when you require tools for developer tools.
Full record for a property by URL. Parses JSON-LD + DOM-side sections: address, lat/lng, beds/baths, sqft, year built, price, status, agent + brokerage, highlights, schools, HOA (raw + monthly), lot size (sqft + acres), parking, heating/cooling, MLS id/source, tax, days-on-market, price drops, `ext…
homes_get_property_photos
Full photo gallery scraped from `<img>` tags on the detail page (JSON-LD only carries one image). Returns `{ url, position, alt? }` per photo, filtered to the homes.com CDN.
homes_bulk_get
Fetch up to 200 properties' structured records in one call (per-row errors, input order preserved).
homes_compare_properties
Side-by-side comparison of 2–8 properties with an aligned summary table. Per-target errors captured per-row. Concurrent fetches.
homes_get_nearby_listings
The "Homes for Sale Near This Property" cross-link cards from a detail page (For Sale, optionally Rentals). URL + address only.
homes_get_history
Combined price + tax history in one fetch: `listing_events`, `ownership_events`, `lien_events`, normalized `events_normalized`, and `tax_records`.