Integration

Stream Estate integration

Stream Estate (formerly Melo) aggregates French real estate listings into properties, each grouping the adverts published for it on several sites. Search properties for sale or rent with filters on price, surface, rooms, location, energy rating and publisher, fetch one property with its adverts or list the properties similar to it, read price per square meter indicators and nearby points of interest, resolve city and department ids for the location filters, and manage saved searches that send new matches and advert events to a webhook or by email, with a tool that sends a simulated webhook to test your endpoint. Query filters that need nested index encoding (full text expressions, geographic shapes, city polygons) are not exposed. Authentication is an API key created on the API Keys page of the Stream Estate console, sent in the X-API-KEY header.

Connect Stream Estate How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

When this happens, do that in Stream Estate.Built from the 13 Stream Estate tools below, on the connection you add once.

What you can do with Stream Estate

Each of these is one operation on one endpoint, available both as a workflow step and as a tool an AI agent can call on its own. Nothing bundles several operations into one action, so what a run did stays readable afterwards.

Most endpoints run on the free plan. A few, mainly the ones that publish on your behalf, need a paid plan.

Search, 5 operations

create_searchCreate searchPOSTCreate a saved search with its criteria (property types, transaction type, budget, surface, rooms, location) and, when notificationEnabled is true, the webhook or email that receives new matches and advert events.
delete_searchDelete searchDELETEDelete a saved search by its uuid; it stops sending notifications.
get_searchGet searchGETGet one saved search by its uuid, with all its criteria and notification settings.
list_searchesList searchesGETList your saved searches, optionally filtered by title or by whether notifications are enabled, optionally ordered by title, paginated.
update_searchUpdate searchPUTUpdate a saved search: the fields you send replace the stored ones (criteria, title, notification settings).

Property, 3 operations

get_propertyGet propertyGETGet one property by its uuid, with every advert published for it (price, contact, energy rating), its city, price, surface, rooms, pictures and nearby stations.
list_propertiesList propertiesGETSearch properties (homes, apartments, land, offices...) for sale or rent across the aggregated French listing sites, filtered by price, surface, rooms, location, energy rating, publisher type and dates. 10 per page by default, at most 30.
list_similar_propertiesList similar propertiesGETList the properties similar to a given property, as returned by Stream Estate, with optional date filter, ordering and pagination (at most 30 per page).

City, 1 operation

list_citiesList citiesGETList French cities filtered by name, label, slug, zipcode or INSEE code, with pagination, as stored by Stream Estate.

Location, 1 operation

search_locationsSearch locationsGETSearch cities and departments by name and return their IRIs, to use in the includedCities[] and includedDepartments[] filters of the property search and price indicators. This route answers without an API key.

Point of interest, 1 operation

list_points_of_interestList points of interestGETList the points of interest (shops, schools, transport and other facilities) around a latitude and longitude, within a radius, optionally limited to some facility types.

Price indicator, 1 operation

get_price_per_meterGet price per meterGETGet the price per square meter average, median and time series of the properties matching the given criteria, aggregated by the chosen interval. Takes the same filters as the property search.

Webhook, 1 operation

send_test_webhookSend test webhookGETSend a simulated `match` (when eventType is omitted) or advert `event` payload to the given endpoint, to test the webhook your saved searches notify. Your server should answer HTTP 200; a failed webhook is retried up to five times, one hour apart.

Use Stream Estate from Claude Code, Cursor or Codex

Connect Stream Estate in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its Stream Estate operations become tools the client can call, next to every other integration you connected.

Claude Code

claude mcp add --transport http livecontext https://livecontext.ai/mcp --header "X-API-Key: YOUR_API_KEY"

Codex (~/.codex/config.toml)

[mcp_servers.livecontext]
url = "https://livecontext.ai/mcp"

[mcp_servers.livecontext.http_headers]
"X-API-Key" = "YOUR_API_KEY"

Cursor, Claude Desktop and other JSON configs

{
  "mcpServers": {
    "livecontext": {
      "type": "http",
      "url": "https://livecontext.ai/mcp",
      "headers": {
        "X-API-Key": "YOUR_API_KEY"
      }
    }
  }
}

Set up the MCP server step by step

How to connect Stream Estate

Create your workspace
Sign up free. Nothing to install.
Connect Stream Estate once
Add your Stream Estate connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.
Describe the job in chat
The workflow builds itself in front of you and picks the endpoints it needs. Drag the steps yourself on the canvas whenever you would rather be explicit.