Bring Meeting Transcription
to CrewAI
Learn how to connect tl;dv to CrewAI and start using 12 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.
What is the tl;dv MCP Server?
Connect your tl;dv account to any AI agent and simplify how you manage your meeting recordings, transcripts, and AI-generated insights through natural conversation.
What you can do
- Meeting Oversight — List all recorded meetings and retrieve detailed metadata, including participants and duration.
- Transcript Access — Fetch full transcriptions for any meeting to search for specific discussion points.
- AI Insights — Read AI-generated notes, summaries, and key moments (highlights) to quickly understand meeting outcomes.
- External Import — Programmatically import meeting recordings from external URLs for processing.
- Content Retrieval — Get direct download links for video recordings and access recent transcripts instantly.
- Operational Monitoring — Check API connectivity and account status directly from the agent.
How it works
1. Subscribe to this server
2. Enter your tl;dv API Key (found in your account settings)
3. Start managing your meeting knowledge base from Claude, Cursor, or any MCP client
Who is this for?
- Product Managers & Researchers — quickly retrieve meeting summaries and highlights via simple AI queries.
- Sales Teams — verify discussion points and share transcripts directly from the workspace.
- Operations Managers — monitor meeting logs and maintain a central repository of recorded organizational knowledge via the AI assistant.
Built-in capabilities (12)
Check connection
Get meeting info
Check call length
Get key moments
Read AI summaries
List attendees
Read transcription
Get video file URL
Upload recording URL
List latest transcripts
List recent meetings
Verify credentials
Why CrewAI?
When paired with CrewAI, tl;dv becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call tl;dv 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
tl;dv in CrewAI
tl;dv and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect tl;dv 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 tl;dv in CrewAI
The tl;dv 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 12 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
tl;dv for CrewAI
Every tool call from CrewAI to the tl;dv 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 the AI-generated notes for a specific meeting?
Yes! Use the get_meeting_notes tool and provide the Meeting ID. Your agent will retrieve the complete AI summary and key points recorded for that session.
How do I search for a specific discussion point in the transcript?
Run the get_meeting_transcript query with the Meeting ID. The agent will retrieve the full text, allowing you to ask the AI to find or summarize specific parts of the conversation.
Is it possible to list the participants of a meeting via AI?
Absolutely. Use the get_meeting_participants tool and provide the Meeting ID. The agent will return the directory of everyone who attended the recorded session.
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.