How to Use the ContentGroove MCP in Cline

Q: Does Cline support direct video uploads through ContentGroove?

Yes, Cline calls createdirectupload to get a signed URL and then handles the HTTP PUT request to upload your video file directly to ContentGroove.

Q: How does Cline keep track of long-running video jobs?

Cline runs background loops checking getmediastatus and pauses its tasks until the ContentGroove video processing completes.

Command Cline to build custom video dashboards and extract ContentGroove highlights directly in VS Code.

See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

MCP Servers - Free for Subscribers

Connect ContentGroove MCP to Cline

Create your Vinkius account to connect ContentGroove to Cline and route execution through our secure gateway. The platform manages server hosting, runtime updates, and security layers. Configuration requires no manual server provisioning.

GDPR Free for Subscribers

Setup ContentGroove with Cline

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Cline builds video apps with live clips

Tell Cline to build a custom ContentGroove video gallery component in your VS Code React app. The agent calls `list_all_clips` to grab your latest ContentGroove highlights and writes the Cline React code to render them. It doesn't just mock the data; Cline integrates actual video URLs by calling `get_clip_details` to populate your media player. You get a working, production-ready ContentGroove video dashboard inside Cline without writing a line of boilerplate.

Autonomous media ingestion in VS Code

When you need to import fresh footage, Cline uses `create_media_from_url` to register the web video with ContentGroove. Cline writes a small script inside VS Code to monitor the process, querying `get_media_status` until the job completes. Once processed, Cline updates your local JSON database with the new ContentGroove assets using `get_media_clips`. Cline manages the whole video lifecycle from raw URL to local project state inside your workspace.

Direct video staging via MCP Server

Cline handles local video files by generating secure, temporary ContentGroove upload endpoints with `create_direct_upload`. Cline then stages the video file payload and pushes it up to the cloud directly from VS Code. After uploading, Cline uses `get_media_details` to check if the ContentGroove project specs match your local configuration. Your Cline workspace stays perfectly aligned with your cloud ContentGroove assets.

Setup guide

Set up ContentGroove MCP in Cline

Prerequisites

VS Code with Cline extension installed
Active Vinkius subscription with a valid endpoint token

1

Open Cline MCP settings

Click the Cline icon in the VS Code sidebar to open the Cline panel. Then click the MCP Servers icon (server stack) at the top-right corner of the panel.
2

Add a remote server

Click "Remote Servers" at the top, then click "Add Remote MCP". In the Name field, type contentgroove-mcp. In the URL field, paste your Vinkius endpoint: https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp. Get your token from cloud.vinkius.com.
3

Enable the server

After saving, the server appears in the Cline MCP panel. Toggle the switch to enable it. The status indicator turns green when the connection is live.
4

Start using tools

Return to the Cline chat and ask: "Check my latest ContentGroove refund status." Cline will discover the available tools and request your approval before invoking each one — giving you full control over every action.

Cline MCP Settings

{
  "mcpServers": {
    "contentgroove-mcp": {
      "url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    }
  }
}

Get your connection token →

Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by ContentGroove. 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.

Why Choose Vinkius

Vinkius connects your tools to AI with real-time monitoring and automatic cost savings — all from one dashboard.

Connect ContentGroove now

Real-time monitoring

Live

visibility into every interaction

Connect your favorite tools to your AI and see exactly what's happening — every request, every response, in real time.

Built-in savings

60%

lower AI costs

Vinkius compresses data between your apps and your AI automatically. Lower bills every month — no configuration required.

Single dashboard

One

place for every integration

Every tool your AI connects to, managed from a single screen. One account, complete control.

Common questions about ContentGroove MCP in Cline

Open the Cline sidebar, click the MCP Servers icon, and paste the ContentGroove connection URL in the Remote Servers tab.

Yes, Cline uses this MCP Server to inspect your ContentGroove video library, then writes the integration code based on the actual JSON structure returned by the tool.

Yes, Cline calls `create_direct_upload` to get a signed URL and then handles the HTTP PUT request to upload your video file directly to ContentGroove.

Cline runs background loops checking `get_media_status` and pauses its tasks until the ContentGroove video processing completes.

Your video files, metadata, and generated clips are transmitted via encrypted HTTPS directly to the ContentGroove API endpoint. Cline runs this integration in an isolated container that never stores your access tokens or file links on disk.

Use it with your favorite AI tools

Connect this server to Cursor, Claude, VS Code, and more.

OpenAI Agents SDK sdk-python

Google ADK sdk-python

Pydantic AI sdk-python

Vercel AI SDK sdk-typescript