Stream Estate vs Codebase Memory MCP

A side-by-side look at the Stream Estate and Codebase Memory MCP 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 declaredCodebase Memory MCP logoCodebase Memory MCPKnowledge & Memory · Local subprocess (stdio)Code-intelligence engine that indexes a repo into a persistent knowledge graph — functions, classes, call chains, HTTP routes, cross-service links. 159 languages via tree-sitter + Hybrid LSP, sub-ms structural queries, 99% fewer tokens than grep. Single static binary, zero dependencies, 100% local. npx codebase-memory-mcp73GreatAuth: no auth required

Verdict: choose Stream Estate for real estate work as a local process; choose Codebase Memory MCP 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

Codebase Memory MCP logoChoose Codebase Memory MCP when

  • You need dedicated capabilities in the Knowledge & Memory domain.
  • You prefer a local stdio subprocess transport.
  • Its auth model fits you: No auth required.
  • You want tools like index_repository, search_graph, query_graph.
Explore Codebase Memory MCP

Feature & specification comparison

Rows where the two servers differ are marked.

SpecStream Estate logoStream EstateCodebase Memory MCP logoCodebase Memory MCP
CategoryReal EstateKnowledge & Memory
Quality signal60/100 · Good73/100 · Great
Install commandConfirmedConfirmed
TransportLocal subprocess (stdio)Local subprocess (stdio)
AuthNot declaredNo auth required
PricingNot declaredFree
Required env varsSTREAM_ESTATE_API_KEYSTREAM_ESTATE_BASE_URLNone listed
Verified ownerCommunity listingCommunity listing
GitHub stars347,308
Directory activity 2 views 0 installs 0 upvotes 8 views 1 installs 1 upvotes
Tools1317

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

Codebase Memory MCP tools 17

  • index_repositoryIndex a repository. full/moderate add semantics; fast omits them; cross-repo-intelligence links services. Reports coverage gaps.
  • search_graphFind symbols via BM25 query, regex name/qn filters, or semantic_query. Rows keep qn/file/lines and in/out over CALLS/USAGE/CALL_REFERENCE/INHERITS/IMPLEMENTS.
  • query_graphRead-only Cypher for multi-hop, aggregation, complexity, or cross-service analysis. Default: 200 visible rows with exact/lower-bound totals and truncation; continue safely with next_cursor. graph=missed is a file tree of flagged coverage gaps; absence is not proof of completeness. Use get_graph_schema(diagnostics=full) for properties.
  • trace_pathTrace callers/callees, data flow, or cross-service paths. Defaults exclude tests and resolver evidence. Rows keep qn/hop with explicit totals, relations, and continuations.
  • get_code_snippetRead a search_graph symbol. auto bounds source and outlines large containers; full restores up to 500 lines. Source/outline pages continue; coverage_note marks gaps.
  • get_file_outlineDeclaration outline of one exact repository-relative file: optional exact label filter, source order, exact total/offset/limit paging; file/folder/container nodes excluded.
  • get_graph_schemaGet node-label and edge-type counts. diagnostics=full also lists queryable properties.
  • compare_graphsCompare two indexed snapshots: deterministic target-only additions and base-only removals of stable node/edge identities; each set capped by limit and a 512 KiB budget with exact totals and truncation reasons.
  • get_architectureCompact counts, languages, packages, entry points. Request structure, dependencies, routes, hotspots, boundaries, layers, clusters, cycles, or file_tree; path scopes a directory.
  • search_codeGraph-ranked text search: compact symbols, full bounded source, or file paths.
  • list_projectsList projects with stable paging. Identity is lean; stats adds graph sizes.
  • delete_projectDelete a project from the index
  • +5 more on 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"
      }
    }
  }
}

Codebase Memory MCP

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "deusdata-codebase-memory-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "codebase-memory-mcp"
      ]
    }
  }
}

Frequently asked questions

Stream Estate is categorized under Real Estate and uses a local stdio subprocess. Codebase Memory MCP belongs to Knowledge & Memory and uses a local stdio subprocess. Pick Stream Estate for real estate work and Codebase Memory MCP 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. Codebase Memory MCP is listed as free. Auth: no auth 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 deusdata-codebase-memory-mcp 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. Codebase Memory MCP has 73/100 (Great) with 8 views, 1 installs and 47,308 GitHub stars.