A side-by-side look at the Engawa and Real Estate Capitale MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Engawa for real estate work over a hosted endpoint; choose Real Estate Capitale MCP for real estate over a hosted endpoint. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
E
Choose Engawa when
You need dedicated capabilities in the Real Estate domain.
No tool names declared yet. Check the project README from the listing page.
Real Estate Capitale MCP 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.
Engawa is categorized under Real Estate and uses a remote HTTP/SSE transport. Real Estate Capitale MCP belongs to Real Estate and uses a remote HTTP/SSE transport. Pick Engawa for real estate work and Real Estate Capitale MCP 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.
Engawa has no declared pricing — check the project's own site. Real Estate Capitale MCP 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 engawa and real-estate-capitale-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Engawa has a quality signal of 37/100 (Fair) with 0 views, 0 installs and 0 GitHub stars. Real Estate Capitale MCP has 37/100 (Fair) with 1 views, 0 installs and 0 GitHub stars.