RenderMe MCP for AI. Control your entire video production pipeline from chat.

Q: How do I check if my video rendering job succeeded using getrenderjobstatus?

You provide a Job ID, and getrenderjobstatus tells you the current state. It'll report 'complete' or 'failed,' giving you immediate visibility into the result.

Q: Do I need to run listvideotemplates before creating a job?

Yeah, you should. Running listvideotemplates gives you all the active deployment IDs and details for templates, which prevents you from running a render using an outdated or non-existent ID.

Q: What if I need to know my monthly usage limit? Can getaccountrenderstats do that?

Yes. getaccountrenderstats pulls your total renders, API calls, and storage used for the month, letting you monitor quota consumption at a glance.

Q: How does RenderMe help me manage my assets? Does listuploadedassets work with it?

It lets you see everything. listuploadedassets lists all media files in the project, and listassetfolders shows how those files are organized for easy retrieval.

Q: Before I create a job, how can I check if my connection to RenderMe is working?

Run checkapihealth right away. This validates the API connectivity and confirms your agent has working credentials before you trigger expensive render jobs.

Q: How do I verify what external systems will receive notifications when a video job finishes?

Use listconfiguredwebhooks. This shows all active hooks, verifying that RenderMe will notify your other services—like Slack or databases—when the rendering completes.

Q: I need to know what dynamic variables a specific video template requires; should I use gettemplatedetails?

Yes, run gettemplatedetails with the deployment ID. This retrieves crucial metadata, like required placeholders (e.g., Name or Date), so your AI client can prepare inputs correctly.

Q: How do I confirm which user account is initiating the rendering process?

Call getcurrentuser to retrieve the authenticated profile details. This confirms the session context for your agent and is key for auditing or billing purposes.

Claude

ChatGPT

Cursor

Gemini

Windsurf

VS Code

JetBrains

Vercel

See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

Connect to your AI in seconds.

RenderMe connects your video production workflow to your AI client. You use this server to manage automated rendering jobs, track media assets, and control deployments for professional videos using natural conversation.

Trigger a render job, check stats, or list available templates—all without leaving the chat.

What your AI can do

Check api health

Verifies if your connection to the RenderMe API is working correctly.

Get template details

Fetches technical details for one specific video template, including its required dynamic variables.

Get render job status

Checks and reports the current status (queued, rendering, failed) of a specific job ID.

+ 9 more capabilities included

Trigger Video Rendering

Initiates a new video rendering job by specifying a template ID and providing dynamic data like text or colors.

Check Job Statuses

Retrieves the current state of any render job, telling you if it's queued, rendering, or finished.

Manage Templates and Assets

Lists all available video templates (deployments) and organizes your source material by listing asset folders and uploaded media.

Monitor Account Health

Checks the overall connection status of the RenderMe API or retrieves usage statistics for your account this month.

Ask an AI about this

Included with Plan

Waiting for input…

AI Agent

RenderMe MCP Server: 12 Tools for Video Ops

Use these tools to programmatically list templates, check job statuses, run renders, and monitor all your video assets.

Make your AI actually useful.

Add this MCP to Claude, Cursor, or Windsurf and your AI stops guessing. It gets real tools to look things up, take action, and handle the stuff you keep doing by hand.

Start using RenderMe on Vinkius

Check Api Health

Verifies if your connection to the RenderMe API is working correctly.

Get Template Details

Fetches technical details for one specific video template, including its required...

Get Render Job Status

Checks and reports the current status (queued, rendering, failed) of a specific job...

Get Current User

Pulls basic profile information for the authenticated user making the request.

Get Account Render Stats

Retrieves usage data, including total renders and API call counts for the month.

List Uploaded Assets

Displays all images and media files currently uploaded to your RenderMe project for use in templates.

List Video Templates

Lists all available, active video templates (deployments) you can use for rendering content.

List Asset Folders

Displays a list of the organizational folders set up to store your media projects...

List Recent Render Jobs

Shows a list of the last few video rendering jobs that were run on the account.

List Video Projects

Shows a list of every video project that has been set up on the account.

List Configured Webhooks

Lists all active webhooks connected to your RenderMe account for external...

Create Video Render Job

Sends a command to start rendering a new video project using an available template.

Security and governance baked right in.

Pick your AI client below to get set up. Just create a Vinkius account, subscribe, and you're instantly up and running. We handle the entire backend infrastructure, delivering out-of-the-box support for HTTPS Streamable, SSE, and OAuth2—zero messy routing required.

Claude AI

Open Claude Settings

Go to claude.ai, click your profile icon, then navigate to Customize → Connectors.

Add Custom Connector

Click the "+" button and select Add custom connector. Paste your Vinkius endpoint URL:

https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp

