RentCast MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| RENTCAST_API_KEY | Yes | Your RentCast API key |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_property_dataC | Get detailed information about a specific property. |
| get_property_valuationA | Get valuation data for a specific property. Note: RentCast API may return basic property data instead of detailed valuations depending on subscription tier. |
| get_rent_estimateB | Get rent estimate for a specific property. Note: RentCast API may return basic property data instead of detailed rent estimates depending on subscription tier. |
| get_market_statisticsC | Get market statistics for a specific area. |
| get_property_listingsC | Get property listings for a specific area. |
| get_property_recordsC | Get property records with various filters. Returns a list of property records. |
| get_random_property_recordsC | Get random property records. Returns a list of random property records. |
| get_property_record_by_idC | Get a specific property record by ID. |
| get_sale_listingsC | Get sale listings with various filters. Returns a list of sale listings. |
| get_sale_listing_by_idC | Get a specific sale listing by ID. |
| get_rental_listingsC | Get rental listings with various filters. Returns a list of rental listings. |
| get_rental_listing_by_idC | Get a specific rental listing by ID. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 12 tools
The tools have clear distinctions between property, rental, and sale data, but there is significant overlap in the 'get_property_data', 'get_property_record_by_id', and 'get_property_records' tools, which could confuse agents about which to use for specific property queries. Descriptions help clarify, but the boundaries are not entirely distinct.
All tool names follow a consistent 'get_<resource>_<action>' pattern using snake_case, with variations like 'by_id' or 'listings' that are predictable and readable. There are no deviations in naming conventions across the set.
With 12 tools, the count is reasonable for a real estate data server, covering market stats, property details, and listings. It might be slightly heavy, but each tool serves a specific purpose without obvious redundancy, fitting well within the typical 3-15 range for a focused domain.
The tool set provides comprehensive read-only coverage for real estate data, including statistics, property records, and listings for rentals and sales. Minor gaps exist, such as no update or delete operations, but this is typical for a data retrieval API, and agents can work around it for most use cases.