Git vs Stream Estate

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

Git logoGitVersion Control · Local subprocess (stdio)Tools to read, search, and manipulate Git repositories.81ExcellentAuth: no auth requiredStream Estate logoStream EstateReal Estate · Local subprocess (stdio)MCP server for the Stream.estate French real estate API60GoodAuth: not declared

Verdict: choose Git for version control work as a local process; choose Stream Estate for real estate as a local process. You can also run both side by side in one mcpServers block.

Which MCP server should you choose?

Git logoChoose Git when

  • You need dedicated capabilities in the Version Control domain.
  • You prefer a local stdio subprocess transport.
  • Its auth model fits you: No auth required.
  • You want tools like repo_path, context_lines, target.
Explore Git

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

Feature & specification comparison

Rows where the two servers differ are marked.

SpecGit logoGitStream Estate logoStream Estate
CategoryVersion ControlReal Estate
Quality signal81/100 · Excellent60/100 · Good
Install commandConfirmedConfirmed
TransportLocal subprocess (stdio)Local subprocess (stdio)
AuthNo auth requiredNot declared
PricingFreeNot declared
Required env varsNone listedSTREAM_ESTATE_API_KEYSTREAM_ESTATE_BASE_URL
Verified owner VerifiedCommunity listing
GitHub stars91,5123
Directory activity 49 views 0 installs 0 upvotes 2 views 0 installs 0 upvotes
Tools1613

Tools & capabilities

Git tools 16

  • repo_path
  • context_lines
  • target
  • message
  • MERGE_HEAD
  • HEAD
  • files
  • max_count
  • start_timestamp
  • end_timestamp
  • branch_name
  • base_branch
  • +4 more on the listing page

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

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.

Git

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "git": {
      "command": "uvx",
      "args": [
        "installations"
      ]
    }
  }
}

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"
      }
    }
  }
}

Frequently asked questions

Git is categorized under Version Control and uses a local stdio subprocess. Stream Estate belongs to Real Estate and uses a local stdio subprocess. Pick Git for version control work and Stream Estate for real estate.

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.

Git is listed as free. Auth: no auth required. Stream Estate has no declared pricing — check the project's own site. 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 git and stream-estate-2 as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, Git has a quality signal of 81/100 (Excellent) with 49 views, 0 installs and 91,512 GitHub stars. Stream Estate has 60/100 (Good) with 2 views, 0 installs and 3 GitHub stars.