How to Use the ContentGroove MCP in Windsurf

Q: Does Windsurf support automatic clip downloading from ContentGroove?

Yes, Cascade uses getmediaclips to fetch the direct clip paths from ContentGroove and writes them straight to your Windsurf workspace files.

Q: How do I configure this MCP Server in my editor?

Open your /.codeium/windsurf/mcpconfig.json file and add the ContentGroove server configuration under the mcpServers block.

Feed video links to Windsurf and let Cascade autonomously generate, track, and extract your ContentGroove social clips.

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 Windsurf

Create your Vinkius account to connect ContentGroove to Windsurf 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 Windsurf

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Cascade chains video imports to clips

Give Windsurf a raw YouTube URL and let Cascade handle the entire ContentGroove ingestion pipeline. Cascade initiates the import via `create_media_from_url` and monitors the progress using `get_media_status` without waiting for your next prompt. Once the processing finishes, Windsurf automatically pulls the results using `get_media_clips`. You get a fully polished list of ContentGroove highlight clips ready for your editors inside your Windsurf workspace, all from a single initial command.

Direct file uploads managed by Windsurf

When you have local footage, Cascade grabs a secure ContentGroove upload URL using `create_direct_upload`. The agent prepares the video payload and handles the binary transfer directly within your Windsurf session, avoiding manual browser uploads entirely. After the upload completes, Windsurf tracks the project lifecycle with `get_media_details`. It keeps your Windsurf workspace in sync with your remote ContentGroove video library without any manual reloading.

Automated clip auditing via MCP Server

Let Cascade audit your entire ContentGroove media library by running `list_media` to find unprocessed raw files. The agent then drills down into specific ContentGroove highlights using `get_clip_details` to evaluate their timestamps inside your Windsurf editor. It can even compile a markdown summary of every video asset by calling `list_all_clips` to show your team what's ready in Windsurf. You just watch Cascade piece the ContentGroove video data together inside your Windsurf IDE.

Setup guide

Set up ContentGroove MCP in Windsurf

Prerequisites

Windsurf IDE installed (macOS, Windows, or Linux)
Active Vinkius subscription with a valid endpoint token

1

Open MCP configuration

Click the Cascade assistant icon in the sidebar, then click the hammer icon (🔨) at the top of the panel. Select "Configure" to open ~/.codeium/windsurf/mcp_config.json.
2

Add the ContentGroove MCP

Paste the JSON snippet shown on the right into the mcpServers object. Replace [YOUR_TOKEN_HERE] with your endpoint token from cloud.vinkius.com.
3

Refresh MCPs

Go back to the hammer icon (🔨) in Cascade and click "Refresh". Windsurf will detect the new server. No full restart is needed — the connection is hot-reloaded.
4

Verify in Cascade

Start a new Cascade conversation and ask something like "Show my ContentGroove payment history." If connected, Cascade will call the ContentGroove tools directly. You will see a green dot next to the server name in the MCP panel.

mcp_config.json

{
  "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 Windsurf

Cascade uses this MCP Server to talk directly to the ContentGroove API. When you paste a video URL inside Windsurf, Cascade automatically triggers the background jobs and polls them until your clips are ready.

Cascade can loop through a list of raw video links inside Windsurf, call `create_media_from_url` for each, and track their statuses in parallel via ContentGroove.

Yes, Cascade uses `get_media_clips` to fetch the direct clip paths from ContentGroove and writes them straight to your Windsurf workspace files.

Open your ~/.codeium/windsurf/mcp_config.json file and add the ContentGroove server configuration under the mcpServers block.

Your raw video files and URLs are sent directly to ContentGroove's secure processing servers, never touching Vinkius's runtime. The MCP metadata and video clips are handled inside ephemeral Windsurf sandboxes that discard your project data immediately after execution.

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