# Rend cloud MCP beta

Connect to https://rend.ai/api/mcp using Streamable HTTP and a personal Rend bearer token. Access currently requires an allowlisted Rend account. OAuth onboarding is not yet available. Studio runs in the browser; no Desktop app or local GPU is required.

## Native HTTP clients

Add the endpoint in your client's MCP settings. Store your personal token in the client's credential settings and use it for bearer authentication. Never put it in a prompt or shared project.

## Stdio bridge

With access to the Rend source package, Node 22.13+ and its MCP dependencies installed, keep the token in an owner-only file outside the repository (permissions 0600). From the Rend project folder:

```sh
node mcp/client-setup.mjs --cloud --token-file "$HOME/.config/rend/mcp-token" --write-configs "$HOME/Desktop/rend-cloud-configs"
node mcp/client-setup.mjs --cloud --token-file "$HOME/.config/rend/mcp-token" --doctor
```

Merge the generated Rend entry into Codex, Cursor or Claude Desktop, then reconnect. The bridge does not require local FFmpeg or Rend Desktop.

## Make a video

Choose the intended project or create one. Describe the brief and confirm the aspect ratio and frame rate. Upload media or provide direct HTTPS media URLs; chat attachments depend on your client exposing the files.

The tools can generate media, edit a versioned JSON composition and render an export. Open the returned Studio link to see the same clips, layers, audio, captions and edits. Generation and processing return background jobs; external clients check rend_get_job to follow their progress.

Edit in chat or by hand in Studio. Export again to bake the changes into a new MP4. Earlier sources and exports remain available.