Stream Estate vs Figma Context MCP
A side-by-side look at the Stream Estate and Figma Context MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Stream Estate for real estate work as a local process; choose Figma Context MCP for architecture & design as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose 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.
Choose Figma Context MCP when
- You need dedicated capabilities in the Architecture & Design domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: API key required.
- You have the keys it needs:
FIGMA_API_KEY, PORT. - You want tools like
get_figma_data, download_figma_images.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Real Estate | Architecture & Design |
| Quality signal | 60/100 · Good | 71/100 · Great |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | API key required |
| Pricing | Not declared | Free |
| Required env vars | STREAM_ESTATE_API_KEYSTREAM_ESTATE_BASE_URL | FIGMA_API_KEYPORT |
| Verified owner | Community listing | Community listing |
| GitHub stars | 3 | 16,057 |
| Directory activity | 2 views 0 installs 0 upvotes | 9 views 0 installs 0 upvotes |
| Tools | 13 | 2 |
| Full listing | View Stream Estate | View Figma Context MCP |
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
Figma Context MCP tools 2
get_figma_dataGet comprehensive Figma file data including layout, content, visuals, and component informationdownload_figma_imagesDownload SVG and PNG images used in a Figma file based on the IDs of image or icon nodes. Images will be saved relative to the server's image directory: /home/user
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": {
"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"
}
}
}
}
Figma Context MCP
{
"mcpServers": {
"glips-figma-context-mcp": {
"command": "npx",
"args": [
"-y",
"figma-developer-mcp"
],
"env": {
"FIGMA_API_KEY": "YOUR_FIGMA_API_KEY_HERE",
"PORT": "YOUR_PORT_HERE"
}
}
}
}
Frequently asked questions
Stream Estate is categorized under Real Estate and uses a local stdio subprocess. Figma Context MCP belongs to Architecture & Design and uses a local stdio subprocess. Pick Stream Estate for real estate work and Figma Context MCP for architecture & design.
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. Figma Context MCP 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 glips-figma-context-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. Figma Context MCP has 71/100 (Great) with 9 views, 0 installs and 16,057 GitHub stars.