Replace [YOUR_TOKEN_HERE] with your token from cloud.vinkius.com. For OAuth-protected servers, expand Advanced settings to add credentials.

Start a conversation

Open a new chat. The RenderMe integration is available immediately — no restart needed.

Antigravity

Configure Agent Environment

Open your Antigravity agent's workspace configuration or mcp-servers.json file.

Bind the Endpoint

Add the Vinkius endpoint URL to your agent's MCP connections list:

"mcp_servers": {
  "renderme": {
    "serverUrl": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
  }
}

Provide your secure token in place of [YOUR_TOKEN_HERE] to ensure your agent requests are authenticated.

Execute

Start your Antigravity session. The agent will autonomously discover and utilize the RenderMe tools with full Vinkius guardrails applied.

VS Code Copilot

⚡

One-Click Install (Recommended)

In your Vinkius Dashboard, simply click the Add to VS Code button for this server. We'll automatically configure your local workspace.

Or configure manually

Open MCP Settings

Open VS Code, press Ctrl/Cmd + Shift + P, and search for GitHub Copilot: MCP Servers.

Add Server Config

Add the Vinkius endpoint configuration to your mcp-servers.json file:

"renderme": {
  "url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
}

Ensure you replace [YOUR_TOKEN_HERE] with your token from cloud.vinkius.com.

LangChain

Install Dependencies

Install the LangChain MCP adapters for your environment:

pip install langchain-mcp-adapters

Connect the Server

Use the SSEClient in LangChain to connect to the Vinkius managed endpoint:

from langchain_mcp_adapters.client import SSEClient

# Connect to Vinkius
client = SSEClient(url="https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp")
tools = client.get_tools()

CrewAI

Define the Tool

Load the Vinkius MCP tools into your CrewAI agents:

from crewai import Agent
from mcp_crewai import MCPTool

# Connect securely to Vinkius
vinkius_tools = MCPTool(url="https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp")

# Assign to Agent
researcher = Agent(
    role='Data Researcher',
    tools=vinkius_tools.get_all()
)

Execute Task

Run your CrewAI process. The agent will autonomously route tasks to the Vinkius managed server.

Choose How to Get Started

Build a custom MCP for your own tools, or connect a ready-made integration from our catalog.

Build Your Own

Turn any API into an MCP. Import a spec, define Agent Skills, or deploy with MCPFusion.

Import from OpenAPI, Swagger, or YAML specs
Create Agent Skills with progressive disclosure
Deploy to edge with MCPFusion framework
Built in DLP, auth, and compliance on every call
Real time usage dashboard and cost metering
Publish to catalog or keep private

Start building

Make Your AI Do More

Start with RenderMe, then connect any of our 5,000+ other servers whenever your AI needs more. One click, no limits.

Use this MCP plus 5,000+ others, all in one place
Add new capabilities to your AI anytime you want
Every connection is secured and compliant automatically
Track usage and costs across all your servers
Works with Claude, ChatGPT, Cursor, and more
New servers added to the catalog every week

Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by RenderMe. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.

VINKIUS INFRASTRUCTURE

Cloud Hosted

Managed infra

V8 Isolated

Sandboxed per request

Zero-Trust Proxy

No stored credentials

DLP Enforced

Policy on every call

GDPR Compliant

EU data residency

Token Compression

~60% cost reduction

Your data is protected. See how we built it.

Works with Claude, ChatGPT, Cursor, and more

The Model Context Protocol standardizes how applications expose capabilities to LLMs. Instead of operating in isolation, your AI gains direct access to external platforms, live data, and real-world actions through secure, standardized connections.

This connection provides 12 powerful capabilities that interface natively with Claude, ChatGPT, Cursor, and other compatible AI platforms. No middleware. No custom integration required.

Media management shouldn't require jumping between five different tabs.

Right now, setting up a batch of videos means logging into the rendering platform, finding the correct template ID in one tab, checking asset availability in a second tab, manually filling out variables in a third, and then switching to a fourth dashboard just to see if the job failed. It's clicking, copying, and hoping.

With this MCP server, you type it all into your chat: 'Render 50 personalized videos using Template X for Name Y.' The agent runs `create_video_render_job`, handles the variables, and gets you a status update. You stay in one place the whole time.

RenderMe MCP Server: Run video ops straight from your chat.

You no longer have to manually submit job IDs or guess if an asset is uploaded. The agent runs `list_video_templates` and `list_uploaded_assets` first, giving you the structured data needed for success before you even ask it to render.

It's not just a better dashboard; it’s a workflow change. Your AI client becomes the dedicated media coordinator that manages the entire process—from concept check to final output.

Support 24/7 support@vinkius.com ↗

Security Vinkius Trust Center ↗

SLA Service Level Agreement ↗

Report Listing Send Report ↗

What your AI can actually do with this

