Rendley docs

Get started

Automation connector

The automation connector gives your AI assistant direct access to Rendley’s video editor. It can create a project, add your media, run the edit, handle approvals, render the result, and return a download link.

https://mcp.rendley.com/mcp/automation

Use this endpoint when you want the assistant to finish the video in the conversation. The lighter directory connector stops after preparing a project and creative brief.

What a run looks like

Start with one request:

Try this prompt

Use interview.mp4 and logo.svg. Cut the interview to the strongest two minutes, remove filler and long pauses, add branded captions and a short animated title, then export a vertical 1080p MP4.

Your client and Rendley work through the steps together:

  1. Add the source files to a new or existing project.
  2. Analyze and transcribe the material when the edit needs it.
  3. Plan the creative and technical work.
  4. Apply timeline edits and create any missing media.
  5. Save the editable project.
  6. Render the requested output and return a temporary download link.

You stay in the conversation throughout. You only need to open Rendley Studio if you want to inspect or adjust the timeline visually after the run finishes.

Built on Rendley Agent

MCP uses the same Rendley Agent that powers POST /v1/agent. It has access to the timeline editor, media analysis, generative-media services, project data, brand kit, and rendering pipeline. It also knows how to handle social formats, ads, UGC-style videos, explainers, typography, subtitles, transitions, color, pacing, and composition.

Your MCP client brings two useful abilities to that workflow. It can pass in files from your computer and use its own model to author motion graphics. It can also respond when Rendley pauses for approval or a creative decision. If you later need server-to-server automation at scale, you can move the same type of work to the Automated Editing API.

Connect it

Most remote MCP clients accept a configuration like this:

{
  "mcpServers": {
    "rendley-automation": {
      "url": "https://mcp.rendley.com/mcp/automation"
    }
  }
}

The first connection opens a Rendley sign-in page. Approve access and the client stores the session. Clients that cannot complete browser sign-in can send a Rendley API key instead.

Some clients use serverUrl instead of url, or require "type": "http". Follow the page for your client:

Approvals and questions

Every MCP edit is interactive. The agent can run free editing steps without interrupting you, but it pauses when it needs a meaningful decision:

  • Plan review: approve the proposed approach or describe what to change.
  • Credit-consuming work: approve, reject, or revise planned AI generation and processing.
  • Creative review: accept a generated asset or request a different direction.
  • Clarification: answer a question the original brief left open.
  • Motion-clip authoring: let your connected model create the requested animation without Rendley generation credits.

Reply in plain language and the same run continues. If your client supports MCP elicitation, some choices may appear as a small form instead of a chat message.

Continue and revise

After an edit finishes, ask for another change in the same project:

Try this prompt

Continue the latest edit in the Launch video project. Keep the timeline structure, replace the opening with a stronger hook, make the captions larger, and export a square version too.

The agent can resume the project’s latest conversation so earlier creative context carries forward. You can also start a fresh conversation against the same project when you want a clean brief.

Canceling an edit

You can ask the client to cancel a pending or running edit. No further steps run, but changes saved before cancellation remain in the project.

Export settings

If you do not specify export settings, Rendley produces a high-quality 1080p MP4. You can request:

  • Format: H.264 MP4 or VP8 WebM.
  • Resolution: 360p, 480p, 720p, 1080p, 2K, or 4K.
  • Quality: high, medium, or low.

Rendering runs in the background and often takes a few minutes. The client checks progress and returns the download link when the file is ready.

Download links expire after a few hours. Save the file rather than keeping the URL as permanent storage.

Plans and credits

The automation endpoint can connect on a free account, but editing and export require a paid Rendley plan. AI generation, AI transformations, and rendering may consume Rendley credits. The agent reports the planned cost-sensitive work before it runs.

Motion graphics authored by your connected model do not consume Rendley generation credits. See Motion graphics for how this uses the model plan attached to your MCP client.

Automation connector versus directory connector

Rendley also offers a lighter connector at https://mcp.rendley.com/mcp. It can plan a video, add source files, and prepare a Rendley project for you to review, but it does not run the edit or export the result.

The lighter connector is available in the Claude directory. Use the automation endpoint above when you want the assistant to finish the video. See The Claude directory version for details.