projects_render
Start the native captioned render of a ready ('cooked') Fry project; returns a render ID. State-changing: requires an Idempotency-Key.
LABSCO SUMMARY
Start-and-poll is the right shape for rendering, and the vendor's own advice is to start read-only.
Video rendering takes minutes, so a tool that returns a render id immediately and a second that reports progress is exactly right — no held connection, no timeout. ContentFries urges least privilege on the key itself, starting read-only and adding scopes, which is worth following since renders spend credits. Credit packs never expiring is a genuinely friendly detail; most vendors expire them.
What it is
ContentFries' hosted endpoint. Their knowledge base says it exposes the same operations as their Control API across projects, recipes, jobs, content review, Planner, credits and webhooks, but publishes only two tools concretely.
What you get
- projects_render — start the native captioned render of a project that is ready, returning a render id
- renders_get — poll that id, getting progress while it works and the result when it finishes or fails
Requirements
An API key as a bearer token — the same workspace-scoped key the Control API uses. Free gives 50 monthly credits and one workspace; credit packs start at $4 and never expire; Creator is $39/month for 650 credits that roll over.
Setup effort
Follow the published steps — Sign in to ContentFries, open Integrations and choose the workspace the agent should use.
USE CASES
01
Rendering without waiting on a call
Kick the render off, take the id, and poll for progress rather than blocking.
02
Keeping the key narrow
Start with a read-only scope and widen only when rendering is meant to happen.
2 tools
Listed in project docs. Your client may show a different list.
renders_get
Poll a render by ID until it completes or fails; returns progress while working and the recorded output URL for a completed render (URL access still subject to delivery policy). Read-only.
BEFORE YOU INSTALL
What to know first
Tools you get
2 tools named in the project's documentation.
Requires
API key as bearer token (same workspace-scoped key as the Control API)
INSTALLATION
Connect your client
Server setup
Sign in to ContentFries, open Integrations and choose the workspace the agent should use.
Create a key with only the scopes the agent needs.
Save the raw key immediately. ContentFries shows it only once.
Use the hosted MCP connection details shown in Integrations and authenticate with the same API key.