Your agent connects RenderMe (re.video) to your workflow, giving you full control over automated video production. You use this server to manage rendering jobs, track assets, and handle deployments just by talking to it.

Triggering Video Rendering:
You start a new render using create_video_render_job. Just give your agent a template ID and the dynamic data—like specific text or colors—and it kicks off the job. You can also check what variables a template needs by calling get_template_details for a specific deployment.

Checking Job Statuses:
When you send that render command, you need to know where it stands. Use get_render_job_status with a job ID to see if the video is queued, actively rendering, or if it failed. If you want an overview, run list_recent_render_jobs to check out history. To monitor your account's overall usage this month, grab stats using get_account_render_stats.

You can also verify that your connection to the RenderMe API is actually working by running check_api_health.

Managing Templates and Assets:
Before you render anything, you gotta know what you're working with. To see all the available video templates you can use for a job, call list_video_templates. If you need to organize your source material, run list_asset_folders to see all the project folders set up in RenderMe. You can also check which specific images and media files are uploaded and ready to go by using list_uploaded_assets.

To get a rundown of every video project that's been built out on the account, use list_video_projects. Finally, if you need external systems notified when things change, list all active webhooks connected through list_configured_webhooks.

Account Information and Context:
Your agent can pull basic profile info for the user making the request by calling get_current_user. You'll also want to know what other data is floating around. Use list_video_templates to see all available deployments, which you might then check with get_template_details if you need specific variable requirements.

This whole setup lets your agent handle complex media workflows—from starting the job to tracking every piece of source material—without forcing you to jump between a dashboard and this chat window. It's everything in one place.

Built · Hosted · Managed by Vinkius RenderMe MCP Server - Automate Video Rendering

Server ID 019dd14c-c6ac-7251-8059-d57142637116

Vinkius Inspector

Compliance Grade A+

Score 100/100

Report View Report ↗

Who is this actually for?

Social Media Managers who hate context switching. Marketing Ops staff tired of manually updating campaign assets across multiple tools. Operations Engineers needing a single source of truth to monitor cloud media health and usage limits.

Marketing Coordinator

Uses this to automatically generate personalized video ads for email campaigns or social posts, feeding dynamic data like names into templates.

Social Media Manager

Checks the status of multiple content drafts using list_recent_render_jobs and quickly pulls asset lists to ensure brand consistency before posting.

Operations Engineer

Runs checks like get_account_render_stats to monitor API usage, ensuring the team stays under quota limits without logging into a separate dashboard.

What Changes When You Connect

Check usage limits and performance stats instantly. Run get_account_render_stats to know exactly where you stand without leaving the conversation window. This prevents unexpected overage charges.

Never guess a template ID again. Use list_video_templates to pull up every active video deployment name and its unique ID, making job creation reliable and fast.

Manage your content source material easily. Run list_uploaded_assets to see every image and piece of media you've stored, ensuring the assets needed for a render are actually there.

Keep track of history without clicking tabs. list_recent_render_jobs gives you an immediate rundown of what was processed minutes ago, making troubleshooting fast.

Pinpoint job progress immediately. If a rendering job is stuck, use get_render_job_status to confirm if it's truly failed or just taking time on the backend.

See it in action

01 01

Batching Personalized Ad Sets

A marketing team needs 50 versions of a testimonial video, each with a different name and date. They prompt their agent: 'Run create_video_render_job for the 'Testimonial v2' template using dynamic fields: {{name}}, {{date}}.' The agent executes the batch render, and they get a link to the finished ZIP archive.

02 02

Pre-Flight Check on Assets

Before kicking off a major campaign, an ops engineer runs list_asset_folders and then list_uploaded_assets. This confirms that all necessary logos, hero images, and background tracks are correctly organized and uploaded before spending money on rendering.

03 03

Debugging a Failed Campaign

A social media manager notices a job failed. They immediately run list_recent_render_jobs to get the ID, then use get_render_job_status with that ID. The result tells them it was a template variable error, saving 15 minutes of manual debugging.

04 04

Auditing Usage Before Year-End

The finance team needs to prove media usage for Q2. They run get_account_render_stats to get total renders and API calls, providing a single data point that was previously buried in three different dashboard sections.

The honest tradeoffs

Guessing the Template ID

Anti-pattern

The user types: 'Render my video using template 1234.' But they don't know if '1234' is correct or even active, so the job fails with a vague error.

The Fix

First, run list_video_templates to see all available deployment IDs. Then, use the exact ID you get back when calling create_video_render_job. That way, you know for sure what you're rendering.

Ignoring Asset Status

Anti-pattern

The user tries to render a video that requires an image ('sunset.jpg'), but they forgot to upload it into the project first.

The Fix

