Skip to main content
Rendobar is MCP-native, meaning AI agents can interact with the API directly through the Model Context Protocol. All 15 MCP tools map 1:1 with the REST API endpoints, so anything you can do with the REST API, an agent can do via MCP.
MCP access is available on Starter plans and above.

​
What is MCP?

The Model Context Protocol (MCP) is a standard for AI agents to interact with external tools and services. Instead of writing custom API client code, an agent discovers available tools and calls them directly using structured inputs and outputs. Rendobar exposes its full API surface as MCP tools, allowing AI agents to submit jobs, check status, manage API keys, and query usage without manual integration code.

​
Connecting to Rendobar

Point your MCP client to the Rendobar MCP endpoint: 
https://api.rendobar.com/mcp

​
Claude Desktop / Claude Code

Add to your MCP configuration: 
{
  "mcpServers": {
    "rendobar": {
      "url": "https://api.rendobar.com/mcp",
      "headers": {
        "Authorization": "Bearer rb_live_YOUR_KEY"
      }
    }
  }
}

​
Custom agents

Any MCP-compatible agent can connect using the SSE transport protocol with an API key in the Authorization header.

​
Available tools

Rendobar provides 15 MCP tools:
ToolDescriptionREST equivalent
submit_jobSubmit a video processing jobPOST /jobs
submit_batchSubmit multiple jobs as a batchPOST /jobs/batch
get_jobGet job status and detailsGET /jobs/:id
get_job_resultGet the output URL and metadataGET /jobs/:id/result
list_jobsList jobs with filters and paginationGET /jobs
cancel_jobCancel a running or waiting jobPOST /jobs/:id/cancel
list_job_typesList all available job typesGET /job-types
get_job_schemaGet the Zod schema for a job typeGET /job-types/:type/schema
get_balanceGet current usage balanceGET /billing/balance
get_usageGet usage stats for a date rangeGET /billing/usage
get_orgGet organization detailsGET /orgs/:id
list_membersList organization membersGET /orgs/:id/members
list_api_keysList API keys for the orgGET /api-keys
create_api_keyCreate a new API keyPOST /api-keys
revoke_api_keyRevoke an existing API keyDELETE /api-keys/:id

​
Authentication

MCP agents authenticate with Rendobar using OAuth, handled by the Better Auth MCP plugin. The flow:
1

Initiate

The agent initiates an OAuth handshake with the Rendobar MCP server.
2

Authorize

The user authorizes the agent in their browser (one-time).
3

Token

The agent receives an access token scoped to the user’s organization.
4

Operate

All subsequent MCP tool calls use this token automatically.
This means agents authenticate once and then operate autonomously within the permissions of the authorized organization.

​
Example: Agent submits a watermark job

Agent: I'll add a watermark to the video.

1. Call submit_job({
     type: "watermark.add",
     inputs: {
       source: "https://example.com/video.mp4",
       watermark: "https://cdn.rendobar.com/assets/brand/logo-full.png"
     },
     params: {
       position: "bottom-right",
       scale: 0.15,
       opacity: 0.8
     }
   })
   -> { jobId: "job_x1y2z3", status: "dispatched" }

2. Call get_job({ jobId: "job_x1y2z3" })
   -> { status: "complete", price: 3000000000 }

3. Call get_job_result({ jobId: "job_x1y2z3" })
   -> { url: "https://r2...", meta: { durationMs: 127500 } }
The agent can also check credits before submitting, list available job types to discover capabilities, and handle errors from failed jobs.

​
Tool discovery

Agents discover available tools by connecting to the Rendobar MCP server endpoint. The server returns tool definitions with:
  • Tool name and description
  • Input schema (Zod-based, auto-generated from the API route schemas)
  • Output schema
This allows agents to understand what each tool does and what parameters it accepts without any prior knowledge of the Rendobar API.

​
Supported agents

Any MCP-compatible agent can use Rendobar, including:
  • Claude (Anthropic) with MCP tool use
  • Custom agents built with the MCP SDK
  • Automation platforms with MCP support

​
Rate limits and billing

MCP tool calls are subject to the same rate limits and credit checks as REST API calls. Each submit_job tool call deducts credits from the organization’s balance, and rate limits are enforced per organization.

Authentication

API key and session auth details

Job Types

All 23 supported operations

Webhooks

Push-based status updates

Credits

Billing and usage tracking