Bring Webrtc
to CrewAI
Learn how to connect Daily.co to CrewAI and start using 50 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 Daily.co MCP Server?
Connect your Daily.co account to any AI agent to orchestrate real-time video and audio communication workflows through natural language.
What you can do
- Room Management — Create, list, update, and delete video rooms. Configure privacy settings (public/private) and custom properties on the fly.
- Participant Control — Monitor real-time presence to see who is in a call and eject participants or ban them when necessary.
- Domain Configuration — Retrieve and set top-level domain settings for your Daily infrastructure.
- Session Data — Sync and retrieve custom session data across all participants to maintain state during meetings.
- App Messaging — Send data payloads to participants within a room to trigger client-side actions or notifications.
How it works
- Subscribe to this server
- Enter your Daily API Key
- Start managing your video infrastructure from Claude, Cursor, or any MCP-compatible client
Your AI acts as a virtual operator, capable of spinning up meeting rooms for support tickets or auditing active sessions without you ever touching a dashboard.
Who is this for?
- Developers — quickly test room configurations and manage WebRTC infrastructure directly from the code editor.
- Support & Ops Teams — monitor active meeting presence and manage participant access for webinars or private consultations.
- Product Managers — automate the creation of unique meeting links for specific project workflows or client calls.
Built-in capabilities (50)
Purchase a specific or random number
Submit a batch processor job
Create a meeting token
Create a new room
Create a webhook
Delete a batch job
Delete a recording reference
Delete a room
Delete a webhook
Kick participants from a room
Get batch job status
Get download links for finished jobs
Retrieve domain configuration
List all active participants on the domain
Retrieve detailed call logs and metrics
Get details for a specific session
List participants in a session
Get recording information
Generate a time-limited S3 download link
Retrieve a specific room
Get active participants in a room
Retrieve meeting session data
Get specific webhook info
Search for numbers by areacode or region
List all batch jobs
List meeting sessions
List numbers owned by your domain
Supports pagination. List cloud recordings
Supports pagination. List rooms
List webhooks
Release a number
Send data to participants
Send DTMF tones to a session
Set domain configuration
Sync data to all participants
Call a sipUri or phoneNumber
Start RTMP/HLS streaming
Start a recording
Start real-time transcription
End a dial-out session
Stop streaming
Stop an active recording
Stop transcription
Update layout or endpoints for streaming
Update participant permissions
Update layout of an active recording
Modify room privacy or configuration
Update participants being transcribed
Update or re-activate a failed webhook
Validate a meeting token
Why CrewAI?
When paired with CrewAI, Daily.co becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call Daily.co 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
Daily.co in CrewAI
Daily.co and 4,000+ other MCP servers. One platform. One governance layer.
Teams that connect Daily.co 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 Daily.co in CrewAI
The Daily.co 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 50 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
Daily.co for CrewAI
Every tool call from CrewAI to the Daily.co MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
Can I see exactly who is currently inside a video room?
Yes. Use the get_room_presence tool with the room name. It returns a snapshot of all active participants currently connected to that specific session.
How do I create a private room that requires a token to join?
You can use the create_room tool and set the privacy parameter to 'private'. You can also pass additional configuration in the properties JSON field.
Is it possible to remove a disruptive participant from a call?
Yes. The eject_participants tool allows you to kick specific users by their IDs. You can also set the ban flag to true to prevent them from re-entering the room.
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 →
Ecomail
10 toolsEquip your AI agent to manage email campaigns, track subscribers, and monitor marketing automation via the Ecomail API.
Temu Seller Hub
12 toolsAutomate cross-border e-commerce ops via Temu — manage orders, track fulfillment, sync inventory, and process returns natively from any AI agent.
WHO GHO
3 toolsAccess 2,200+ health indicators from 194 countries — life expectancy, disease prevalence, mortality rates, immunization coverage, and environmental health data from the World Health Organization.
Password Manager Export Analyzer
1 toolsAnalyze Bitwarden, LastPass, or 1Password CSV exports for weak and duplicate passwords — without EVER sending real passwords to the AI.