Bring Video Campaigns
to CrewAI
Learn how to connect Videco 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.
GDPR Free for SubscribersCompatible with every major AI agent and IDE
Gemini
What is the Videco MCP Server?
Connect your Videco account to any AI agent and manage personalized videos, campaigns, leads, and analytics through natural conversation.
What you can do
- Video Management u2014 Create, list, and review personalized videos from your template library
- Campaign Management u2014 Create and monitor video campaigns with audience targeting and delivery metrics
- Lead Tracking u2014 Access all leads captured from video interactions with engagement scores
- Video Analytics u2014 View detailed metrics including views, watch time, drop-off points, and CTA click rates
- Template-Based Creation u2014 Generate new personalized videos instantly from existing templates
How it works
- Subscribe to this server
- Retrieve your API Key from your Videco account settings
- Start managing video campaigns from Claude, Cursor, or any MCP client
Who is this for?
- Sales Teams u2014 create personalized prospecting videos and track engagement per lead
- Marketing Teams u2014 launch video campaigns and monitor conversion metrics
- Customer Success u2014 send personalized onboarding videos and track completion rates
Built-in capabilities (10)
Verify Videco API connectivity
Create a campaign
Create a personalized video
Get campaign details
Get lead details
Get video details
Get video analytics
List all campaigns
List all leads
List all videos
Why CrewAI?
When paired with CrewAI, Videco becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call Videco 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
Videco in CrewAI
Videco and 4,000+ other MCP servers. One platform. One governance layer.
Teams that connect Videco 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 | 4,000+ 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 Videco in CrewAI
The Videco 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.
* 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
Videco for CrewAI
Every tool call from CrewAI to the Videco 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 create a personalized video via AI?
Use the create_video tool with a name and template ID. The personalized video is generated instantly from your Videco templates.
Can I track video engagement and leads?
Yes. Use get_video_analytics for views, watch time, and CTR, and list_leads to see all captured lead contacts with engagement scores.
How do I create and manage video campaigns?
Use create_campaign with a name and video ID to launch a campaign, then list_campaigns and get_campaign to track performance.
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.
Explore More MCP Servers
View all →
Paystack
10 toolsManage payments via Paystack — list transactions, verify payments, and manage customers directly from any AI agent.
Cohere (AI Platform)
7 toolsPower enterprise AI via Cohere — generate text, perform chat completions, reorder documents, and manage embeddings directly from any AI agent.
São Paulo (Cidade)
11 toolsAccess the official São Paulo Open Data portal — search datasets, query resources via SQL, and explore city organizations and themes.
SurveyMethods
12 toolsOnline survey software and data analysis.