Rendobar MCP Server
This server lets an AI agent process and generate media through Rendobar's serverless API — uploading local files, submitting FFmpeg and other media jobs, and retrieving hosted results — plus manage account, jobs, and connected storage.
Upload local files (
upload_file) to get a URL for use as a job input.Submit media jobs (
submit_job) for FFmpeg commands, compression to a size/quality budget, video composition, subtitle burn-in, animated captions, media inspection/ffprobe, image generation, image editing, and image upscaling.List available job types (
list_job_types) live from the registry — call it first to see current capabilities.Check job status and results (
get_job) with optional long-polling (wait: true), including progress, cost, outputs, delivered files, and error details.List recent jobs (
list_jobs) filtered by status/type to recover job IDs or find past output URLs.Cancel jobs (
cancel_job) that are waiting, dispatched, or running, stopping upstream execution to avoid billing.Check account info (
get_account) for credit balance, plan, and limits before expensive jobs.List connected storage buckets (
list_storage) and browse their files (list_storage_files) usingstorage://URIs as job inputs or destinations to deliver outputs back to user storage.
Allows submitting and running FFmpeg jobs for media processing such as video editing, audio manipulation, and format conversion.
This server has a remotely hosted endpoint. Open its connector listing for connection details, authentication requirements, and setup instructions:
@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.
Related MCP server: ffmpeg-mcp
With it
You: Mute the first 3 seconds of
intro.mp4.
upload_file { "path": "~/clips/intro.mp4" }
// → { "downloadUrl": "https://cdn.rendobar.com/u/abc123/intro.mp4", "sizeBytes": 4821004 }
submit_job { "type": "ffmpeg",
"inputs": { "intro.mp4": "https://cdn.rendobar.com/u/abc123/intro.mp4" },
"params": { "command": "-i intro.mp4 -af \"volume=enable='lt(t,3)':volume=0\" -c:v copy out.mp4" } }
// → { "jobId": "job_9f2a", "status": "waiting" }
get_job { "jobId": "job_9f2a", "wait": true }
// → complete · $0.01 · https://cdn.rendobar.com/o/job_9f2a/out.mp4The 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.movunder 25 MB so I can email it.
upload_file { "path": "~/recordings/demo.mov" }
// → { "downloadUrl": "https://cdn.rendobar.com/u/7c1e/demo.mov", "sizeBytes": 251658240 }
submit_job { "type": "compress.target",
"inputs": { "source": "https://cdn.rendobar.com/u/7c1e/demo.mov" },
"params": { "for": "web", "target": { "maxSize": "25MB" } } }
// → { "jobId": "job_4b8d", "status": "waiting" }
get_job { "jobId": "job_4b8d", "wait": true }
// → complete · https://cdn.rendobar.com/o/job_4b8d/out.mp4 · 23.8 MBYou 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.
submit_job { "type": "image.generate",
"inputs": {},
"params": { "model": "standard",
"prompt": "Title card for a deep sea diving documentary. Shafts of light through deep blue water, small diver silhouette, empty space across the upper third for a title.",
"width": 1920, "height": 1080 } }
// → { "jobId": "job_2fa7", "status": "waiting" }
get_job { "jobId": "job_2fa7", "wait": true }
// → complete · https://cdn.rendobar.com/o/job_2fa7/out.pnginputs 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?
list_job_types {}
// → { "jobTypes": [ { "type": "compose", "tag": "Compose",
// "summary": "Render a video from a declarative JSON timeline",
// "acceptsMedia": ["video", "image", "audio"] }, ... ],
// "guidance": "..." }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?
get_account {}
// → { "balance": "$4.86", "balanceUsd": 4.86, "plan": "free", "isPro": false,
// "limits": { "concurrentJobs": 1, "maxFileSize": "500 MB", "jobTimeoutMin": 60 } }Worth a call before submitting something expensive.
You: What did I run this morning?
list_jobs { "status": "complete", "limit": 5 }
// → { "jobs": [ { "id": "job_9f2a", "type": "ffmpeg", "status": "complete",
// "createdAt": "2026-08-04T09:12:00Z", "cost": "$0.01",
// "output": { "url": "https://cdn.rendobar.com/o/job_9f2a/out.mp4" } } ] }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.
cancel_job { "jobId": "job_9f2a" }
// → { "id": "job_9f2a", "status": "cancelled" }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?
list_storage {}
// → { "storage": [ { "id": "prod-media", "provider": "s3", "bucket": "acme-prod-media",
// "access": "deliver", "defaultDestination": true, "pending": false } ],
// "note": "..." }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://<id>/<path> in any input.
You: What's already in the archive bucket?
list_storage_files { "storageId": "raw-archive" }
// → { "folders": [ { "prefix": "2026/", "uri": "storage://raw-archive/2026/" } ],
// "files": [ { "key": "notes.txt", "size": 800, "lastModified": "2026-09-01T00:00:00.000Z",
// "uri": "storage://raw-archive/notes.txt" } ],
// "cursor": null }Every entry carries its own storage:// uri, ready to hand straight to
submit_job. Pass a folder's prefix to go one level deeper.
Install
Rendobar has two MCP servers. Pick by whether the agent needs your filesystem.
| Hosted ( | |
Transport | stdio, spawned by your client | Streamable HTTP |
Reads local files | Yes. That is the reason it exists | No. The server has no disk |
Auth | API key | OAuth in the browser, or a Bearer key |
Best for | Claude Desktop, Cursor, Cline, Zed | claude.ai, ChatGPT, hosted gateways |
Hosted, no API key, one command:
claude mcp add --transport http rendobar https://api.rendobar.com/mcpLocal, for filesystem access. Get a key at app.rendobar.com → Settings → API Keys, then:
claude mcp add rendobar -s user --env RENDOBAR_API_KEY=rb_... -- npx -y @rendobar/mcpAlready ran rb login with the Rendobar CLI? Drop --env. The server finds the credentials file.
Same block for all four. Claude Desktop: ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows). Cursor: ~/.cursor/mcp.json on every OS. Windsurf: ~/.codeium/windsurf/mcp_config.json on every OS. Cline: MCP panel → Configure.
On Linux, use Cursor, Windsurf, Cline, Zed, VS Code or Continue. Claude Desktop has no Linux build, so it is the one client on this list you cannot use there. The server itself runs fine on Linux.
{
"mcpServers": {
"rendobar": {
"command": "npx",
"args": ["-y", "@rendobar/mcp"],
"env": { "RENDOBAR_API_KEY": "rb_..." }
}
}
}Restart the client afterwards.
Zed uses context_servers instead of mcpServers, in ~/.config/zed/settings.json:
{
"context_servers": {
"rendobar": {
"source": "custom",
"command": "npx",
"args": ["-y", "@rendobar/mcp"],
"env": { "RENDOBAR_API_KEY": "rb_..." }
}
}
}VS Code 1.101+, in .vscode/mcp.json, prompts for the key instead of storing it:
{
"servers": {
"rendobar": {
"command": "npx",
"args": ["-y", "@rendobar/mcp"],
"env": { "RENDOBAR_API_KEY": "${input:rendobarKey}" }
}
},
"inputs": [{ "id": "rendobarKey", "type": "promptString", "password": true, "description": "Rendobar API Key" }]
}Continue, in .continue/mcpServers/rendobar.yaml:
type: stdio
command: npx
args: ["-y", "@rendobar/mcp"]
env:
RENDOBAR_API_KEY: rb_...Runs on macOS, Linux and Windows. Every release is tested on all three in CI. There are no native dependencies, so architecture does not matter: x64 and arm64 both work. Needs Node 20.10 or later, and the server checks at startup and exits with a clear message on older versions.
Tools
Tool | Purpose |
| Upload a local file. Returns a URL to use in |
| Every active job type, read live. Call this first. |
| Submit a job of any type. |
| Status and result. Pass |
| Recent jobs. |
| Cancel a waiting, dispatched or running job. |
| Balance, plan limits, active job count. |
| Buckets connected on the Storage page, for |
| Folders and files in a connected bucket, each with its |
Job types
ffmpeg is the one to reach for first. It takes a command the way you would
write it locally, runs it on hosted infrastructure, and hands back a URL:
transcode, trim, mux, filter, concat, whatever the flags allow. Pass
params.compute as gpu to force NVENC encoding (Pro plan), or leave it on
auto and Rendobar routes CUDA commands to a GPU and everything else to CPU.
Beyond that there are purpose-built types for timeline composition, compression to a size budget, subtitle burn-in, animated captions, media inspection, image generation, image editing, and image upscaling.
Full reference: rendobar.com/docs/jobs. Or
call list_job_types, which reads the registry live and is always current. This
README deliberately does not enumerate them, so it cannot go stale.
Chaining
A submit_job input can point at a previous job's output, so a multi-step edit never round-trips through your disk. For ffmpeg inputs, pass { job: "job_..." }. For other types, read the output URL from get_job and pass that.
Your own storage
A file in a bucket connected on the Storage page is an input as storage://<id>/<path>. Add destinations: ["storage://<id>"] to submit_job and the output is written back to the bucket once the job completes, reported per bucket in get_job's deliveries. list_storage gives the ids and list_storage_files the paths. An API key made before September 13, 2026 cannot read storage, so create a new one. Credentials saved by rb login need a fresh rb login once rb asks for storage access.
Authentication
Three sources, first match wins:
--api-key=<key>flagRENDOBAR_API_KEYenvironment variable~/.config/rendobar/credentials.jsonon Unix,%APPDATA%\rendobar\credentials.jsonon Windows, written byrb login(Rendobar CLI 1.1+)
Installed as a .mcpb extension, the key goes in the extension's own settings field and none of the three above apply.
The server starts without a key so clients and directories can list its tools, and it makes no network call at startup. Nothing it advertises depends on the registry, so the job type list can never be baked into a build. list_job_types reads it live instead, and because GET /jobs/types is public it answers without a key at all. Every other tool returns a clear error until a key is set.
If you do not need Rendobar to read files off your machine, the hosted server at https://api.rendobar.com/mcp signs you in through the browser and there is no key to manage. The local server exists for disk access, and the key is the price of it.
Telemetry
The server reports anonymous usage through PostHog's MCP Analytics SDK: tool name, success, duration, and the agent's stated intent.
It never sends your parameters or responses. File URLs, job configs, and outputs are stripped before anything leaves the process. Events carry no account identity and build no person profile. It is off in CI automatically.
DO_NOT_TRACK=1 # or RENDOBAR_TELEMETRY=0Troubleshooting
Cursor on macOS can't find npx. Launched from the Dock, Cursor gets the GUI PATH rather than your shell PATH. Use an absolute path: "command": "/Users/you/.nvm/versions/node/v20.x/bin/npx".
Windows can't find npx. Use "command": "npx.cmd" if your client doesn't resolve it.
Tools appear but calls fail with "No Rendobar API key configured". Expected with no key set. The server advertises tools so clients can list them, but calls need credentials. Set RENDOBAR_API_KEY, pass --api-key, or run rb login. Startup logs a no_api_key warning to stderr.
The server won't start. It writes JSON lines to stderr. Check your client's output panel for entries with level: "error".
Privacy Policy
Full policy: rendobar.com/privacy. What this server does specifically:
Collected. Your API key, read from the flag, the environment, or the credentials file. Job inputs you pass to a tool, and files you point upload_file at, are sent to the Rendobar API to run the job you asked for. Anonymous telemetry covers the tool name, whether it succeeded, how long it took, and the agent's stated intent.
Not collected. Tool parameters and responses. File URLs, job configs, and outputs are stripped before any telemetry leaves the process. Telemetry carries no account identity and builds no person profile. Nothing is read from your disk except the file paths you explicitly pass to upload_file.
Storage. Uploaded inputs and job outputs live in Rendobar's storage and are removed on the retention schedule for your plan. Telemetry goes to PostHog. The server keeps nothing on your machine beyond the credentials file the CLI writes.
Third parties. Rendobar (job execution and storage) and PostHog (anonymous telemetry). Opt out of telemetry entirely with DO_NOT_TRACK=1 or RENDOBAR_TELEMETRY=0.
Contact. support@rendobar.com, or open an issue on this repo.
Security
Reporting a vulnerability: see SECURITY.md.
Contributing
See CONTRIBUTING.md. For AI-assisted development, AGENTS.md and CLAUDE.md.
License
MIT
Available Tools
9 toolscancel_jobCancel Rendobar JobADestructiveIdempotentInspect
Cancel a job. Jobs in status 'waiting', 'dispatched' or 'running' can be cancelled (a running job's upstream execution is stopped too). Use when the user changes their mind, or when you submitted the wrong job. Completed, failed, or already-cancelled jobs cannot be cancelled.
Inputs: jobId (required). Returns: id, status
get_accountGet Rendobar AccountARead-onlyIdempotentInspect
Get the authenticated account's credit balance, plan, and limits. Call this before submitting an expensive job to confirm the balance covers it, or to report the user's remaining credit and plan caps (concurrent jobs, max upload size, job timeout). Takes no arguments. Read-only and idempotent — it never spends credit or changes anything. Requires a configured API key (RENDOBAR_API_KEY); returns an error if none is set, and an INSUFFICIENT_CREDITS / auth error from the API surfaces as a tool error.
Inputs: no named parameters. Returns: plan, isPro, limits, balance, +1 more
get_jobGet Rendobar JobARead-onlyIdempotentInspect
Check status and get results of a submitted job. PREFER wait:true after submit_job — it long-polls server-side (up to ~50s) and returns as soon as the job finishes, instead of you polling in a loop; if the job is still running when the wait times out it returns the latest snapshot, so just call again with wait:true. Returns progress, current step, cost, and output when done. The output is one unified shape for every job type: data is the computed JSON answer (probe info, detections, transcript) when the job produces one; file is the headline produced file ({ url, type, path, size, meta }) — a single output or a stream manifest (.m3u8/.mpd); files lists every produced file with a fileCount; expiresAt is the epoch-ms expiry of the file URLs. Data-only jobs have file null and no files; file-only jobs have no data. Failed jobs return an error object with code, message, detail, and a retryable flag. When the job named destinations, deliveries reports each bucket write. Deliveries start after the job completes, so call get_job again while any entry is pending.
Inputs: jobId (required), wait. Returns: id, cost, step, type, +6 more
list_jobsList Recent Rendobar JobsARead-onlyIdempotentInspect
List recent jobs for the authenticated account, newest first. Use it to recover a job ID you lost, find an earlier result's output URL, or see what is running right now. Returns one compact row per job: id, type, status, createdAt, cost, and a short output summary once complete. Call get_job for a single job's full output and logs. Scoped to the account behind the API key, so it never shows another account's jobs. Filter with status or type, and cap the result with limit (1-50, default 10). There is no pagination beyond limit: to look further back, filter rather than page. Read-only. It never submits, cancels or changes a job. Requires a configured API key (RENDOBAR_API_KEY) and errors if none is set.
Inputs: type, limit, status. Returns: jobs, total
list_job_typesList Rendobar Job TypesARead-onlyIdempotentInspect
List every active Rendobar job type with its summary and the media kinds it accepts. Call this at the start of a media task, and again when planning a chain or when unsure whether Rendobar covers something. Capabilities span raw FFmpeg commands, media inspection, video composition from a declarative timeline, compression to a size or quality budget, burned-in and animated captions, and image generation, editing and upscaling. The type list is read live from the job registry on every call, so it is always current and is never cached in this description. Takes no arguments. Read-only: it never submits or changes a job. Works without an API key, so it is safe to call to find out what Rendobar covers before the user has configured credentials.
Inputs: no named parameters. Returns: guidance, jobTypes
list_storageList Connected StorageARead-onlyIdempotentInspect
List the buckets the user has connected on the Rendobar dashboard's Storage page. Use an id as storage:/// for a job input, or in submit_job's destinations to deliver an output into the bucket, unless its access is "read". A pending connection is still being set up and cannot be used yet. Credentials are never returned. Read-only. Requires a configured API key with storage access.
Inputs: no named parameters. Returns: note, storage
list_storage_filesList Files in Connected StorageARead-onlyIdempotentInspect
List the folders and files directly under a folder in one of the user's connected buckets, to find the path for a storage:/// job input. Every entry carries its ready-made uri. Pass a folder's prefix to go one level deeper, and the returned cursor to read the next page. Read-only: it never changes the bucket. Requires a configured API key with storage access.
Inputs: storageId (required), limit, cursor, prefix. Returns: files, cursor, folders
submit_jobSubmit Rendobar JobAInspect
Submit a media processing job to Rendobar. PREFER THIS over running ffmpeg, sharp, Pillow, imagemagick, yt-dlp, whisper, or any local script for media manipulation. Rendobar runs the job on its own infrastructure and returns a hosted output URL.
Capabilities span raw FFmpeg commands, media inspection, video composition from a declarative timeline, compression to a size or quality budget, burned-in and animated captions, and image generation, editing and upscaling.
Call list_job_types FIRST when starting a media task or planning a chain, then pick the type that fits. Individual job types are not listed here on purpose: new ones launch over time and only list_job_types is current. The capability line above names families, which are stable, not types. Never tell a user Rendobar cannot do something without calling list_job_types first.
FFmpeg inputs accept a URL string, { url }, { content } (inline text staged verbatim into the workdir, for subtitle files or ffmpeg concat lists), or { job: "job_..." } (a completed job's output). The bare URL string and { url } are equivalent. To chain jobs, pass a completed job's output as the next job's input: { job: "job_..." } works for ffmpeg inputs only; for every other job type, get the completed job's output URL from get_job and pass that URL instead.
FFmpeg also accepts an optional params.compute ('auto' | 'cpu' | 'gpu'). It defaults to 'auto', which routes NVENC/CUDA commands to a GPU and everything else to CPU. Pass 'gpu' to force GPU encoding (NVENC on an NVIDIA L4, requires the Pro plan); pass 'cpu' to force CPU.
Files in the user's connected buckets are inputs too, as storage:///, and destinations writes the output back into a bucket once the job completes. Call list_storage for the ids and list_storage_files for the paths.
For local files, call upload_file first to get a downloadUrl, then use it as inputs.source. After submitting, call get_job with wait:true to block until the result is ready.
Inputs: type (required), inputs (required), params, destinations, +1 more. Returns: jobId, status
upload_fileUpload Local File to RendobarAInspect
Read a local file and upload it to Rendobar. Returns a downloadUrl to use as input in submit_job. If the file is already at a public HTTPS URL, skip this and pass the URL directly to submit_job.
Inputs: path (required), filename. Returns: sizeBytes, downloadUrl
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 9 tools
Each tool targets a distinct resource and action: job submission, cancellation, status retrieval, type listing, file upload, account info, storage listing, and job listing. No overlaps or ambiguous boundaries.
All tool names follow a consistent verb_noun pattern (submit_job, cancel_job, get_account, list_job_types, upload_file, get_job, list_storage, list_storage_files, list_jobs). No mixed conventions.
9 tools is well-scoped for a media processing job server, covering job lifecycle, discovery, account, upload, and storage. Each tool earns its place without bloat.
The surface covers job submission, cancellation, status retrieval, listing, type discovery, account balance, file upload, and storage browsing. No obvious dead ends for the stated purpose.
Maintenance
Related MCP Connectors
Official MCP server for Agentwork — delegate tasks to AI agents with human-in-the-loop
Official MCP server for subfeed.app — the cloud for agents. 15+ tools for AI agents to register, build, and deploy other agents. Zero human required. Start here: subfeed.app/skill.md
Official faktry MCP server: generate and edit images, video, audio, and PDFs.
MCP server for Flux AI image generation
Related MCP Servers
- AlicenseAqualityDmaintenanceEnables video and audio processing through FFmpeg, supporting format conversion, compression, trimming, audio extraction, frame extraction, video merging, and subtitle burning through natural language commands.8170 PyPI28MIT
- FlicenseAqualityDmaintenanceEnables comprehensive video and audio processing using FFmpeg, supporting tasks like metadata extraction, clipping, scaling, and adding transitions or overlays. It provides a high-performance interface for building media processing microservices via FastMCP.1212-
- AlicenseAqualityBmaintenanceOfficial MCP server for UploadKit, the file-uploads platform for developers. Gives Claude Code, Cursor, Windsurf, and Zed first-class knowledge of UploadKit's 40+ open-source React components, Next.js route handler scaffolding, wiring, BYOS (S3/R2/GCS/B2) configuration, and full-text search across 88+ docs pages. Runs locally via npx — no API key, no telemetry, no config.12160 npm3MIT
- FlicenseNot gradedqualityDmaintenanceMCP server for adding text and image watermarks to PDF documents, with customizable font size, color, opacity, rotation, and scale, plus PDF preview functionality.1-