Redfin MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| HASDATA_API_KEY | Yes | Your HasData API key, required to authenticate with the Redfin MCP server. Used as the x-api-key header for remote HTTP connections or as the HASDATA_API_KEY environment variable for the stdio launcher. |
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
} |
| completions | {} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| hasdata_redfin_listing_getRealEstateListingsA | Get Redfin Real Estate Listings Searches Redfin for-sale, for-rent, or sold listings with pagination. The location accepts a zipcode, city, neighborhood, school, school district, apartment-building name, or a full street address. Returns each listing with address, Redfin URL, list price, beds/baths, square footage, lot size, year built, days on market, status, coordinates, photos, MLS number, and HOA; an address or building returns a single property card instead. Use for real-estate market research, lead generation for agents, price/DOM trend analysis, and feeding URLs into the Redfin Property endpoint for deep-dive details. |
| hasdata_redfin_property_getPropertyDetailsA | Get Redfin Property Details Fetches the full Redfin property page by URL. Returns address, list/sold price, price history, Redfin Estimate, beds/baths, square footage, lot size, year built, property type, HOA, days on market, school ratings, tax history, listing agent, full description, photos, walk/transit/bike scores, and nearby comparables. Use for CMA reports, investor due-diligence, valuation models, listing enrichment, and powering buyer-assistant agents with verified property facts. |
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 2 tools
The two tools have clearly distinct purposes: one searches for listings based on location, the other fetches detailed property data from a URL. There is no overlap since the search output feeds into the property details endpoint, creating a clear sequential workflow.
Both tools follow the same pattern: hasdata_redfin_<resource>_<get...>. The resource (listing vs property) and action (getRealEstateListings vs getPropertyDetails) are consistently structured, making the naming predictable and readable.
With only 2 tools, the server feels minimal, but the scope is narrowly defined around Redfin data retrieval. This falls on the borderline of the 1-2 tool threshold, though the tools are complementary and not redundant.
The search and details tools cover the core workflow of finding listings and then diving into property specifics. Minor gaps exist such as no direct lookup by MLS ID or enhanced market analytics, but the essential data retrieval surface for Redfin is present.