Changelog
New

Upload files to Rendobar's MCP server from any device

The hosted MCP server can now receive file uploads directly, from a shell agent's presigned PUT to a link you finish on your phone, alongside a job discovery tool and output chaining between jobs.

API MCP

You can now edit a video from your phone by talking to an agent. Ask for the edit, tap the link it sends back, pick the clip from your camera roll, and the finished file arrives in the same conversation. Nothing is installed and no file ever touches the agent’s machine, because there is no machine.

Terminal window
claude mcp add --transport http rendobar https://api.rendobar.com/mcp

On claude.ai it is Settings, Connectors, Add custom connector, and the same URL.

Two ways in, decided by what the client can reach

Call upload_media and it opens an upload session. An agent with shell access gets a presigned URL back immediately and PUTs the bytes itself, then calls complete_upload. An agent with no filesystem access, a phone or a plain chat conversation, gets a link instead: app.rendobar.com/u/<token>. Hand that link to the person you’re talking to and they finish the upload from their own device, then get_upload({ wait: true }) returns as soon as the file lands. Either way you end up with a ready asset whose URL is the next submit_job input.

The hosted server has no disk of its own, which is why this took a session protocol rather than a file parameter. It used to send any client without shell access to the local @rendobar/mcp package instead.

The rest of the tool set

Three more tools round out the set:

  • list_job_types reads the job registry fresh on every call: every active job type, what it’s for, what it chains with, and an example payload. Call it once at the start of a task instead of guessing at a type string.
  • Output chaining. Any submit_job input can be { job: "job_..." } instead of a URL, so a multi-step edit references a prior job’s output directly. No download and re-upload in between.
  • get_job waits and previews. Pass wait: true to block up to 45 seconds until a job finishes instead of polling, and a completed video job can come back with an inline poster frame alongside the result, when one exists.

Ten tools total now: submit_job, get_job, list_jobs, probe_media, get_account, cancel_job, upload_media, complete_upload, get_upload, and list_job_types. API keys still work everywhere, and @rendobar/mcp remains the fastest path when an agent has real filesystem access and wants to skip the presign round trip. Full reference at the MCP docs.

Connecting without an API key is covered in connect the MCP server with OAuth.

Share