MCP Connector
Connect Renderly to Claude and other AI assistants and create personalized videos at scale in plain language — render from your own templates and projects, no code required.
Renderly is available as an MCP (Model Context Protocol) connector — a remote server that brings your Renderly library into your AI assistant. Connect it to Claude on the web, desktop, or in Claude Code, then create videos by just talking:
"Render my real-estate template for these 10 listings."
Claude discovers your templates and projects, fills in the variables, fires the renders, and hands back the video links. It's the fastest way to generate personalized video at scale — your AI agent does the work, drawing from your own Renderly account and credits.
This is the same rendering engine and credits as the REST API and no-code integrations — just driven conversationally. If you're integrating Renderly into your own backend, use the API instead.
Quick facts
| Endpoint | https://renderly.video/api/mcp |
| Transport | Streamable HTTP (remote) |
| Auth | OAuth 2.1 ("Sign in with Renderly") or a Renderly API key |
| Cost | Standard Renderly credits — ~1 credit per minute of 1080p video (rounded up to the nearest 0.5) |
| Scope (v1) | Render from your existing templates and projects with text and media-URL variable overrides |
What you can do
This release lets your AI assistant work with the videos you've already built in Renderly — discovering their variables, personalizing them, rendering, and tracking status. No new tooling or code on your side.
| You ask… | Renderly does… |
|---|---|
| "What Renderly templates can I use?" / "List my projects." | Lists your projects and the public system templates |
| "What can I personalize in my 'Listing Promo' project?" | Returns the variables and their current values |
| "Render my Listing Promo with address '123 Ocean Dr' and price '$1.2M'." | Starts a render with your replacement values |
| "Render my Sale template for each of these 8 product names." | Fires a batch of personalized renders |
| "Is that render done? Give me the link." | Polls the job and returns the final video URL |
Connecting
You need an existing Renderly account — the connector acts as your account, drawing from your credits and your own library. If you connect with an email that has no Renderly account, the tools will tell you to sign up first.
Claude.ai (web)
Add a custom connector pointing at https://renderly.video/api/mcp, then Sign in with Renderly.
- Pro / Max (personal): add it directly under Settings → Connectors.
- Team / Enterprise: an Owner adds it once under Organization settings → Connectors; members then enable it for themselves. Each member's renders draw from their own Renderly account.
Claude Code (terminal)
With a Renderly API key (simplest):
claude mcp add --transport http --scope user renderly \
https://renderly.video/api/mcp \
--header "Authorization: Bearer rnd_YOUR_API_KEY"Or with OAuth — add it without the header, then run /mcp to sign in:
claude mcp add --transport http --scope user renderly \
https://renderly.video/api/mcpClaude Desktop, Cursor & other MCP clients
Add a custom connector with the same URL (https://renderly.video/api/mcp) and authenticate with OAuth, or supply an Authorization: Bearer rnd_… header.
Confirm it works
Ask your assistant to "list my Renderly templates" or "what's my Renderly credit balance?". If it answers with your library, you're connected.
Authentication & accounts
- OAuth ("Sign in with Renderly") is the path for Claude.ai and desktop apps. API keys (
rnd_…) are ideal for terminal and developer use — generate one under Settings → API Keys (see API Keys). - Your AI assistant only ever acts as your Renderly account — renders draw from your credits, and you only see your own templates and projects.
- Connect with the email that owns your Renderly account. Signing in with a different email is the most common reason authorization fails.
Tools reference
The connector exposes these tools to your AI client. You don't call them by hand — your assistant picks the right one from your request — but it's useful to know what's available.
| Tool | Purpose |
|---|---|
renderly_whoami | Confirm the connection; returns account email + credit balance |
renderly_list_templates | List public system templates and their variables |
renderly_list_projects | List your own projects (those with personalizable variables) |
renderly_get_variables | Return the variables (and current values) for a template or project |
renderly_create_render | Start a render from a template/project with variable replacements (uses credits) |
renderly_get_render_status | Poll a render job; returns status, progress, and the final video URL |
Example: a batch of listings
A realtor with 10 new listings and a Renderly "Listing Promo" template can hand the whole batch to Claude in one message instead of editing 10 videos by hand:
- Paste the 10 listings (address, price, photo) and ask Claude to render the Listing Promo for each.
- Claude reads the template's variables —
address,price, and the background image. - For every listing, Claude calls
renderly_create_renderwith the right values, kicking off 10 renders. - Claude tracks each job's status.
- Claude hands back 10 finished video URLs, ready to post to listings, social, or email.
The same pattern works for product announcements, social variations, and any personalized output — anywhere you'd otherwise render the same composition many times with different values.
What's in this release
Covered: rendering from templates and projects you've already built, with text and media-URL variable overrides.
Not yet (on the roadmap):
- Generating a brand-new video from a text prompt
- Uploading local media files through the connector (media variables take a URL for now — see Uploading media)
- A few advanced editor features
Troubleshooting
Connection won't authorize. Make sure you're signing in with the email that owns your Renderly account. If that email has no account, sign up at renderly.video first.
Does it cost anything? The connector is free to add. Renders use your normal Renderly credits — about 1 credit per minute of 1080p video.
Which clients work? Claude.ai (web), Claude Desktop, Claude Code, Cursor, and other MCP-compatible clients.
Can my team use it? Yes — on Team and Enterprise, an admin adds the connector once and members enable it. Each member renders against their own account.
Where to go next
| If you want to… | Read |
|---|---|
| Build the templates your assistant will render | Templates & Personalization |
| Generate an API key for terminal/developer use | API Keys |
| Integrate Renderly into your own backend | Rendering · API reference |
| Automate with no-code tools instead | Integrations |