realestate-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| REALESTATE_MCP_CHANNEL | No | Browser channel; msedge also works | chrome |
| REALESTATE_MCP_PROFILE | No | Where the warm browser profile lives | ~/.realestate-mcp/profile |
| REALESTATE_MCP_TIMEOUT | No | Navigation timeout in ms | 60000 |
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": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_listingsA | Search realestate.com.au for properties to buy, rent, or recently sold. Returns up to 25 listings per page with address, price, bed/bath/car counts, land size, agency, agents, inspection times and auction dates. Call resolve_location first if the user's location is vague or misspelled. |
| get_listingA | Fetch full detail for one realestate.com.au listing, including the complete description, all photos, floorplans, agency and agent contacts. Accepts a listing URL or a bare numeric listing ID. |
| resolve_locationA | Turn partial or ambiguous location text into canonical REA suburb/region names with state and postcode. Fast (no browser needed). Use this to disambiguate before search_listings — e.g. "bondi" returns Bondi, Bondi Beach, Bondi Junction. |
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 3 tools
Each tool serves a distinct purpose: searching listings, fetching a specific listing's full details, and resolving ambiguous locations. There is no overlap between them, and the descriptions clearly differentiate their roles.
All tool names follow a consistent verb_noun pattern in snake_case: search_listings, get_listing, resolve_location. The naming is predictable and aligns with each tool's function.
With only 3 tools, the set is tightly scoped for a real estate listing search and detail service. Each tool is necessary and there is no bloat, making it easy for an agent to understand and use the server effectively.
The core workflow of searching, resolving locations, and viewing listing details is well-covered. A minor gap is the lack of explicit pagination support in search_listings, but this is not a significant limitation for most use cases.