Connect your listing video workflow
ReeltyPro integrations work with your own listing photos, account credits and saved videos. Review property facts and every completed video in ReeltyPro before sharing.
Account linking is currently unavailable
The configured account sign-in service must be restored before new MCP connections can complete. Protocol and public discovery endpoints are deployed; authenticated workflows have not passed live review. There is no public ChatGPT approval or recommendation claim. Contact support for the current rollout status.
MCP connection
The remote Streamable HTTP endpoint is https://reeltypro.com/mcp. Account linking uses OAuth authorization code with S256 PKCE and dynamic public-client registration. Approve access in the normal ReeltyPro sign-in flow. Do not paste API keys, login codes or payment details into a conversation.
videos:readreads current capabilities and only your saved video jobs, review state and released downloads.uploads:writereserves a signed owned photo batch and uploads exact supplied JPEG, PNG or WebP bytes.videos:writerequests a video under your existing balance, source, account and capacity checks.
From your photos to a reviewed video
- Read
reeltypro_capabilitiesfor current readiness, source requirements, limits and the exact photo-rights affirmation. - Reserve an owned batch with
reeltypro_start_upload, then callreeltypro_upload_photofor each exact supplied photo. ChatGPT file intake accepts at most 4,000,000 bytes per photo; base64 intake accepts at most 3,000,000 decoded bytes. - Explicitly authorize existing credit use and affirm the displayed rights statement before
reeltypro_create_video. Supply only your own photos, facts and room labels. - Use
reeltypro_list_videosandreeltypro_video_statusto inspect actual owned states and follow review links. Queued, processing and review-held jobs are not released downloads.
Retain each request UUID and retry with identical arguments. Upload retries retain the same batch, index and bytes. Cancelling an assistant request does not cancel an admitted render. Staging, social publishing, credit purchases, review approval and render cancellation are not exposed as MCP tools. No paid provider render has been run for MCP review.