Stream Estate vs Hindsight

A side-by-side look at the Stream Estate and Hindsight MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.

Stream Estate logoStream EstateReal Estate · Local subprocess (stdio)MCP server for the Stream.estate French real estate API60GoodAuth: not declaredHindsight logoHindsightKnowledge & Memory · Local subprocess (stdio)Hindsight: Agent Memory That Works Like Human Memory - Built for AI Agents to manage Long Term Memory57GoodAuth: api key required

Verdict: choose Stream Estate for real estate work as a local process; choose Hindsight for knowledge & memory as a local process. You can also run both side by side in one mcpServers block.

Which MCP server should you choose?

Stream Estate logoChoose Stream Estate when

  • You need dedicated capabilities in the Real Estate domain.
  • You prefer a local stdio subprocess transport.
  • You have the keys it needs: STREAM_ESTATE_API_KEY, STREAM_ESTATE_BASE_URL.
  • You want tools like get-cities, location-autocomplete, get-points-of-interest.
Explore Stream Estate

Hindsight logoChoose Hindsight when

  • You need dedicated capabilities in the Knowledge & Memory domain.
  • You prefer a local stdio subprocess transport.
  • Its auth model fits you: API key required.
  • You have the keys it needs: HINDSIGHT_API_LLM_API_KEY, HINDSIGHT_API_LLM_PROVIDER, HINDSIGHT_DB_PASSWORD.
Explore Hindsight

Feature & specification comparison

Rows where the two servers differ are marked.

SpecStream Estate logoStream EstateHindsight logoHindsight
CategoryReal EstateKnowledge & Memory
Quality signal60/100 · Good57/100 · Good
Install commandConfirmedConfirmed
TransportLocal subprocess (stdio)Local subprocess (stdio)
AuthNot declaredAPI key required
PricingNot declaredFree
Required env varsSTREAM_ESTATE_API_KEYSTREAM_ESTATE_BASE_URLHINDSIGHT_API_LLM_API_KEYHINDSIGHT_API_LLM_PROVIDERHINDSIGHT_DB_PASSWORD
Verified ownerCommunity listingCommunity listing
GitHub stars353,003
Directory activity 2 views 0 installs 0 upvotes 14 views 0 installs 0 upvotes
Tools13Not listed

Tools & capabilities

Stream Estate tools 13

  • get-citiesSearch French cities by name, zipcode, INSEE code, or geographic polygon. Returns city IDs needed for property search filters.
  • location-autocompleteAutocomplete cities and departments by search query. Returns IDs needed for location filters in search-properties and create-search.
  • get-points-of-interestFind points of interest (schools, hospitals, restaurants, parking) near a location. Returns facilities within a radius of given coordinates.
  • get-price-per-meterGet price per m² statistics (average, median, time series) for properties matching filters. Useful for market analysis and property valuation.
  • search-propertiesSearch French real estate properties with extensive filters for location, price, size, rooms, energy rating, and more. Returns paginated results with property details, adverts, photos, and nearby stations. Use location-autocomplete first to resolve city/department IDs.
  • get-propertyGet full details for a single property by UUID, including all adverts, price history events, photos, contact info, and nearby transit stations.
  • find-similar-propertiesFind properties similar to a given property. Useful for market comparisons and finding alternatives.
  • create-searchCreate a saved search with optional webhook notifications for real-time property alerts. Configure location, price, size filters and webhook endpoints.
  • list-searchesList all saved searches for the authenticated user. Can filter by notification status and title.
  • get-searchGet details of a specific saved search by its ID.
  • update-searchUpdate an existing saved search with new criteria, filters, or webhook configuration.
  • delete-searchDelete a saved search by its ID.
  • +1 more on the listing page

Hindsight tools

No tool names declared yet. Check the project README from the listing page.

Ready-to-paste client configs

Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.

Stream Estate

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "stream-estate-2": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-stream-estate"
      ],
      "env": {
        "STREAM_ESTATE_API_KEY": "YOUR_STREAM_ESTATE_API_KEY_HERE",
        "STREAM_ESTATE_BASE_URL": "YOUR_STREAM_ESTATE_BASE_URL_HERE"
      }
    }
  }
}

Hindsight

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "vectorize-io-hindsight": {
      "command": "npx",
      "args": [
        "-y",
        "@vectorize-io/hindsight-coding-agents"
      ],
      "env": {
        "HINDSIGHT_API_LLM_API_KEY": "YOUR_HINDSIGHT_API_LLM_API_KEY_HERE",
        "HINDSIGHT_API_LLM_PROVIDER": "YOUR_HINDSIGHT_API_LLM_PROVIDER_HERE",
        "HINDSIGHT_DB_PASSWORD": "YOUR_HINDSIGHT_DB_PASSWORD_HERE"
      }
    }
  }
}

Frequently asked questions

Stream Estate is categorized under Real Estate and uses a local stdio subprocess. Hindsight belongs to Knowledge & Memory and uses a local stdio subprocess. Pick Stream Estate for real estate work and Hindsight for knowledge & memory.

Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.

Stream Estate has no declared pricing — check the project's own site. Hindsight is listed as free. Auth: api key required. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.

Yes. MCP clients support multiple servers: add stream-estate-2 and vectorize-io-hindsight as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, Stream Estate has a quality signal of 60/100 (Good) with 2 views, 0 installs and 3 GitHub stars. Hindsight has 57/100 (Good) with 14 views, 0 installs and 53,003 GitHub stars.