Tldv for AI agents
tl;dv records and transcribes video meetings, used by teams that want searchable notes and highlights from calls without watching the whole recording back. Connect it once through Arc0, and your agent, or Claude, ChatGPT and Cursor, can use it through one MCP endpoint, limited to what each user approved.
What agents do in Tldv.
Get a meeting's transcript
Pull the full transcript of a recorded meeting as a read-only reference.
Get meeting highlights
Read the auto-generated highlights from a call to summarize key moments.
Download a meeting recording
Retrieve the recorded video file for a specific meeting.
7 Tldv actions, graded by risk.
Every Tldv action is tagged read, write or destructive, so one policy covers the whole app and new actions inherit the right default.
read
6Look things up. Allowed by default.
- tldv.get_meetingGet Meeting
- tldv.list_meetingsList Meetings
- tldv.get_meeting_highlightsGet Meeting Highlights
- tldv.get_meeting_transcriptGet Meeting Transcript
- tldv.check_healthCheck API Health
- tldv.download_meeting_recordingDownload Meeting Recording
write
1Create and change things. Allow, or ask the user first.
- tldv.import_meetingImport Meeting
destructive
0Delete, cancel or archive. Ask first, or deny outright.
- No destructive actions.
Tldv in three steps.
- 01Your users connect TldvThey add their Tldv api key on Arc0 Connect, under your brand. It goes straight into the vault.
- 02You set the rulesReads run, and writes like “import Meeting” can wait for the user to approve.
- 03Any agent can actYour agent calls Tldv through the Arc0 SDK or MCP, and so can Claude, ChatGPT and Cursor. Every call lands on the audit log.
await arc0.policies.set('tldv', { read: 'allow', write: 'ask', // import_meeting destructive: 'deny', }) # Claude Code: the same connection, one URL $ claude mcp add --transport http arc0 \ https://mcp.arc0.ai/u/u_8f2
How Tldv connects.
Users add their Tldv api key on Arc0 Connect. It is encrypted in the vault, never shown to the model, and each user can rotate or revoke it at any time.
The same Tldv connection serves your agent over MCP and your own backend over REST and the proxy, so a user connects once. How Arc0 handles credentials →
- AUTH
- API key
- CREDENTIALS
- Per-tenant encrypted vault
- MODEL SEES
- Results only, never credentials
- AUDIT LOG
- Every call, on every plan
Use Tldv from any agent.
ClaudeChatGPTCursor
Codex
VS CodeOpenAI Agents SDKClaude Agent SDK
Vercel AI SDK
Mastra
LangGraph
Tldv and Arc0, answered.
Can I use Tldv with Claude, ChatGPT or Cursor?
Yes. Connect Tldv to Arc0 once, then add your Arc0 MCP URL to Claude, ChatGPT, Cursor, Claude Code or any other remote-MCP client. Each assistant only gets the Tldv actions you allow.
How do users connect Tldv?
Users add their Tldv api key on Arc0 Connect. It is encrypted in the vault, never shown to the model, and each user can rotate or revoke it at any time.
Which Tldv actions can my agent take?
7 in total: 6 read, 1 write and 0 destructive, such as “import Meeting”. Your policies decide which of them each agent may call.
Can I make my agent read-only in Tldv?
Yes. Allow read actions and deny writes in the Tldv policy. Your agent can still look things up, and any write it attempts is blocked and logged.
Can my own backend call Tldv too?
Yes. The same Tldv connection is available over REST and through the Arc0 proxy, so your product and your agent share one connection per user.
Plug Tldv into your agent.
Your users connect Tldv once, under your brand. Your agent gets 7 actions behind your policies, with every call on the record.
Free to build · MCP + REST · Audit log on every plan