Reel Estate MCP vs DealMachine — MCP Server Comparison | AllMCPs
Side-by-Side Model Context Protocol Comparison
Reel Estate MCP vs DealMachine
In-depth architectural comparison of the Reel Estate MCP and DealMachine MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.
At a Glance & Executive Verdict
Reel Estate MCP
Real Estate · Local stdio
Quality: 60/100 (Good) | Auth: OAuth 2.0
DealMachine
Real Estate · Remote HTTP/SSE
Quality: 43/100 (Fair) | Auth: No auth required
Verdict Summary: Choose Reel Estate MCP if you need specialized Real Estate tools running via a local process. Choose DealMachine if your workspace requires Real Estate integration with remote web transport. Both servers can be configured concurrently in your client's mcpServers manifest.
Which MCP Server Should You Choose?
Choose Reel Estate MCP when:
You need dedicated capabilities in the Real Estate domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: OAuth 2.0 (Freemium).
Show the upstream MCP URL, read-only flag, the account plan, whether writes are allowed (canWrite) with a plain-language writeAccess reason, and the live /users/profile response for the OAuth-authenticated user. Good first call to confirm auth and whether create/generate/render tools will work (free accounts are read-only over the MCP). If not signed in, it returns a 'run login' error — use the `login` tool.
login
Authenticate with the backend. If not already logged in, returns an authorization URL to open in your browser; approve the sign-in and the token is cached in the background, then retry your action. (Browser-based login can't be popped reliably from here, so you click the link.)
logout
Clear the cached OAuth session (and best-effort revoke it server-side) so the next tool call re-authenticates via the browser. Use to switch accounts or reset a broken auth state.
list_projects
GET /projects for the authenticated user. Supports paging, sorting, search, and status filter.
Ready-to-Paste Client Configurations
Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).
Reel Estate MCP is categorized under Real Estate and uses a local stdio subprocess. In contrast, DealMachine belongs to Real Estate using remote streaming HTTP/SSE transport. Select Reel Estate MCP when you need capabilities focused on real estate and DealMachine when you require tools for real estate.
GET /projects/:id — full project document for the authenticated user.
project_stats
GET /projects/stats — aggregate project counts/metrics for the authenticated user.
list_clips
Clips for the authenticated user. With projectId -> GET /clips/project/:projectId; otherwise GET /clips (the clip library) with paging/status.
list_movies
Rendered movies for the user. With projectId -> GET /movies/project/:projectId; else GET /movies.
list_voices
GET /voices — voiceover voices available to the user (stock + cloned).
get_usage
GET /billing/usage — credit and export usage for the authenticated user.
help
Guided, numbered walkthrough of the whole pipeline — sign in → create a project → add photos → edit → animate clips → add music/voiceover/overlays → arrange → render — with example args and the gotchas (async polling, paid gating). Call this first if you're not sure where to start.
list_endpoints
Return the curated catalog of API endpoints (grouped) so you know what `api_request` can call. Not exhaustive — every mounted route is reachable, this covers the main surface.
+11 more tools listed on main page
DealMachine Tools (0)
No explicit tool names declared in metadata yet. Check project README on main listing page.