MCP + ReelSDK $0.02 per compute minute, first $0.50 free
Give Claude, Cursor and Codex 6 video tools over MCP
The reelsdk-mcp package gives Claude Code, Claude Desktop, Cursor and Codex 6 ReelSDK video tools, with raw ffmpeg 8.1 at $0.02 per compute minute and captions at $0.03 per output minute. It is a local stdio server for captions, slideshows, shorts, raw ffmpeg, job status and uploads, added with one npx line.
- Local files upload on their own, results land in ./reelsdk-output
- Every result carries the local path and the URL
- Open source under the MIT license
bash: line 1: ffmpeg: command not found
Source: Bash exit status
The same job as one call to ReelSDK
{
"mcpServers": {
"reelsdk": {
"command": "npx",
"args": ["-y", "github:bitgate/reelsdk-mcp"],
"env": { "REELSDK_KEY": "rsdk_live_..." }
}
}
}
Why ffmpeg breaks here
Why agents call ReelSDK instead of a local ffmpeg
An agent that edits video through its shell needs ffmpeg on the machine, and where it's missing bash prints ffmpeg: command not found and exits with 127. Long encodes also run into the agent's command limits: Claude Code stops a Bash command after 2 min by default. reelsdk-mcp gives the agent 6 tools that run on ReelSDK instead: add_captions, make_slideshow, make_short, run_ffmpeg with ffmpeg 8.1, get_job and upload_file.
The server runs on your machine over stdio. It uploads local files up to 100 MiB, waits up to 50 s for each job by default, saves the outputs to ./reelsdk-output and returns each file's local path, URL and size. A job that takes longer comes back as running, and the agent calls get_job until it finishes. Raw ffmpeg costs $0.02 per compute minute, captions and slideshows $0.03 per output minute.
Where each client keeps the server
| Client | Where the server goes | Good to know |
|---|---|---|
| Claude Code | claude mcp add, or .mcp.json with --scope project | Warns past 10,000 tokens of tool output, caps it at 25,000 |
| Claude Desktop | claude_desktop_config.json, the mcpServers block above | On macOS in ~/Library/Application Support/Claude/ |
| Cursor | .cursor/mcp.json in the project, or ~/.cursor/mcp.json | The same mcpServers block |
| Codex | codex mcp add, or ~/.codex/config.toml | 10 s to start and 60 s per tool call by default |
| ChatGPT web | Remote MCP servers through plugins | Run this stdio server from Codex instead |
MCP limits from reelsdk-mcp on GitHub, checked November 2026.
Set it up
A key, one config entry, a request
The server needs Node 20 or newer and git, and starts from GitHub with npx; there is nothing else to install.
Get a key
Create a ReelSDK account and copy an API key; keys start with
rsdk_live_. The server reads it fromREELSDK_KEY.Add the server to your client
Claude Desktop and Cursor take the
mcpServersblock from the fix above. Claude Code and Codex add the server with one command each.Claude Code claude mcp add reelsdk --env REELSDK_KEY=rsdk_live_... -- npx -y github:bitgate/reelsdk-mcpCodex codex mcp add reelsdk --env REELSDK_KEY=rsdk_live_... -- npx -y github:bitgate/reelsdk-mcpAsk for an edit
Ask for something like "cut an 8 s vertical teaser from in.mp4". The agent calls
run_ffmpegwith named inputs, ffmpeg args and the outputs to save, like the call below. The server cut this 8-second 720x1280 teaser and saved it to./reelsdk-output.add_captionsuploads a local clip the same way and returns a captioned video, a transcript and srt, vtt and ass captions, in about 17 seconds.tools/call run_ffmpegTry it { "method": "tools/call", "params": { "name": "run_ffmpeg", "arguments": { "inputs": { "in.mp4": "https://api.reelsdk.com/f/lib/in/seo-int/nasa-vision.mp4" }, "args": [ "-ss", "2", "-t", "8", "-i", "in.mp4", "-vf", "crop=ih*9/16:ih,scale=720:1280,fade=t=out:st=7:d=1", "-af", "afade=t=out:st=7:d=1", "-c:v", "libx264", "-crf", "23", "-c:a", "aac", "-movflags", "+faststart", "teaser.mp4" ], "outputs": ["teaser.mp4"] } } }
FAQ
Video on MCP, answered
Does ReelSDK have an MCP server?
Yes. reelsdk-mcp is an open-source local stdio server under the MIT license with 6 tools: add_captions, make_slideshow, make_short, run_ffmpeg, get_job and upload_file. It installs with npx -y github:bitgate/reelsdk-mcp, needs Node 20 or newer and git, and reads your key from REELSDK_KEY.
Does the ReelSDK MCP server work with ChatGPT?
ChatGPT on the web uses remote MCP servers through plugins, and reelsdk-mcp is a local stdio server, so run it from Codex with codex mcp add reelsdk --env REELSDK_KEY=rsdk_live_... -- npx -y github:bitgate/reelsdk-mcp. Codex gives a tool call 60 s by default and the server waits 50 s, so a longer job comes back as running, with its id for get_job.
Where do the rendered files go?
The server saves them to a reelsdk-output folder in the client's workspace root, or in the folder it starts in, unless REELSDK_OUTPUT_DIR points elsewhere. Each result lists the file's local path, URL and size, and the URLs work for 7 days.
What happens with a long render?
Each tool waits up to 50 s by default, and REELSDK_WAIT_S raises that to at most 300. A job still running after that comes back with its job id, and the agent calls get_job until the files are saved. A ReelSDK job runs for 10 min at most.
Can an agent use the ReelSDK API without MCP?
Yes. api.reelsdk.com serves llms.txt and openapi.json. The render tools map to POST /v1/captions, /v1/slideshow, /v1/shorts and /v1/ffmpeg with a Bearer key, and get_job maps to GET /v1/jobs/{id}.
The same fix on other platforms
All integrationsReady to build?
Ship video from your app today
Your first $0.50 is free, and one key covers every endpoint.
