Rendley docs

Work with your files

Rendley MCP can start with media you already have. Local files can go straight into a project, with no manual upload in Rendley Studio or public hosting step.

The exact workflow depends on where the file is and what your MCP client can access.

Files on your computer

Desktop, terminal, and IDE clients such as Codex, Claude Code, Cursor, or VS Code can often read files from paths you provide.

Use /Users/me/Recordings/interview.mp4 and /Users/me/Brand/logo.svg. Cut the interview to 90 seconds, add the logo to the end card, add captions, and export a 1080p MP4.

Your client reads the bytes and uploads them directly to Rendley’s storage. Rendley adds the files to the project library, runs the edit in the cloud, and returns the completed project or export.

Large files use multipart uploads automatically. You can add up to 50 files in one upload batch. An edit can receive up to 20 new files at once, so the client adds larger collections to the project library in batches before starting the edit.

Files attached to a chat

In ChatGPT, Claude, and other browser clients, attach the files to the conversation and refer to them by name.

Use the attached demo.mp4, voiceover.wav, and logo.png. Sync the demo to the voiceover, add the logo at the end, and export it in 9:16.

Whether this works directly depends on how the client exposes attachments to connected tools. A capable client provides Rendley with a temporary download reference or gives the assistant access to the file in its working environment.

If the client cannot pass the attachment through, use a public HTTPS link or add the file to the Rendley project in Studio. The assistant can continue from the existing project media afterwards.

Files already on the web

Give the agent a public, direct-download HTTPS URL:

Import https://cdn.example.com/assets/product-demo.mp4, make a 30-second vertical cut, and add captions.

Rendley fetches the file server-side. This works in browser clients and avoids transferring the bytes through the assistant’s environment.

A webpage URL is different from a direct file URL. If you want the agent to read a page and use its text or images, say so:

Read https://example.com/launch and use the page’s copy and product images to create a 30-second launch video.

Media already in Rendley

You can reuse footage from an existing project without uploading it again.

Open the “Customer story” project. Use the interview and office B-roll already in its library to make a 30-second LinkedIn cut.

If several projects or files could match, use their exact names. The agent asks you to choose when it cannot safely identify the source.

Brand assets

Logos, fonts, product images, voice choices, and other reusable assets can live in a workspace brand kit. Ask the agent to add them once, then reference the kit in later projects.

Add logo.svg and Inter-Variable.ttf to the Marketing workspace brand kit, then use that kit for this edit.

Brand assets persist across projects in the workspace. Ordinary project uploads belong to the project library instead.

How uploads are handled

File bytes go directly to object storage using short-lived upload targets; they do not pass through the MCP server itself. The client then completes the upload so the media becomes available to the project.

A file added to the library is not automatically placed on the timeline. Your prompt should say how the agent should use it.

If an upload stops halfway through

Ask the client to retry the failed file. Each file or multipart segment has its own upload target, so it does not need to restart the entire batch. If an upload target has expired, ask it to create a new one.

Do not open the Rendley editor while an MCP edit is actively running or paused; opening the project can take over the live editing session. Wait until the agent reports that the edit has finished.