Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type @ followed by the MCP server name and your instructions, e.g., "@RentCast MCP Server search for 3-bedroom homes for sale under $500k in Austin, TX"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
MCP server that wraps the RentCast API to help search for houses for sale, get property valuations, rent estimates, and market statistics.
# Install dependencies
uv sync
# Set your API key
export RENTCAST_API_KEY="your-api-key-here"Get an API key at app.rentcast.io.
Related MCP server: RentCast MCP Server
# stdio transport (default, for Claude Desktop / Claude Code)
uv run rentcast-mcp
# Or directly
uv run python -m rentcast_mcpAdd to your claude_desktop_config.json:
{
"mcpServers": {
"rentcast": {
"command": "uv",
"args": ["--directory", "/path/to/rentcast-mcp", "run", "rentcast-mcp"],
"env": {
"RENTCAST_API_KEY": "your-api-key-here"
}
}
}
}Tool | Description |
| Search homes for sale by location, price, beds, baths, sqft, year built |
| Full details for a specific listing by ID |
| Property records with owner info, tax history, sale history |
| Automated value estimate (AVM) with comparable sales |
| Rental value estimate for investment analysis |
| Market statistics and price trends for a zip code |
| Side-by-side comparison of multiple listings |
| Search recently sold properties (comps) |
# Search listings
uv run python cli.py search_sale_listings '{"zipCode": "95123", "minBedrooms": 4, "maxPrice": 2100000}'
# Get property value
uv run python cli.py get_property_value '{"address": "5500 Grand Lake Dr, San Antonio, TX, 78244"}'
# Market stats
uv run python cli.py get_market_stats '{"zipCode": "78701"}'
# Rent estimate
uv run python cli.py get_rent_estimate '{"address": "123 Main St, Austin, TX 78701"}'
# Compare listings
uv run python cli.py compare_listings '{"listing_ids": ["id1", "id2"]}'Free tier: 50 API calls/month. The server tracks call count per session and warns when approaching the limit.
Compare multiple sale listings side-by-side for easy evaluation.
Args: listing_ids: List of RentCast listing IDs to compare (2-10 listings recommended)
Inputs: listing_ids (required). Returns: result
Get full details for a specific sale listing by its RentCast ID.
Args: listing_id: The RentCast listing ID (returned by search_sale_listings)
Inputs: listing_id (required). Returns: result
Get aggregate market statistics and price trends for a zip code.
Args: zipCode: 5-digit zip code to get market data for historyRange: Number of months of history to include (1-24, default 12)
Inputs: zipCode (required), historyRange. Returns: result
Get property records including tax history, owner info, and sale history for an address.
Args: address: Full property address (e.g., "5500 Grand Lake Dr, San Antonio, TX, 78244")
Inputs: address (required). Returns: result
Get an automated value estimate (AVM) for a property with comparable sales.
Args: address: Full property address (e.g., "5500 Grand Lake Dr, San Antonio, TX, 78244") compCount: Number of comparable properties to include (1-25, default 10)
Inputs: address (required), compCount. Returns: result
Get a rental value estimate for investment analysis of a property.
Args: address: Full property address (e.g., "5500 Grand Lake Dr, San Antonio, TX, 78244")
Inputs: address (required). Returns: result
Search recently sold properties (comparable sales) for pricing evaluation.
Args: zipCode: 5-digit zip code to search in address: Full address for location-based search radius: Search radius in miles (max 100) latitude: Latitude for circular search longitude: Longitude for circular search minBedrooms: Minimum number of bedrooms maxBedrooms: Maximum number of bedrooms minPrice: Minimum sale price maxPrice: Maximum sale price saleDateRange: Date range for sales in YYYY-MM-DD,YYYY-MM-DD format (e.g., "2024-01-01,2025-01-01") propertyType: Property type filter -- Single Family, Condo, Townhouse, etc. limit: Maximum results to return (1-500, default 20) offset: Pagination offset
Inputs: limit, offset, radius, address, +9 more. Returns: result
Search for homes currently for sale by location, price range, size, and other criteria.
Args: zipCode: 5-digit zip code to search in city: City name (case-sensitive) state: 2-character state abbreviation (e.g., CA, TX) address: Full address string for precise search latitude: Latitude for circular radius search longitude: Longitude for circular radius search radius: Search radius in miles (max 100, requires lat/lng) propertyType: Property type filter -- Single Family, Condo, Townhouse, Manufactured, Multi-Family, Apartment, Land minBedrooms: Minimum number of bedrooms maxBedrooms: Maximum number of bedrooms minBathrooms: Minimum number of bathrooms maxBathrooms: Maximum number of bathrooms minPrice: Minimum listing price maxPrice: Maximum listing price minSqft: Minimum square footage maxSqft: Maximum square footage minLotSize: Minimum lot size in square feet maxLotSize: Maximum lot size in square feet minYearBuilt: Minimum year built maxYearBuilt: Maximum year built maxDaysOnMarket: Maximum days on market (min 1) status: Listing status -- Active (default) or Inactive limit: Maximum results to return (1-500, default 20) offset: Pagination offset
Inputs: city, limit, state, offset, +20 more. Returns: result
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Scored across 8 tools
Each tool targets a distinct data type and action: searching current listings, searching sold comps, fetching listing details, property records, value estimates, rent estimates, market stats, and comparing listings. Even the two search tools are clearly separated by active vs. sold status. No meaningful overlap between tools.
All tool names follow a consistent verb_noun pattern with snake_case: 'search_' for searches, 'get_' for retrievals, and 'compare_' for comparison. This is highly predictable and makes the tool set easy to navigate.
8 tools is well within the ideal 3-15 range for a focused real estate data server. Each tool covers a distinct core operation (search, detail, estimates, stats) without unnecessary bloat. The count feels perfectly scoped to the server's purpose.
The server covers the full range of read-only property data needs: active listings, recent sales, property records, valuation, rent estimation, and market trends. The only notable gap is the absence of rental listing search despite 'RentCast' branding, but this is minor given the rent estimate tool and the overall breadth.
Rentcast MCP — wraps Rentcast API (api.rentcast.io/v1)
Search SimplyRETS MLS listings and open houses; read listing and market analytics.
Redfin for-sale, for-rent and sold listings plus full property pages, as structured JSON.
Zillow for-sale, for-rent and sold listings, and full property details, as structured JSON.
