tl;dv logo tldv.io

Live

tl;dv API and MCP server

tl;dv has an API that only reads meetings, transcripts and notes, with no way to clip, note, share or file them. Sign in to tl;dv once in your own Cloud Browser, and your AI agent does the work there for you. The same tools work over MCP for agents and as a REST API for scripts.

Sign up free View as Markdown

Not affiliated with tl;dv.

tl;dv has no API for this. So we run one for you.

tl;dv's own API, a GitHub MCP server and Cotlet compared
What you need tl;dv's APIGitHub MCP serverCotlet
Clips, notes, sharing, folders No No Yes, 13 tools
Acts as you, signed in 24/7 No No Yes, Cloud Browser
Fixed for you when tl;dv changes N/A No Yes, tested every 6h
Runs with your laptop off N/A No Yes, hosted

Checked Oct 17, 2026. Sources: tl;dv Public API docs (v1alpha1) · tl;dv Help: API · tl;dv Help: MCP · tl;dv MCP server (official repository)

Your own Cloud Browser, on 24/7. Sign in once. We keep it connected.

  1. 01Sign in to tl;dv in your own Cloud Browser

  2. 02Connect it for your agents

  3. 03Cotlet keeps it signed in and working

How do I connect tl;dv to Claude, ChatGPT or my code?

AI agents connect over MCP, scripts call the REST API. Both reach the same 13 tools with one API key.

For AI agents: MCP

Add Cotlet to your agent once. tl;dv and every other app you connect show up as its tools.

  • Claude
  • ChatGPT
  • OpenClaw
  • Hermes
  • GrokBot
  • Cursor
  • n8n
  • Any MCP client
  1. 1

    Add Cotlet to your agent

    Claude Code
    claude mcp add --transport http cotlet \
  https://cotlet.dev/mcp/v1 \
  --header "Authorization: Bearer $COTLET_API_KEY"
    Cursor
    {
  "mcpServers": {
    "cotlet": {
      "url": "https://cotlet.dev/mcp/v1",
      "headers": {
        "Authorization": "Bearer ${COTLET_API_KEY}"
      }
    }
  }
}
    Codex
    # ~/.codex/config.toml
[mcp_servers.cotlet]
url = "https://cotlet.dev/mcp/v1"
bearer_token_env_var = "COTLET_API_KEY"

    Paste the snippet for your client. The same server and key serve every app you connect, so you do this once.

For scripts: REST API

Every tool is an endpoint under /api/v1/tldv with its own method and path, such as POST /api/v1/tldv/meetings/{meeting_id}/share, with the same API key. Our open-source repo has ready scripts to start from.

REST API docs

What can the tl;dv API and MCP server do?

13 tools on your own tl;dv account. Agents call them as operations of the MCP tools tldv_read and tldv_write; scripts call each one at its own REST endpoint, with the same inputs and answers.

API reference
tl;dv tools in Cotlet's MCP server and REST API
Tool What it does Access
list_meetings Meetings in your library with title, date, duration, your role and folder, newest first. read
get_meeting One meeting with participants, link, folder and who can open it. read
get_transcript Full transcript of a meeting with speaker and time per line. read
get_meeting_notes AI notes grouped by topic, plus the notes people added by hand, with timestamps. read
list_clips Clips in your Clips library with title, meeting and length, newest first. read
list_folders Your folders with who can open them, version and number of meetings. read
add_note Add a timestamped note to a finished meeting, under your name. write
create_clip Save a segment of a meeting as a clip in your Clips library. write
rename_meeting Change the title of a meeting. write
add_to_folder File a meeting in one of your folders. Needs the Editor or Admin role on the meeting. writeasks first
share_meeting Give people or a whole domain access to a meeting. Needs the Admin or Editor role on the meeting. writeasks first
set_link_access Make a meeting public to anyone with the link, or limit it to the people with access. writeasks first
delete_meeting Permanently delete a recording. It cannot be recovered. writeasks first

Scroll the table for all 13 tools.

Ask in plain words. Your agent does the rest.

All tl;dv use cases

Is it safe to connect tl;dv?

You sign in yourself in your own Cloud Browser, we never save your password, and anything that reaches your readers waits for your OK. The browser profile is encrypted in the EU. Independent scanners grade cotlet.dev A+.

Security overview

How much do the tl;dv API and MCP server cost?

One price for both: a tool call costs the same over MCP or REST. Free 7-day trial with 2,000 credits, no card needed. Then one-time credit packs, no subscription, valid 12 months. Most calls use 25 credits, and your Cloud Browser uses 50 credits a day while tl;dv is enabled for agents, so 20 calls a day come to 550 credits.

See full pricing
Cotlet credit packs: price, credits and calls at 25 credits each
Credits Price, one time Calls at 25 credits Per 1,000 credits
5,000 $29 200 $5.80
15,000 $79 600 $5.27
32,000 $149 1,280 $4.66
60,000 $249 2,400 $4.15

Only successful calls use credits; failed calls and timeouts cost nothing. At a balance of 0 calls pause, never a surprise charge. Authenticate with the Authorization: Bearer header.

Questions

Does tl;dv have an API?

tl;dv has a public REST API (version v1alpha1) and an official hosted MCP server, and both are read-focused (checked 17 Oct 2026). The API lists meetings and reads a meeting, its transcript, its notes and a signed download link; its only writes import or upload new recordings. The MCP server, on tl;dv Pro or higher, searches meetings and reads metadata, transcripts and notes, and its docs say it cannot create, edit, delete or share meetings.

How do I get access?

Sign up free, open tl;dv under Integrations in the console and press Request access. Your free trial starts with your account, no card needed.

Is the MCP server different from the API?

No, only the way in. Cotlet builds each integration as a REST API and puts an MCP server on top, so both have the same 13 tools, the same inputs and answers, one API key and one price. AI agents such as Claude, ChatGPT or Cursor use MCP; scripts, cron jobs and HTTP steps in n8n, Make or Zapier use the REST API.

What is the Cloud Browser?

Your own Chrome that Cotlet runs for you in the EU, around the clock. You open it from the console, sign in to tl;dv yourself and press Enable for agents. Your agent's calls go through it, from its IP with its cookies, so tl;dv sees the browser you signed in with. Password saving is off and the profile is stored encrypted with AES-256-GCM.

Can my agent act without asking me?

Not on anything that reaches other people: add_to_folder, share_meeting, set_link_access, delete_meeting wait for your OK by default. You can switch that off per tool for scheduled runs.

Can my agent send the tl;dv bot to a meeting?

No. Cotlet's tools work on recordings that already exist. tl;dv's help center adds the bot through the Chrome extension or the desktop app, or by turning on auto-recording in Preferences, and neither tl;dv's API nor its MCP server sends the bot.

Should I use a tl;dv MCP server from GitHub instead?

Pick one if you want the code on your own computer and do not mind the upkeep: you install it, sign it in and fix it when tl;dv changes. Pick Cotlet if you want it hosted and kept working for you.

Can I use it in n8n, Make or Zapier?

Yes. Add https://cotlet.dev/mcp/v1 in n8n's MCP Client node, or call the REST endpoints from an HTTP step in Make or Zapier.

Who runs Cotlet?

Cotlet is run by Take Group, a Polish software company working since 2019. Take Group runs about 3,200 websites on its own systems and has its own DevOps team for infrastructure security. We built and used integrations like this inside the company for years before opening them as Cotlet.

Is Cotlet affiliated with tl;dv?

No. Cotlet is independent and not affiliated with tl;dv.

Give your agent access to tl;dv.

Free 7-day trial with 2,000 credits, no card needed.

Sign up free