Reel Estate MCP

What reel-estate-mcp does

The reel-estate-mcp MCP server brings Reel Estate’s property-video workflow into MCP-compatible assistants. It supports project browsing, address resolution, local image uploads, AI photo editing, clip generation, timeline changes, and final movie rendering. The available workflow is suited to real-estate agents, marketers, or automation systems that begin with listing photos and need a finished property video.

Photo editing operations include virtual staging, twilight conversion, upscaling, seasonal changes, and replace, remove, add, or manual edits. The broader tool set also supports motion clips, voiceover and other timeline audio, image or text overlays, timeline reordering, and rendered movie discovery.

How it works

The reel-estate-mcp MCP server runs locally over stdio and forwards API operations to Reel Estate’s backend /mcp endpoint. The backend remains responsible for authentication, plan checks, and permissions. Convenience tools expose common operations, while list_endpoints and api_request provide access to the backend’s API catalog and routes.

On the first tool call, the server opens a browser for Reel Estate sign-in. OAuth authorization code flow with PKCE returns through a local callback at http://localhost:8765/callback; access and refresh tokens are then cached under ~/.reel-estate-mcp. The whoami tool reports the current plan, whether writes are allowed, and the reason when they are not. Use login to begin or clear a session and logout to revoke the server session and remove local credentials.

Setup and configuration

Node.js 18 or newer, a Reel Estate account, and an MCP-compatible client are required. Add the server to an MCP client with:

{
  "mcpServers": {
    "reel-estate": {
      "command": "npx",
      "args": ["-y", "reel-estate-mcp"]
    }
  }
}

Claude Code can instead launch it with claude mcp add reel-estate -- npx -y reel-estate-mcp. No environment variables or API keys are required. The first authentication flow needs access to a browser and the local callback port. To switch accounts, run logout or remove the token cache directory.

Tools and capabilities

The reel-estate-mcp MCP server provides tools for:

• Checking authentication and plan write access with whoami.
• Browsing projects, clips, rendered movies, and available voices.
• Resolving free-text property addresses into ranked candidates.
• Uploading local images to a project through presigned uploads.
• Editing images with staging, twilight, upscale, seasonal, and object-change operations.
• Generating motion clips and checking their status.
• Adding audio or image/text overlays to a timeline.
• Moving or reordering timeline elements.
• Rendering the completed timeline into a listing video.

The help tool and getting_started prompt provide a guided walkthrough. Start with whoami before attempting project changes or generation.

Limitations and notes

Free Reel Estate accounts are read-only through MCP. Creating, editing, generating, uploading, and rendering operations require a paid plan; read operations such as browsing projects, clips, and movies remain available to free accounts. A blocked write can return 403 MCP_PAID_PLAN_REQUIRED.

Authentication is account-based rather than API-key-based. The server uses a public OAuth client and PKCE, and its local token cache contains the session state needed for later calls. Local image uploads are supported, but the server does not require users to provide storage credentials. Generated operations and permissions remain subject to Reel Estate’s backend rules and plan limits.

Getting started with this reel-estate-mcp MCP server

Always refer to the official documentation for the most accurate and up-to-date information.