An astronaut overseeing a futuristic data hub

Connect Rendi to ChatGPT, Claude and Gemini

Set it up once and it works in ChatGPT, Claude, Cursor, and any other client you love. It all runs safely in the background, so you can relax and focus on what really matters. Execute complex FFmpeg commands through simple natural language.

Ask AI about this Connector

Developed, maintained, and hosted by Vinkius.

MCP VERIFIED · PRODUCTION READY · VINKIUS GUARANTEED

Waiting for input…

Works with modern AI clients that support MCP, including ChatGPT, Claude, Cursor, and more.

ChatGPTClaudeCursorPerplexityGeminiMicrosoft CopilotRaycastMeta AI

Your AI does the work. We keep it safe and sound.

No other AI tool gives you this. Your workflow runs in the client you already love, your account stays protected, and you decide what the agent can and cannot do. It is the whole reason to make the switch.

Each Connector lives inside our infrastructure, the same place where your workflow runs. The three things below are already part of it, working quietly in the background so you never have to think about them. Nothing to add, nothing to set up, nothing to worry about.

A futuristic MCP client docking bay
V8 Isolate01

Each Connector runs inside its own sealed environment.

Each Connector runs inside its own sealed V8 runtime — no access to your files, your system, or other servers. A Connector never sees past its own request.

Kill Switch02

One switch stops every agent. Instantly.

One action deactivates every Connector, revokes every token, and ends every session at once. AI Governance keeps the record.

FinOps per User03

Spending limits that pause instead of surprise.

Every user keeps their own connections and credentials, isolated from everyone else. Anything that would cross your spending limit is held for your approval, not billed.

Three controls, built into the layer your AI connects through.

Curated set · 11 capabilities

We ship only the actions that matter.

Capability set01 / 03

01-04

4 capabilities in this set.

Part of 11 available through Rendi.

  1. 01

    Delete file

    Removes a specific file from your Rendi storage.

  2. 02

    Get command status

    Checks the progress of an FFmpeg command and retrieves the final storage URL once it finishes.

  3. 03

    Get file details

    Retrieves specific data regarding a file currently in Rendi storage.

  4. 04

    Get file info

    Fetches technical metadata and specific details for a single file.

Capability set02 / 03

05-08

4 capabilities in this set.

Part of 11 available through Rendi.

  1. 05

    List commands

    Shows a list of all FFmpeg commands you have submitted.

  2. 06

    List files

    Displays all files currently held in your Rendi storage.

  3. 07

    Convert video to audio

    Extracts the audio track from a video file.

  4. 08

    Ffprobe

    Runs an FFprobe analysis to extract deep technical metadata from a media file.

Capability set03 / 03

09-11

3 capabilities in this set.

Part of 11 available through Rendi.

  1. 09

    Generate thumbnail

    Creates a still image thumbnail from a video file.

  2. 10

    Run chained ffmpeg commands

    Executes a sequence of multiple FFmpeg commands in a single request.

  3. 11

    Run ffmpeg command

    Triggers a single FFmpeg command to run in the cloud and returns a command ID to track it.

Real work

What teams actually run

01

Rapid Prototyping

Test specific FFmpeg encoding parameters through your AI client before deploying them to a production pipeline.

02

Asset Validation

Check if a video file meets specific resolution or codec requirements before it enters your CMS.

03

Automated Previews

Have your agent generate thumbnails and audio extracts for large batches of video files.

04

Format Conversion

Convert heavy video files into web-friendly formats like WebM using simple chat prompts.

Automate a task

Put Rendi to work on one thing.

Step-by-step automations your AI runs through this Connector: the workflow, the prompts to start with, and the exact capabilities behind each move.

One connector, every AI

Rendi works with the most popular AI clients.

These are the most popular clients, each with a step-by-step guide: one link, set up once, with governance and visibility built in. And because everything runs on the MCP standard, the same connection also works in any other compatible client — nothing to rebuild.