Before running create_video_render_job, run list_uploaded_assets. Check the output for 'sunset.jpg'. If it's missing, you know exactly what source file needs to be added.

Polling on Job Status

Anti-pattern

The user keeps running status checks manually: 'What's the job status?' -> (wait 5 minutes) -> 'Status again?' This wastes API calls and slows down the chat flow.

The Fix

Better yet, check if webhooks are set up using list_configured_webhooks. If they are, let your agent subscribe to updates instead of continuously asking for status.

When It Fits, When It Doesn't

Use this server if you need full API control over a complex media pipeline. This means automation: triggering renders, managing variable inputs (text/colors), and tracking the entire lifecycle from template selection (list_video_templates) to final download link retrieval.

Don't use it if your need is simple asset viewing—just run list_uploaded_assets or list_asset_folders. Also, don't rely on this just for basic file storage; you still need the dedicated media library. You must use RenderMe when you need to move beyond just storing files and actually execute a paid rendering process.

If your workflow involves these three steps—(1) Know what templates exist (list_video_templates), (2) Have source materials ready (list_uploaded_assets), and (3) Trigger the job (create_video_render_job)—then this is your tool.

Questions you might have

How do I check if my video rendering job succeeded using get_render_job_status? +

You provide a Job ID, and get_render_job_status tells you the current state. It'll report 'complete' or 'failed,' giving you immediate visibility into the result.

Do I need to run list_video_templates before creating a job? +

Yeah, you should. Running list_video_templates gives you all the active deployment IDs and details for templates, which prevents you from running a render using an outdated or non-existent ID.

What if I need to know my monthly usage limit? Can get_account_render_stats do that? +

Yes. get_account_render_stats pulls your total renders, API calls, and storage used for the month, letting you monitor quota consumption at a glance.

How does RenderMe help me manage my assets? Does list_uploaded_assets work with it? +

It lets you see everything. list_uploaded_assets lists all media files in the project, and list_asset_folders shows how those files are organized for easy retrieval.

Before I create a job, how can I check if my connection to RenderMe is working? +

Run check_api_health right away. This validates the API connectivity and confirms your agent has working credentials before you trigger expensive render jobs.

How do I verify what external systems will receive notifications when a video job finishes? +

Use list_configured_webhooks. This shows all active hooks, verifying that RenderMe will notify your other services—like Slack or databases—when the rendering completes.

I need to know what dynamic variables a specific video template requires; should I use `get_template_details`? +

Yes, run get_template_details with the deployment ID. This retrieves crucial metadata, like required placeholders (e.g., [Name] or [Date]), so your AI client can prepare inputs correctly.

How do I confirm which user account is initiating the rendering process? +

Call get_current_user to retrieve the authenticated profile details. This confirms the session context for your agent and is key for auditing or billing purposes.

Can my AI automatically find my RenderMe templates? +

Yes! Use the list_deployments tool. Your agent will respond with complete metadata for all your video templates, including their IDs and technical specifications in seconds.

How do I find my RenderMe (re.video) API Key? +

Log in to your RenderMe account at app.re.video, navigate to the Settings or API section, and you will find your unique secret token there.

Connect to your AI in seconds.

Check api health

Get template details

Get render job status

RenderMe MCP Server: 12 Tools for Video Ops

Make your AI actually useful.

Check Api Health

Get Template Details

Get Render Job Status

Get Current User

Get Account Render Stats

List Uploaded Assets

List Video Templates

List Asset Folders

List Recent Render Jobs

List Video Projects

List Configured Webhooks

Create Video Render Job

Security and governance baked right in.

Claude AI

Open Claude Settings

Add Custom Connector

Start a conversation

Claude Code

Open your terminal

Add the MCP Server

Start coding

Cursor

One-Click Install (Recommended)

Open Cursor Settings

Add New Server

Use in Composer

Antigravity

Configure Agent Environment

Bind the Endpoint

Execute

VS Code Copilot

One-Click Install (Recommended)

Open MCP Settings

Add Server Config

Windsurf

One-Click Install (Recommended)

Open Windsurf Settings

Add Server Endpoint

LangChain

Install Dependencies

Connect the Server

CrewAI

Define the Tool

Execute Task

Choose How to Get Started

Build Your Own

Make Your AI Do More

Works with Claude, ChatGPT, Cursor, and more

Media management shouldn't require jumping between five different tabs.

RenderMe MCP Server: Run video ops straight from your chat.

What your AI can actually do with this

Here's how it actually works

Who is this actually for?

What Changes When You Connect

See it in action

Batching Personalized Ad Sets

Pre-Flight Check on Assets

Debugging a Failed Campaign

Auditing Usage Before Year-End

The honest tradeoffs

Guessing the Template ID

Ignoring Asset Status

Polling on Job Status

When It Fits, When It Doesn't

Questions you might have