tl;dv MCP server
6 operations2 webhooks
Meeting intelligence with tl;dv - list and read recorded meetings, pull transcripts and AI notes, import a recording from a URL, and search folders.
Try tl;dv with your agent
Connect tl;dv, then paste this into Claude, ChatGPT or Cursor. For ideas from other apps, see the use cases.
Using Corsair, show me what you can do in tl;dv on my account, then run one read-only example and show me the result.
tl;dv tools and triggers
Tools are what your agent can do in tl;dv through Corsair's MCP server. Triggers are the tl;dv events a routine can start from.
Meetings
- GetRead-only
Get one meeting by id, including the phone number and metadata an import attached
meetings.get
- ImportWrite
Import a meeting from a public media URL, which starts a processing job and spends recording minutes
meetings.import
- ListRead-only
List meetings with paging, date bounds and folder or type filters
meetings.list
- NotesRead-only
Get the AI notes and topics generated for one meeting
meetings.notes
- TranscriptRead-only
Get the transcript of one meeting, sentence by sentence
meetings.transcript
Folders
- ListRead-only
Search the folders a user can see, with their meeting ids
folders.list
Connect tl;dv to Claude, ChatGPT or Cursor
- 1
Connect tl;dv in Corsair
Add your tl;dv API key once in Corsair. Corsair stores the credential encrypted and makes the tl;dv API calls for your agent, so it never goes into a prompt or a config file. Connect tl;dv
If your link lets the agent add apps, you can skip this: it gives you a sign-in link the first time it needs tl;dv. On a ChatGPT personal plan, connect tl;dv here first.
- 2
Add Corsair's MCP server to your agent
Every client uses the same address:
https://mcp.corsair.dev/mcpOpen Customize → Connectors → Add custom connector, paste the address, then select Connect.Add a custom MCP server with the address and choose OAuth. Personal plans get read tools only.Add to CursorOr add this to~/.cursor/mcp.json. Cursor opens Corsair to sign in the first time it connects.{ "mcpServers": { "corsair": { "url": "https://mcp.corsair.dev/mcp" } } }Run this, then run/mcpin Claude Code to sign in.claude mcp add --transport http corsair https://mcp.corsair.dev/mcpCodex, Gemini CLI, VS Code, Zed and other clients with OAuth sign-in work the same way. Clients without it, such as GitHub Copilot's coding agent, use a link's own address and an API key. Setup for every client
- 3
Sign in and choose what needs your approval
Your client opens Corsair to sign in. Pick a link: the apps your agent can use and a mode that decides what it may do without asking. None of tl;dv's operations are destructive, so in the default Cautious mode they all run right away. Strict mode asks before each of its 1 write, and Read mode allows reads only.
FAQ
Install corsair and @corsair-dev/tldv, add the tl;dv plugin, and connect with an API key. Then call methods like corsair.tldv.api.folders.list() from your app. Corsair verifies webhooks, and keeps each tenant isolated.
Yes. tl;dv requires an API key from your tl;dv account or developer dashboard. Create credentials with access that matches what you automate, then paste them into Corsair or connect through managed auth in Hub.
Yes. One Corsair client can hit tl;dv, GitHub, Notion, Stripe, and the rest. Trigger tl;dv from a webhook, push updates to Slack, or chain actions across plugins. Same tenant context across integrations, plain TypeScript.
Teams use Corsair for meeting intelligence with tl;dv - list and read recorded meetings, pull transcripts and AI notes, import a recording from a URL, and search folders. Common builds include sync jobs, admin tooling, and agents that call tl;dv APIs from your backend. Webhook handlers react to tl;dv events and fan out to Slack, email, or other plugins in the same tenant.
The SDK is open source. Self-host and you pay Corsair nothing for the integration layer. Hub bills for hosted auth and execution, not per tl;dv API call. Hub has a generous free tier. For hobby projects you can probably run the whole thing on free. Paid plans start to matter with more tenants or heavier traffic.
We maintain @corsair-dev/tldv in the open repo. When tl;dv ships API changes, upgrade the package. Your call sites stay typed. You should not need to rewrite the integration layer each time.
No. Corsair does not read your tl;dv data or hold individual access credentials. Credentials stay in your database. API calls run on your instance. We do not store tl;dv data on your behalf.
Yes. Add https://mcp.corsair.dev/mcp as a custom connector or MCP server in Claude, ChatGPT, Cursor, VS Code, Claude Code, Codex or any client that supports remote MCP servers with OAuth sign-in, then sign in to Corsair. On ChatGPT personal plans, custom servers currently get read tools only.
Yes. Put tl;dv on a link in Strict mode and every write waits for your approval, while destructive actions are refused. None of the tl;dv operations are destructive, so the default Cautious mode runs them all without asking. You can change a link's mode at hub.corsair.dev/me.