Turn real-estate listing photos into property videos from your AI assistant.
Reel MCP server exists for a simple reason — assistants are far more useful when they can act on Reel directly instead of describing what you should do. Turn real-estate listing photos into property videos from your AI assistant.
You sign in once through your browser (OAuth + PKCE — no API keys, no secrets), and every call is proxied through the backend's /mcp endpoint, which stays the single authority for auth, plans, and permissions. This bridge's one superpower on top of that: it can read local image files and stream them straight into a project — something a purely remote server can't do.
Once Reel is connected, these are the calls the assistant has available:
help — Guided, always-current walkthrough (also the getting_started prompt)whoami — Confirm auth; reports plan, canWrite, and a writeAccess reason. Run first.resolve_address — Geocode a free-text address → ranked candidates (for real-listing projects)add_image_from_file — Upload a local image into a project (presigned upload — no storage creds)edit_image — AI photo edit — virtual staging, twilight, upscale, seasonal, replace/remove/add, manualrender_movie — Assemble the timeline into the final listing videoreel-estate-mcp on npm is all you need. Most clients run it directly, so configuration is a few lines and a restart.
Plenty of file and storage access servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Reel's toolset — help, whoami, resolve_address and 3 more — is a fair guide to whether it matches your workflow. It is maintained by com.tryreelestate; worth a glance at recent repository activity before you build anything load-bearing on it.
We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.
| Tool | What it does |
|---|---|
| help | Guided, always-current walkthrough (also the getting_started prompt) |
| whoami | Confirm auth; reports plan, canWrite, and a writeAccess reason. **Run first.** |
| resolve_address | Geocode a free-text address → ranked candidates (for real-listing projects) |
| add_image_from_file | Upload a **local** image into a project (presigned upload — no storage creds) |
| edit_image | AI photo edit — virtual staging, twilight, upscale, seasonal, replace/remove/add, manual |
| render_movie | Assemble the timeline into the final listing video |
{
"mcpServers": {
"reel-estate": {
"command": "npx",
"args": ["-y", "reel-estate-mcp"]
}
}
}Add to claude_desktop_config.json, then restart Claude Desktop.
Scoped local file access — read, write, search and reorganise files in directories you explicitly allow.
Search and read your Drive — Docs, Sheets and files become context your assistant can actually use.
Query, modify and analyse local SQLite databases in conversation — the fastest way to chat with a data file.
Build a programmable telecommunications stack for connecting telephony services with the Internet via a cloud-based utility.
Chat with your second brain — search, read and write vault notes through the Local REST API.
Connects AI models to an Obsidian knowledge base for direct access and manipulation of notes and folders.