Remotion / render contracts / MCP
Local Remotion Rendering with Short-Lived Render Contracts
Render contracts keep Composition input small, scoped, and revocable.
The flow
The local code agent gets schemas, composes a project, saves the descriptor, and requests a render contract. The local renderer loads the hosted Composition bundle and passes only the contract input props.
The Composition then fetches the descriptor with an opaque render token. The token can expire, be read-limited, and be revoked.
What not to pass
Do not pass a long-lived MCP or API token into Composition code. Hosted Composition bundles are downloadable JavaScript, so private authorization belongs in the Worker.
Use the fragment catalog
Turn these workflows into a render descriptor your local Remotion renderer can consume.
Browse fragments