Skip to main content

Documentation Index

Fetch the complete documentation index at: https://rendobar.com/docs/llms.txt

Use this file to discover all available pages before exploring further.

Browser and mobile clients can’t run a local stdio MCP server. Use the remote HTTP server at https://api.rendobar.com/mcp instead. Job submission and status polling work the same as local; local file uploads require an extra step. If you’re on a desktop with Claude Desktop, Cursor, Cline, Windsurf, Zed, VS Code, Claude Code, or Continue — install the local server instead. It’s a better fit.

​
Connect

In claude.ai, open Settings → Connectors → Add custom connector:
  • Name: Rendobar
  • URL: https://api.rendobar.com/mcp
  • Authentication: Bearer token
  • Token: your rb_live_... API key
Save. Start a new chat — the agent has access to Rendobar tools.

​
Tools

Same six job-related tools as the local server, plus upload_media instead of upload_file. Full schemas: Tools reference.

​
Local file uploads

The remote server can’t read your laptop. When an agent calls upload_media, the response is a curl command for you to run: 
curl -X POST \
  -H "Authorization: Bearer rb_live_..." \
  -H "Content-Type: video/mp4" \
  --data-binary @./video.mp4 \
  "https://api.rendobar.com/uploads?filename=video.mp4"
The response contains a downloadUrl. Paste that back into the chat. The agent uses it as a submit_job input. For agents to upload files in a single tool call, install the local server on the same machine where the files live.

​
Limits

Rate limits, file-size caps, and credit consumption are identical to REST and to the local MCP. They are per-organization, not per-tool.

​
See also