Server Everything vs Stream Estate

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

Server Everything logoServer EverythingOther Tools and Integrations · Local subprocess (stdio)MCP server that exercises all the features of the MCP protocol73GreatAuth: no auth requiredStream Estate logoStream EstateReal Estate · Local subprocess (stdio)MCP server for the Stream.estate French real estate API60GoodAuth: not declared

Verdict: choose Server Everything for other tools and integrations 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?

Server Everything logoChoose Server Everything when

  • You need dedicated capabilities in the Other Tools and Integrations domain.
  • You prefer a local stdio subprocess transport.
  • Its auth model fits you: No auth required.
  • You want tools like echo, get-annotated-message, get-env.
Explore Server Everything

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.

SpecServer Everything logoServer EverythingStream Estate logoStream Estate
CategoryOther Tools and IntegrationsReal Estate
Quality signal73/100 · Great60/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 ownerCommunity listingCommunity listing
GitHub stars91,5123
Directory activity 9 views 0 installs 0 upvotes 2 views 0 installs 0 upvotes
Tools1613

Tools & capabilities

Server Everything tools 16

  • echoEchoes back the input string
  • get-annotated-messageDemonstrates how annotations can be used to provide metadata about content.
  • get-envReturns all environment variables, helpful for debugging MCP server configuration
  • get-header-paramsReturns its region argument and the Mcp-Param-Region HTTP header it arrived in. Demonstrates x-mcp-header (a 2026-07-28 Streamable HTTP client mirrors the argument into the header) and JSON Schema 2020-12 input and output schemas.
  • get-resource-linksReturns up to ten resource links that reference different types of resources
  • get-resource-referenceReturns a resource reference that can be used by MCP clients
  • get-structured-contentReturns structured content along with an output schema for client data validation
  • get-sumReturns the sum of two numbers
  • get-tiny-imageReturns a tiny MCP logo image.
  • gzip-file-as-resourceCompresses a single file using gzip compression. Depending upon the selected output type, returns either the compressed data as a gzipped resource or a resource link, allowing it to be downloaded in a subsequent request: during the current session for a 2025-era client, or for ten minutes at a minted URI on protocol version 2026-07-28.
  • trigger-list-changedSends a notifications/<list>/list_changed for the tool, prompt or resource list. On protocol version 2026-07-28 it is delivered on each subscriptions/listen stream that asked for that list; a 2025-era client receives it unsolicited.
  • trigger-log-messagesSends one log message at each logging level during the call. On protocol version 2026-07-28 only the messages at or above the level the request names in _meta (io.modelcontextprotocol/logLevel) are sent, and none if it names no level; a 2025-era client gets those at or above the level it set with logging/setLevel. Deprecated: logging is deprecated as of protocol version 2026-07-28.
  • +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.

Server Everything

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "modelcontextprotocol-server-everything": {
      "command": "npx",
      "args": [
        "-y",
        "@modelcontextprotocol/server-everything"
      ]
    }
  }
}

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

Server Everything is categorized under Other Tools and Integrations and uses a local stdio subprocess. Stream Estate belongs to Real Estate and uses a local stdio subprocess. Pick Server Everything for other tools and integrations 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.

Server Everything 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 modelcontextprotocol-server-everything and stream-estate-2 as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, Server Everything has a quality signal of 73/100 (Great) with 9 views, 0 installs and 91,512 GitHub stars. Stream Estate has 60/100 (Good) with 2 views, 0 installs and 3 GitHub stars.