Building your own app? The connector is yours to use.

You don't need a client to put Rendi to work: the same hosted connection plugs into your own applications and agent code, with the same governance on every request. Build with it, chat with it — one connection for both.

Observed, not estimated

934ms average. Fast in production.

Rendi is checked daily against the live service.

Daily averagePeak 1266ms
Oct 3Today
Fastest day
744ms
Slowest day
1266ms
14-day trend
Slowing+36%

Connect your client

One URL. Every client.

Activate the Connector, copy your link, and paste it into the client you already use. 11 capabilities arrive ready to run.

Preview access · not provider authentication

The vk_preview_* token belongs to Vinkius preview infrastructure. It lets Claude discover and display the capabilities of Rendi, so you can see the experience inside your AI.

It does not authenticate your account with Rendi. Actions requiring credentials or live account data may not run until you activate the Connector and authorize the service.

Rendi Connector

You're all set. Choose your MCP client and follow the setup instructions.

Connector linkhttps://edge.vinkius.com/vk_preview_yLT1nhPB29SIqqpsgoNP1Ev6sJDTpO5q0f2OjGk5/mcp

Claude Desktop

Follow the steps below to connect in seconds.

  1. 1In Claude Desktop, open Settings → Connectors.
  2. 2Click “Add custom connector” and paste the connector link above as the remote MCP server URL.
  3. 3Click Add and start a new chat — Rendi capabilities are ready to use.
Configuration · claude_desktop_config.jsonCopy
{
  "mcpServers": {
    "rendi-mcp": {
      "url": "https://edge.vinkius.com/vk_preview_yLT1nhPB29SIqqpsgoNP1Ev6sJDTpO5q0f2OjGk5/mcp"
    }
  }
}
  • Claude
  • ChatGPT
  • Cursor
  • VS Code
  • Windsurf
  • Claude Code
  • JetBrains
  • Cline

Step-by-step instructions for each client are in the guide. How to connect

Guided setup for Claude? Set up Rendi in Claude and other AIs

See all the AI clients this connector works with ↑

Who it's for

Built for the work Rendi owners hand off.

This MCP is built for technical professionals who need to manipulate media without managing their own transcoding infrastructure.

  • 01

    Content Engineers

    They hand off repetitive FFmpeg parameter testing and file monitoring to the agent.

  • 02

    Video Producers

    They use the AI to quickly generate previews and technical analysis of assets.

  • 03

    Operations Teams

    They delegate media metadata retrieval and processing health checks to the agent.

FAQ

Questions Rendi owners ask.

  • 01

    Do I need to install FFmpeg on my computer?

    No. All FFmpeg commands are executed in the Rendi cloud, so your local machine stays untouched.

  • 02

    How do I get my processed files?

    Once a command finishes, the MCP provides a storage URL where you can access the output files.

  • 03

    Can I run multiple commands at once?

    Yes. You can use the chained command capability to execute a sequence of operations in one go.

  • 04

    What kind of media info can I get?

    You can retrieve detailed technical metadata including codecs, bitrates, resolutions, and stream details using ffprobe.

  • 05

    Where are my files stored?

    Files are held in Rendi's cloud storage, and you can manage them using the list and delete capabilities.

  • 06

    Can my AI automatically convert a video file into an MP3 audio track using Rendi?

    Yes! Use the run_ffmpeg_command capability with the conversion parameters (e.g., 'ffmpeg -i input.mp4 output.mp3'). Your agent will execute the command in the cloud and return the result URL instantly.

  • 07

    How do I find my Rendi API Key?

    Log in to your Rendi dashboard at rendi.dev, and your unique secret API key will be displayed on the main page or under account settings.

  • 08

    What is the format for chained FFmpeg commands?

    Use the run_chained_ffmpeg_commands capability and provide an array of strings, where each string is a valid FFmpeg command. Rendi will execute them sequentially in a single processing job.

Connect Rendi to Claude, Cursor, ChatGPT & more