A side-by-side look at the Casatoo and Engawa MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Casatoo for real estate work; choose Engawa 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?
C
Choose Casatoo when
You need dedicated capabilities in the Real Estate domain.
No tool names declared yet. Check the project README from the listing page.
Engawa 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.
Casatoo
No confirmed install command for Casatoo yet — follow the setup steps linked from its listing page rather than a guessed package name.
Casatoo is categorized under Real Estate and uses an install path we have not confirmed yet. Engawa belongs to Real Estate and uses a remote HTTP/SSE transport. Pick Casatoo for real estate work and Engawa 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. Casatoo has no confirmed install command yet — follow its own setup instructions.
Casatoo has no declared pricing — check the project's own site. Engawa 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 casatoo and engawa as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Casatoo has a quality signal of 37/100 (Fair) with 0 views, 0 installs and 0 GitHub stars. Engawa has 37/100 (Fair) with 0 views, 0 installs and 0 GitHub stars.