Bring Meeting Transcription
to Cursor
Learn how to connect tl;dv to Cursor 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 Cursor?
Cursor's Agent mode turns tl;dv into an in-editor superpower. Ask Cursor to generate code using live data from tl;dv and it fetches, processes, and writes. all in a single agentic loop. 12 tools appear alongside file editing and terminal access, creating a unified development environment grounded in real-time information.
- —
Agent mode turns Cursor into an autonomous coding assistant that can read files, run commands, and call MCP tools without switching context
- —
Cursor's Composer feature can generate entire files using real-time data fetched through MCP. no copy-pasting from external dashboards
- —
MCP tools appear alongside built-in tools like file reading and terminal access, creating a unified agentic environment
- —
VS Code extension compatibility means your existing workflow, keybindings, and extensions all work alongside MCP tools
tl;dv in Cursor
tl;dv and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect tl;dv to Cursor 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 Cursor
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 Cursor 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 Cursor
Every tool call from Cursor 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.
What is Agent mode and why does it matter for MCP?
Agent mode is Cursor's autonomous execution mode where the AI can perform multi-step tasks: reading files, editing code, running terminal commands, and calling MCP tools. Without Agent mode, Cursor operates in a simpler ask-and-answer mode that doesn't support tool calling. Always ensure you're in Agent mode when working with MCP servers.
Where does Cursor store MCP configuration?
Cursor looks for MCP server configurations in a mcp.json file. You can configure servers at the project level (.cursor/mcp.json in your project root) or globally (~/.cursor/mcp.json). Project-level configs take precedence.
Can Cursor use MCP tools in inline edits?
No. MCP tools are only available in Agent mode through the chat panel. Inline completions and Tab suggestions do not trigger MCP tool calls. This is by design. tool calls require user visibility and approval.
How do I verify MCP tools are loaded?
Open Settings → Features → MCP and look for your server name. A green indicator means the server is connected. You can also check Agent mode's available tools by clicking the tools dropdown in the chat panel.
Tools not appearing in Cursor
Ensure you are in Agent mode (not Ask mode). MCP tools only work in Agent mode.
Server shows as disconnected
Check Settings → Features → MCP and verify the server status. Try clicking the refresh button.