Bring Video Hosting
to CrewAI
Learn how to connect api.video to CrewAI and start using 9 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.
What is the api.video MCP Server?
Connect your api.video account to any AI agent and take full control of your professional video hosting infrastructure and automated media workflows through natural conversation.
What you can do
- Video Orchestration — List and manage your entire high-fidelity video library programmatically, or create new video objects to prepare for uploads in real-time
- Asset Intelligence — Retrieve detailed high-fidelity status and direct asset URLs for players, thumbnails, and navigation markers (chapters) directly through your agent
- Deep Analytics Tracking — Monitor performance metrics like total plays and impressions using high-fidelity aggregation tools to coordinate your content strategy
- Multilingual Captions — Access and manage subtitle tracks across multiple languages to maintain a perfectly coordinated global viewer experience
- Infrastructure Monitoring — Access your directory of custom player themes and store-level metadata directly through your agent for instant operational reporting
How it works
1. Subscribe to this server
2. Retrieve your Production API Key from your api.video dashboard (API Keys section)
3. Start orchestrating your video content and performance from Claude, Cursor, or any MCP client
No more manual toggling between video dashboards or digging through complex embed settings. Your AI acts as your dedicated video engineer and media architect.
Who is this for?
- Content Creators — instantly retrieve player links and update video metadata using natural language commands
- Product Managers — monitor video performance and track feature walkthrough engagement without leaving your creative workspace
- Developers — integrate high-speed cloud-based video management into custom application workflows through simple AI queries
Built-in capabilities (9)
Set title and description here. Initialize a new video
video. Permanently delete a video
Retrieve performance metrics
Get metadata for a video
List custom player themes
List captions for a video
List chapters for a video
Supports filtering by title or tags. List your api.video videos
Modify video metadata
Why CrewAI?
When paired with CrewAI, api.video becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call api.video 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
mcpsparameter 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
api.video in CrewAI
api.video and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect api.video 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.
Raw MCP | Vinkius | |
|---|---|---|
| Server catalog | Find and host yourself | 3,400+ managed |
| Infrastructure | Self-hosted | Sandboxed V8 isolates |
| Credential handling | Plaintext in config | Vault + runtime injection |
| Data loss prevention | None | Configurable DLP policies |
| Kill switch | None | Global instant shutdown |
| Financial circuit breakers | None | Per-server limits + alerts |
| Audit trail | None | Ed25519 signed logs |
| SIEM log streaming | None | Splunk, Datadog, Webhook |
| Honeytokens | None | Canary alerts on leak |
| Custom domains | Not applicable | DNS challenge verified |
| GDPR compliance | Manual effort | Automated purge + export |
Why teams choose Vinkius for api.video in CrewAI
The api.video 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 9 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.
* 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
How Vinkius secures
api.video for CrewAI
Every tool call from CrewAI to the api.video MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
How do I find my api.video API Key?
Log in to your account, navigate to the API Keys section in your dashboard, and copy your unique Production API Key.
Can I get a direct player link via AI?
Yes! The get_video_details tool retrieves high-fidelity asset URLs including the player, mp4 source, and thumbnails for any specific video.
How do I check video analytics?
Use the get_video_analytics tool and specify the metric (e.g., 'play') and aggregation (e.g., 'total') to retrieve real-time performance data.
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.
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.
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.
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.
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.
MCP tools not discovered
Ensure the Edge URL is correct. CrewAI connects lazily when the crew starts. check console output.
Agent not using tools
Make the task description specific. Instead of "do something", say "Use the available tools to list contacts".
Timeout errors
CrewAI has a 10s connection timeout by default. Ensure your network can reach the Edge URL.
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.