서버리스 인프라를 사용하여 AI agent가 비디오, 오디오, 이미지를 변환하고 텍스트 프롬프트로 미디어를 생성할 수 있도록 지원합니다.
다른 이름 rendobar/mcp, mcp, @rendobar/mcp
- 스타
- 1
- Tools
- 9
- 다운로드, 30일
- —
- 최신 버전
- 1.13.0
- 마지막 커밋
- 2026년 11월 15일
- 라이선스
- MIT
Rendobar MCP란?
Rendobar은(는) MCP server입니다. 서버리스 인프라를 사용하여 AI agent가 비디오, 오디오, 이미지를 변환하고 텍스트 프롬프트로 미디어를 생성할 수 있도록 지원합니다. 9개 도구를 제공합니다. 예: upload_file, list_job_types, submit_job.
프로젝트 README에서 생성된 요약
Rendobar MCP server 정보
Rendobar는 AI agent가 비디오, 오디오, 이미지를 조작할 수 있는 서버리스 미디어 프로세싱 인프라를 제공합니다. stdio를 통해 로컬에서 실행되는 이 MCP server는 agent가 컴퓨터의 파일에 직접 접근하고, 이를 클라우드에 업로드하며, FFmpeg와 같은 로컬 소프트웨어 없이도 복잡한 변환을 수행할 수 있게 합니다. 이 server는 미디어 워크플로우를 자동화하려는 Claude Desktop, Cursor, Cline, Zed 등의 클라이언트를 사용하는 개발자를 위해 설계되었습니다.
사용자는 사용자 정의 FFmpeg 명령 실행, 특정 크기로 파일 압축, diffusion model을 사용한 텍스트 프롬프트 기반 이미지 생성 등 광범위한 작업을 수행할 수 있습니다. 또한 작업 관리, 계정 잔액 확인, 연결된 스토리지 버킷과의 상호작용을 위한 도구를 포함합니다. 실시간 레지스트리를 사용하므로 server 업데이트 없이도 사용 가능한 작업 유형이 확장될 수 있습니다. 이 로컬 버전을 사용하려면 환경 변수를 통해 Rendobar API key를 제공해야 합니다.
활용 사례
- 1복잡한 FFmpeg 명령 실행agent가 표준 명령 구문을 사용하여 로컬 파일에 특정 오디오 필터나 비디오 설정을 적용할 수 있습니다.
- 2미디어를 특정 크기로 압축이메일 전송을 위한 엄격한 용량 제한에 맞게 비디오 파일 크기를 줄이도록 AI에게 지시할 수 있습니다.
- 3텍스트로 이미지 생성개발자가 agent에게 텍스트 설명을 기반으로 고해상도 타이틀 카드나 시각적 에셋을 생성하도록 요청할 수 있습니다.
- 4클라우드 스토리지 에셋 관리AI agent가 연결된 스토리지 버킷 내의 파일을 탐색하고, 프로세싱 작업을 위해 해당 파일의 고유 URI를 사용할 수 있습니다.
프로젝트의 README를 바탕으로 작성되었습니다. 모든 활용 사례는 해당 내용의 인용문과 대조하여 확인합니다.
Rendobar MCP 설치 방법
형식 확인: 2026년 11월 10일Cursor에 추가Goose에 추가Claude Code에 Rendobar MCP 설치
$ claude mcp add --env 'RENDOBAR_API_KEY=<YOUR_RENDOBAR_API_KEY>' mcp -- npx -y @rendobar/mcpCursor에 Rendobar MCP 설치
~/.cursor/mcp.json
{
"mcpServers": {
"mcp": {
"command": "npx",
"args": [
"-y",
"@rendobar/mcp"
],
"env": {
"RENDOBAR_API_KEY": "<YOUR_RENDOBAR_API_KEY>"
}
}
}
}VS Code에 Rendobar MCP 설치
.vscode/mcp.json
{
"servers": {
"mcp": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@rendobar/mcp"
],
"env": {
"RENDOBAR_API_KEY": "<YOUR_RENDOBAR_API_KEY>"
}
}
}
}VS Code CLI에 Rendobar MCP 설치
$ code --add-mcp '{"name":"mcp","type":"stdio","command":"npx","args":["-y","@rendobar/mcp"],"env":{"RENDOBAR_API_KEY":"<YOUR_RENDOBAR_API_KEY>"}}'Claude Desktop에 Rendobar MCP 설치
claude_desktop_config.json
{
"mcpServers": {
"mcp": {
"command": "npx",
"args": [
"-y",
"@rendobar/mcp"
],
"env": {
"RENDOBAR_API_KEY": "<YOUR_RENDOBAR_API_KEY>"
}
}
}
}Codex에 Rendobar MCP 설치
$ codex mcp add mcp --env 'RENDOBAR_API_KEY=<YOUR_RENDOBAR_API_KEY>' -- npx -y @rendobar/mcpCodex config.toml에 Rendobar MCP 설치
~/.codex/config.toml
[mcp_servers.mcp] command = "npx" args = ["-y", "@rendobar/mcp"] [mcp_servers.mcp.env] RENDOBAR_API_KEY = "<YOUR_RENDOBAR_API_KEY>"
Gemini CLI에 Rendobar MCP 설치
$ gemini mcp add -s user -e 'RENDOBAR_API_KEY=<YOUR_RENDOBAR_API_KEY>' mcp npx -- -y @rendobar/mcpGemini settings.json에 Rendobar MCP 설치
~/.gemini/settings.json
{
"mcpServers": {
"mcp": {
"command": "npx",
"args": [
"-y",
"@rendobar/mcp"
],
"env": {
"RENDOBAR_API_KEY": "<YOUR_RENDOBAR_API_KEY>"
}
}
}
}Rendobar MCP 도구 9
README에서 감지됨upload_filelist_job_typessubmit_jobget_joblist_jobscancel_jobget_accountlist_storagelist_storage_files
| upload_file | — | |
| list_job_types | — | |
| submit_job | — | |
| get_job | — | |
| list_jobs | — | |
| cancel_job | — | |
| get_account | — | |
| list_storage | — | |
| list_storage_files | — |
구성
RENDOBAR_API_KEY비밀Rendobar API key (starts with 'rb_'). Get one at https://app.rendobar.com/settings/api-keys. The server starts without it so tools can be listed, but tool calls require it.
DO_NOT_TRACK
| 이름 | 설명 | 유형 |
|---|---|---|
| RENDOBAR_API_KEY | Rendobar API key (starts with 'rb_'). Get one at https://app.rendobar.com/settings/api-keys. The server starts without it so tools can be listed, but tool calls require it. | 비밀 |
| DO_NOT_TRACK | — |
자동 검사
2026년 11월 12일에 실행됨전체 보고서 →자동 검사를 통과했습니다. 이는 보안 감사가 아닙니다. 코드를 직접 읽고 서버에 필요한 최소한의 권한만 부여하십시오. 검사 방식
- 소스 저장소 연결 및 접근 가능통과
- 오픈 소스 라이선스 (OSI)통과
- 최근 1년 내 커밋 또는 릴리스통과
- 패키지 이름이 인기 패키지와 유사하지 않음통과
- 원격 엔드포인트가 HTTPS 사용통과
- 파괴적인 도구에 라벨 표시됨통과
- 모델에 대한 숨겨진 지침 없음통과
- 패키지 및 해당 종속성에 중요한 보안 권고 없음통과
README
GitHub에서 보기@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.
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.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.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 MB
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.
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.png
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?
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.
@rendobar/mcp (this package) |
Hosted (api.rendobar.com/mcp) |
|
|---|---|---|
| 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/mcp
Local, 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/mcp
Already 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_file |
Upload a local file. Returns a URL to use in submit_job. |
list_job_types |
Every active job type, read live. Call this first. |
submit_job |
Submit a job of any type. |
get_job |
Status and result. Pass wait: true to long-poll for ~50s. |
list_jobs |
Recent jobs. |
cancel_job |
Cancel a waiting, dispatched or running job. |
get_account |
Balance, plan limits, active job count. |
list_storage |
Buckets connected on the Storage page, for storage:// inputs and destinations. |
list_storage_files |
Folders and files in a connected bucket, each with its storage:// URI. |
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=0
Troubleshooting
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
Rendobar MCP 질문
Rendobar MCP를 Claude Code에 추가하려면 어떻게 하나요?
터미널에서 claude mcp add --env 'RENDOBAR_API_KEY=<YOUR_RENDOBAR_API_KEY>' mcp -- npx -y @rendobar/mcp를 실행합니다. 모든 프로젝트에서 사용할 수 있게 하려면 --scope user를 추가합니다.
Rendobar MCP를 Cursor에 추가하려면 어떻게 하나요?
~/.cursor/mcp.json를 열고 mcpServers 아래에 서버를 추가합니다. 위 설치 섹션에 표시된 Cursor 구성을 사용합니다.
Rendobar MCP는 어떤 도구를 제공하나요?
9개 도구를 제공합니다. 예: upload_file, list_job_types, submit_job, get_job, list_jobs.
Rendobar로 기존 미디어를 어떻게 처리할 수 있나요?
비디오, 오디오, 이미지에 FFmpeg 명령을 실행하거나, 파일을 목표 크기로 압축하고, 자막을 삽입하거나, JSON 타임라인을 사용하여 비디오를 합성할 수 있습니다.
이 server로 새로운 미디어를 생성할 수 있나요?
네, 호스팅된 diffusion model을 사용하여 텍스트 프롬프트로부터 이미지를 생성하고, 텍스트 명령으로 기존 이미지를 편집하거나, 이미지 해상도를 높일 수 있습니다.
현재 사용 가능한 작업 유형은 어떻게 확인하나요?
server는 호출 시마다 레지스트리에서 현재 세트를 실시간으로 읽어오는 list_job_types 도구를 제공합니다.
FFmpeg와 같은 로컬 소프트웨어를 설치해야 하나요?
아니요, 모든 프로세싱은 Rendobar 인프라에서 수행되므로 로컬 머신에 별도로 설치할 필요가 없습니다.