rendobar/mcp

Serverless media processing for AI agents.
The official Model Context Protocol server for Rendobar.
Docs  · 
npm  · 
Glama  · 
Discord
@rendobar/mcp is the official Model Context Protocol server for Rendobar, a serverless media processing API. The server runs locally over stdio and reads files straight from your disk, so an AI agent can take a file off your machine, process it on Rendobar's infrastructure, and hand back a hosted URL.
Rendobar covers both sides of media work.
**Transform what you have.** Run any FFmpeg command against video, audio or images the way you would write it locally. Inspect a file and get a normalized summary plus the full ffprobe report. Compose video from a declarative JSON timeline. Compress to a target size or quality, where the encoder searches candidate encodes and returns the smallest file that clears the bar. Burn in subtitles from SRT, VTT or ASS, or let it transcribe when none is given.
**Generate what you do not.** Create an image from a text prompt on hosted open-weight diffusion models. Edit up to four reference images from a written instruction, no masks and no coordinates. Upscale on a one-step diffusion restoration model that reconstructs detail rather than only sharpening. The same model-backed layer drives the transcription and keyword highlighting behind animated captions, so this is not an image-only capability.
The job list grows over time, so this README names families rather than types. list_job_types reads the current set live from the registry on every call.
Published to npm as @rendobar/mcp and to the official MCP Registry as com.rendobar/mcp.
Without it
> **You:** Mute the first 3 seconds of intro.mp4.
The agent tells you to install FFmpeg. Then you go looking for how to gate a
filter on a timestamp, land on volume=enable='lt(t,3)', and lose another few
minutes to quote escaping in your shell. Nobody remembers that syntax, which is
the problem.
With it
> **You:** Mute the first 3 seconds of intro.mp4.
The agent writes the filter. Rendobar runs it. Nothing gets installed on your
machine, and -c:v copy means the video stream is never re-encoded.
Two more things to ask for
**Hit a size budget.**
> **You:** Get demo.mov under 25 MB so I can email it.
You give it the ceiling, not a bitrate. The encoder searches candidate encodes
and returns the smallest file that still clears the quality bar, so you are not
guessing at CRF values to land under a mail server's limit.
**Generate an image.**
> **You:** Make a 1920x1080 title card for a video about deep sea diving.
inputs is empty because nothing is being transformed. Ask for a tier
(economy, standard, premium) and the platform picks the model, or pin an
exact model id to reach its own controls. Requested dimensions are snapped to
what the chosen model can actually render.
The rest of the surface
Six more tools, and the prompts that reach them.
> **You:** What can Rendobar actually do?
Read live from the job registry on every call, which is why nothing in this
README enumerates job types. A new one appears here without a release.
> **You:** How much credit is left?
Worth a call before submitting something expensive.
> **You:** What did I run this morning?
The compact row is enough to find a result you lost. Call get_job when you
need the full output.
> **You:** Stop that one, I picked the wrong file.
Works on waiting, dispatched and running jobs. A running job's upstream
execution is stopped too, so you are not billed for work you cancelled.
> **You:** Where can this land once it's done?
The buckets connected on the Storage page, without the endpoint or region an
agent has no use for. Use the id in destinations, or as
storage:// / in any input.
> **You:** What's already in the archive bucket?
Every entry carries its own storage:// uri, ready to hand straight to