4,000+ servers built on vurb.ts
Vinkius
CrewAIFramework
Vidyard MCP Server

Bring Video Hosting
to CrewAI

Learn how to connect Vidyard to CrewAI and start using 10 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.

MCP Inspector GDPR Free for Subscribers
Attach Video To PlayerCreate Empty PlayerDelete Video AssetDelete Video PlayerGet Player DetailsGet Video DetailsGet Video Source FilesList Video PlayersList VideosUpdate Player Name

Compatible with every major AI agent and IDE

ClaudeClaude
ChatGPTChatGPT
CursorCursor
GeminiGemini
WindsurfWindsurf
VS CodeVS Code
JetBrainsJetBrains
VercelVercel
+ other MCP clients
Vidyard

What is the Vidyard MCP Server?

Connect your Vidyard account to any AI agent and manage your business video library through natural conversation.

What you can do

  • Video Library — List all video assets stored in your Vidyard dashboard and retrieve unique video IDs
  • Metadata & Details — Get technical metadata for any video including length, encoding status, and descriptions
  • Player Management — Create, update, and manage video players (facades) to customize how your content is embedded
  • Video Organization — Attach videos to specific players and organize your content for different marketing or sales needs
  • Direct Stream Access — Retrieve direct stream URLs and raw MP4 download links for various video qualities (480p, 720p, etc.)
  • Asset Management — Rename players or permanently delete video assets and player containers from your dashboard

How it works

  1. Subscribe to this server
  2. Enter your Vidyard API Token
  3. Start managing your video library through Claude, Cursor, or any MCP-compatible client

No more manual browsing through complex video dashboards. Your AI agent becomes your video asset manager.

Who is this for?

  • Marketing Teams — organize video players for different campaigns and retrieve embed codes through chat
  • Sales Professionals — quickly find and share specific videos or product demos with prospects
  • Content Creators — manage video assets, check encoding status, and retrieve source files for distribution
  • Support Engineers — find relevant tutorial videos and manage player branding for knowledge base articles

Built-in capabilities (10)

attach_video_to_player

Requires both player ID and video ID. Adds a video asset into a specific player container

create_empty_player

Creates a new, empty video player container

delete_video_asset

This action is irreversible. Permanently deletes a video asset from Vidyard

delete_video_player

Note that the original video assets are not deleted. Permanently deletes a video player

get_player_details

Retrieves details for a specific video player

get_video_details

Retrieves technical metadata for a specific video asset

get_video_source_files

Retrieves direct stream URLs for various video qualities (480p, 720p, etc.)

list_video_players

Lists all configured video players (facades) in the account

list_videos

Lists all video assets stored in the Vidyard dashboard

update_player_name

Updates the display name or title of an existing player

Why CrewAI?

When paired with CrewAI, Vidyard becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call Vidyard tools autonomously, one agent queries data, another analyzes results, a third compiles reports, all orchestrated through Vinkius with zero configuration overhead.

  • Multi-agent collaboration lets you decompose complex workflows into specialized roles, one agent researches, another analyzes, a third generates reports, each with access to MCP tools

  • CrewAI's native MCP integration requires zero adapter code: pass Vinkius Edge URL directly in the mcps parameter and agents auto-discover every available tool at runtime

  • Built-in task delegation and shared memory mean agents can pass context between steps without manual state management, enabling multi-hop reasoning across tool calls

  • Sequential and hierarchical crew patterns map naturally to real-world workflows: enumerate subdomains → analyze DNS history → check WHOIS records → compile findings into actionable reports

See it in action

Vidyard in CrewAI

AI AgentVinkius
High Security·Kill Switch·Plug and Play
Why Vinkius

Vidyard and 4,000+ other MCP servers. One platform. One governance layer.

Teams that connect Vidyard to CrewAI through Vinkius don't need to source, host, or maintain individual MCP servers. Every tool call runs inside a hardened runtime with credential isolation, DLP, and a signed audit chain.

