Real Estate MCP Server

Immobiliensuche und Marktanalyse von Redfin mit Einblicken in die Nachbarschaft

Dokumentation

Real Estate MCP — Property Search & Details for AI Agents (nexgendata/real-estate-mcp-server) Actor

MCP server exposing US property search and full listing detail (Redfin-sourced) as agent tools. Connect Claude, Cursor, n8n or the OpenAI Agents SDK. No API key. Pay per record.

Pricing

from $50.00 / 1,000 property records

This Actor is paid per event and usage. You are charged both the fixed price for specific events and for Apify platform usage.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

What's an Apify Actor?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes. In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours, and optionally produces a well-defined JSON output, datasets with results, or files in key-value store. In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects. You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For examples already wired to this Actor's own input schema, see the API section below.

Each client library has reference documentation the quickstart does not restate: JavaScript/TypeScript (npm install apify-client) and Python (pip install apify-client).

README

Real Estate MCP

A Model Context Protocol server that gives AI agents US residential real-estate data — property search and full listing detail, sourced from Redfin — as callable tools. For real-estate research, valuation and lead agents.

📊 Sample Output

1 real rows delivered by Real Estate MCP — Property Search & Details for AI Agents — run NlJemeZkMCFvpVm9M on build 0.0.38

typetooltimestamplocationresults
tool_callsearch_redfin_properties2026-09-22T06:48:56.974648+00:00Austin, TX5

Real rows from run NlJemeZkMCFvpVm9M on build 0.0.38 (2026-09-22), unedited apart from masked emails/phones and shortened long text; fields the source does not publish are empty.

🔧 Input reference

FieldTypeDefaultWhat it does
debugbooleanfalseEnable verbose logging in the MCP server stdout. Helpful when wiring a new AI client (Claude Desktop, Cursor, n8n) and you want to see every tool invocation. Leave off in producti…
maxToolCallSecondsinteger90Maximum time a single MCP tool invocation may run before the server aborts it and returns a timeout error to the AI client. Increase only if your agent issues unusually long-runni…

🧾 JSON sample record

One real record from run NlJemeZkMCFvpVm9M (emails/phones masked, long text shortened):

{
  "type": "tool_call",
  "tool": "search_redfin_properties",
  "timestamp": "2026-09-22T06:48:56.974648+00:00",
  "location": "Austin, TX",
  "results": 5
}

💰 Pricing

EventPrice (USD)When it is charged
Actor Start (apify-actor-start)$0.0005Charged when the Actor starts running. Number of events charged depends on Actor memory (one event per GB, minimum one event).
Property record (apify-default-dataset-item)$0.05One real-estate property record returned

Pay-per-event: you pay only for what the run delivers. A run that delivers nothing bills no result events (only the actor-start event, when the actor defines one). Example: a run that delivers 100 results costs 100 × $0.05 = $5.00 plus the start fee.

🔗 Related Actors

More from the NexGenData MCP servers for AI agents family:

29 more in this family on the NexGenData Store page.

🛠 Tools (2)

  • get_property_details — Full detail for a specific property.
  • search_redfin_properties — Search Redfin property listings by location and filters.

🔌 Connect (Claude Desktop / Cursor / n8n / OpenAI Agents SDK)

Add this MCP server to your client config:

{
  "mcpServers": {
    "real-estate": {
      "url": "https://nexgendata--real-estate-mcp-server.apify.actor/mcp"
    }
  }
}

Sample agent prompt:

Search for 3-bed homes under $600k in Denver and pull full details on the top result.

Pricing: $0.05 per property record (Pay-Per-Event). Runs in Standby mode.


Related NexGenData actors

Use caseActor
Redfin listings, sold history, comps in flat JSONRedfin Real Estate Scraper
Redfin listings via MCP (agent tools)redfin-mcp-server
UK property listings from RightmoveRightmove UK Real Estate
Singapore HDB resale transactionsSG HDB Resale Prices
Singapore URA private-property transactionsSG URA Property Transactions
Denmark housing market via BoligaBoliga Denmark Real Estate
AI-native financial data for LLM agentsFinance MCP Server
Local-business + map data MCP for agentsGoogle Maps MCP Server
Multi-source travel & rental MCPTravel MCP Server

Home: thenextgennexus.com Full catalog: apify.com/nexgendata

Actor input Schema

debug (type: boolean):

Enable verbose logging in the MCP server stdout. Helpful when wiring a new AI client (Claude Desktop, Cursor, n8n) and you want to see every tool invocation. Leave off in production.

maxToolCallSeconds (type: integer):

Maximum time a single MCP tool invocation may run before the server aborts it and returns a timeout error to the AI client. Increase only if your agent issues unusually long-running property scrapes (e.g. fetching hundreds of comps in one shot).

Actor input object example

{
  "debug": false,
  "maxToolCallSeconds": 90
}

Actor output Schema

results (type: string):

Successful property-search tool calls written to the default dataset.

API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

JavaScript example

import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "debug": false,
    "maxToolCallSeconds": 90
};

// Run the Actor and wait for it to finish
const run = await client.actor("nexgendata/real-estate-mcp-server").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

Python example

from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = {
    "debug": False,
    "maxToolCallSeconds": 90,
}

# Run the Actor and wait for it to finish
run = client.actor("nexgendata/real-estate-mcp-server").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

CLI example

echo '{
  "debug": false,
  "maxToolCallSeconds": 90
}' |
apify call nexgendata/real-estate-mcp-server --silent --output-dataset

MCP server setup

{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,nexgendata/real-estate-mcp-server"
        }
    }
}

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an Authorization: Bearer <APIFY_API_TOKEN> header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/LjGCyVAYO45XhjA7U/builds/enE3rUgXu1RTmapm9/openapi.json