Reel-E

ai.reel-ePublished by reel-e.aiOfficial publisherv1.0.0Updated Nov 7, 2026

Make and edit real estate listing videos, photos and websites from your AI assistant.

VerifiedStreamable HTTPWeb executableMedia & Design

Overview

AI-generated overview

Reel-E is a remote MCP server that lets an assistant create and edit real estate listing videos, photos and websites.

What you can do
  • Create and edit real estate listing videos from the assistant.
  • Create and edit listing photos.
  • Build and edit listing websites.
  • No tool list, instructions or README were supplied, so the exact operations and their inputs are not documented here.
When to use it
Useful for real estate agents, marketers or property teams that want an assistant to produce or revise listing videos, photos and websites without leaving the chat.
Requirements
A remote MCP endpoint at the provider's site, connected over streamable HTTP. Authentication is required and uses OAuth, so the user must sign in with a Reel-E account. No environment variables or headers are declared.
Before you install
The server is authorized through OAuth and can create and edit published listing media and websites, so changes may be visible to clients or the public. Review what the assistant produces before publishing. No details on data handling or pricing were provided.

Installation

In SourceWeft

  1. Open Reel-E in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/ai.reel-e%2Freel-e/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "reel-e": {
      "type": "http",
      "url": "https://www.reel-e.ai/mcp"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.0.0LatestNov 7, 2026

Score

67% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.