4,000+MCP Servers ready
<40msCold start
60%Token savings
Raw MCP
Vinkius
Server catalogFind and host yourself4,000+ managed
InfrastructureSelf-hostedSandboxed V8 isolates
Credential handlingPlaintext in configVault + runtime injection
Data loss preventionNoneConfigurable DLP policies
Kill switchNoneGlobal instant shutdown
Financial circuit breakersNonePer-server limits + alerts
Audit trailNoneEd25519 signed logs
SIEM log streamingNoneSplunk, Datadog, Webhook
HoneytokensNoneCanary alerts on leak
Custom domainsNot applicableDNS challenge verified
GDPR complianceManual effortAutomated purge + export
Enterprise Security

Why teams choose Vinkius for Vidyard in CrewAI

The Vidyard MCP Server runs on Vinkius-managed infrastructure inside AWS — a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts. All 10 tools execute in hardened sandboxes optimized for native MCP execution.

Your AI agents in CrewAI only access the data you authorize, with DLP that blocks sensitive information from ever reaching the model, kill switch for instant shutdown, and up to 60% token savings. Enterprise-grade infrastructure, zero maintenance.

Vidyard
Fully ManagedVinkius Servers
60%Token savings
High SecurityEnterprise-grade
IAMAccess control
EU AI ActCompliant
DLPData protection
V8 IsolateSandboxed
Ed25519Audit chain
<40msKill switch
Stream every event to Splunk, Datadog, or your own webhook in real-time

* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure

The Vinkius Advantage

How Vinkius secures Vidyard for CrewAI

Every tool call from CrewAI to the Vidyard MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.

< 40msCold start
Ed25519Signed audit chain
60%Token savings
FAQ

Frequently asked questions

01

Can I get direct download links for my videos through the agent?

Yes. The get_video_source_files tool allows your agent to retrieve direct MP4 download links and stream URLs for different qualities (like 720p or 1080p), making it easy to share raw files or use them in other applications.

02

How do I add a video to a specific player?

Use the attach_video_to_player tool. You'll need to provide the player_id and the video_id. Your agent can help you find these IDs by listing your players and videos first.

03

Can I create new video players through conversation?

Absolutely. The create_empty_player tool lets you provision a new player container with a descriptive name. Once created, you can attach videos to it and manage its settings directly through your agent.

04

How does CrewAI discover and connect to MCP tools?

CrewAI connects to MCP servers lazily. when the crew starts, each agent resolves its MCP URLs and fetches the tool catalog via the standard tools/list method. This means tools are always fresh and reflect the server's current capabilities. No tool schemas need to be hardcoded.

05

Can different agents in the same crew use different MCP servers?

Yes. Each agent has its own mcps list, so you can assign specific servers to specific roles. For example, a reconnaissance agent might use a domain intelligence server while an analysis agent uses a vulnerability database server.

06

What happens when an MCP tool call fails during a crew run?

CrewAI wraps tool failures as context for the agent. The LLM receives the error message and can decide to retry with different parameters, fall back to a different tool, or mark the task as partially complete. This resilience is critical for production workflows.

07

Can CrewAI agents call multiple MCP tools in parallel?

CrewAI agents execute tool calls sequentially within a single reasoning step. However, you can run multiple agents in parallel using process=Process.parallel, each calling different MCP tools concurrently. This is ideal for workflows where separate data sources need to be queried simultaneously.

08

Can I run CrewAI crews on a schedule (cron)?

Yes. CrewAI crews are standard Python scripts, so you can invoke them via cron, Airflow, Celery, or any task scheduler. The crew.kickoff() method runs synchronously by default, making it straightforward to integrate into existing pipelines.

09

MCP tools not discovered

Ensure the Edge URL is correct. CrewAI connects lazily when the crew starts. check console output.

10

Agent not using tools

Make the task description specific. Instead of "do something", say "Use the available tools to list contacts".

11

Timeout errors

CrewAI has a 10s connection timeout by default. Ensure your network can reach the Edge URL.

12

Rate limiting or 429 errors

Vinkius enforces per-token rate limits. Check your subscription tier and request quota in the dashboard. Upgrade if you need higher throughput.

Explore More MCP Servers

View all →