[Cotlet](https://cotlet.dev/index.md) · [Integrations](https://cotlet.dev/integrations.md) · [How it works](https://cotlet.dev/how-it-works.md) · [Use cases](https://cotlet.dev/use-cases.md) · [Security](https://cotlet.dev/security.md) · [For developers](https://cotlet.dev/for-developers.md) · [For automation agencies](https://cotlet.dev/for-agencies.md) · [Blog](https://cotlet.dev/blog.md) · [API docs](https://cotlet.dev/docs.md) · [Help center](https://cotlet.dev/help.md) · [Changelog](https://cotlet.dev/changelog.md) · [Contact](https://cotlet.dev/contact.md) · [Pricing](https://cotlet.dev/pricing.md) · [Sign up](https://cotlet.dev/signup)

# tl;dv API and MCP server

> 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.

Meeting recorder for Google Meet, Zoom and Microsoft Teams: a bot or desktop app records the call, then tl;dv adds a transcript, AI notes with timestamps, clips and sharing in a searchable library.

## What is the tl;dv API?

Cotlet's tl;dv API exposes 13 endpoints for your own tl;dv account: list meetings, get meeting, get transcript, get meeting notes, list clips, list folders, add note, create clip, rename meeting, add meeting to folder, share meeting, set link access and delete meeting. The list_meetings endpoint returns meetings in your library with title, date, duration, your role and folder, newest first. Each endpoint takes simple JSON inputs like meeting_id, folder_id or limit and works both as an operation of the tldv_read or tldv_write MCP tool for agents and as a REST call for scripts.

- **Category:** [Productivity & teams](https://cotlet.dev/integrations/category/productivity-teams.md)
- **Endpoints:** 13 (6 read, 7 write)
- **Updated:** 2026-10-21

tl;dv has a public REST API (version v1alpha1) and an official hosted MCP server, and both are read-focused (checked 17 Oct 2026). Cotlet is a hosted MCP server and REST API for tl;dv with 13 endpoints (6 read, 7 write): you sign in once in your own cloud browser, your AI agent does the work.

## Does tl;dv have an official 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.

| Task | tl;dv official | Cotlet |
|---|---|---|
| List and search meetings | Yes: API list endpoint and MCP search; the MCP returns at most 50 meetings per search | Yes |
| Read a meeting transcript | Yes: API and MCP; the API returns it only once processing is complete | Yes |
| Read AI and manual notes | Yes: API notes endpoint and MCP notes tool | Yes |
| Create a clip from a moment | No | Yes |
| Add a timestamped note | No: The API highlights endpoint is deprecated and read-only | Yes |
| Share a meeting or change who can open it | No | Yes |
| Rename a meeting or add it to a folder | No | Yes |
| Delete a recording | No: The API docs say meetings can only be imported, not updated or deleted | Yes |

Sources: [tl;dv Public API docs (v1alpha1)](https://doc.tldv.io), [tl;dv Help: API](https://intercom.help/tldv/en/articles/11583137-api), [tl;dv Help: MCP](https://intercom.help/tldv/en/articles/15322415-mcp), [tl;dv MCP server (official repository)](https://github.com/tldv-public/tldv-mcp-server)

## For AI agents

```text
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.
Cotlet provides a hosted MCP server and REST API for tl;dv: 13 tools (6 read, 7 write).
Access       Sign up at https://cotlet.dev/app/signup?app=tldv, then request the app and create API keys in the Cotlet console.

MCP server   https://cotlet.dev/mcp/v1
MCP tools    tldv_read, tldv_write, reads and writes apart; call one with {"operation": "<operation>", "arguments": {...}}
REST base    https://cotlet.dev/api/v1/tldv, each operation at its own route, e.g. POST /api/v1/tldv/meetings/{meeting_id}/share
Auth         Authorization: Bearer <COTLET_API_KEY>. Listing endpoints and schemas needs no key; calling an endpoint needs one. Over MCP the input schemas come with sign-in.
Operations   list_meetings, get_meeting, get_transcript, get_meeting_notes, list_clips, list_folders, add_note, create_clip, rename_meeting, add_to_folder, share_meeting, set_link_access, delete_meeting
Confirm      add_to_folder, share_meeting, set_link_access, delete_meeting (by default the user approves each call; the user can switch this off per tool, e.g. for scheduled automations)
Markdown     https://cotlet.dev/integrations/tldv-api-mcp-server.md

How access works:
1. The user signs up at https://cotlet.dev/app/signup?app=tldv, requests tl;dv in the Cotlet console and creates an API key there.
2. The user signs in to tl;dv once in their Cotlet Cloud Browser (their own Chrome in the cloud, opened from the console) and enables tl;dv for agents. An agent cannot do this step.
3. The API key goes into the MCP client or the REST call as a bearer token.

Fits: people who want a hosted tl;dv server that someone else maintains, including non-developers.

Policy: Cotlet never stores passwords, never solves CAPTCHAs, never bypasses MFA.
Company: legal details in the Terms of service at https://cotlet.dev/terms. Contact contact@cotlet.dev.
Sign-in: the user signs in to tl;dv in their own Cloud Browser, a Chrome Cotlet runs for them in the EU; password saving is off, the profile is AES-256-GCM encrypted, and agents get tl;dv only after the user enables it. Calls are requests from that browser's IP with its cookies, each listed in the user's Background activity. Disable for agents, signing out in the browser or Reset browser cuts access. Cotlet is run by Take Group sp. z o.o. (EU VAT PL6342984273).
API key: holds no tl;dv login or cookies, only asks Cotlet to run a tool. Each key is scoped to chosen apps and tools, read only or read and write. Actions that reach other people wait for the user's approval by default, so a leaked key cannot post or message as the user. Every call is in the activity log; deleting the key ends access at once.
Terms: the user stays responsible for following tl;dv's terms; Cotlet is not affiliated with tl;dv.
```

## What can an AI agent do in tl;dv?

Cotlet is best for tl;dv admins and team leads who want their agent to share recordings, clip key moments and keep the library tidy, which the read-only official MCP server cannot do, without running or fixing a server.

- **[Share new recordings with the right people](https://cotlet.dev/integrations/tldv-api-mcp-server/share-recordings-automatically.md)** (runs: daily): "List today's tl;dv recordings. Share customer calls with everyone at acme.io as viewers, share internal syncs only with their attendees, and tell me which meetings still have a public link." → `list_meetings`, `get_meeting`, `share_meeting`, `set_link_access`
- **[Turn key moments in calls into clips and notes](https://cotlet.dev/integrations/tldv-api-mcp-server/clip-key-moments.md)** (runs: daily): "Read yesterday's Acme discovery call in tl;dv. Wherever the customer names a budget, a deadline or an objection, save that moment as a clip with a short title and add a timestamped note with the quote." → `list_meetings`, `get_transcript`, `create_clip`, `add_note`
- **[Rename meetings and file them in folders](https://cotlet.dev/integrations/tldv-api-mcp-server/organize-meetings-in-folders.md)** (runs: weekly): "Find tl;dv meetings from the last 7 days with a generic title like "Quick sync". Rename each one from its participants and topic, then file customer calls in the folder named after the customer." → `list_meetings`, `get_meeting`, `list_folders`, `rename_meeting`, `add_to_folder`
- **Pull action items from the week's calls** (runs: weekly): "Go through my tl;dv meetings from the last 7 days. For each call, list the action items and decisions from the notes, and open the transcript only where the notes are missing or unclear." → `list_meetings`, `get_meeting_notes`, `get_transcript`
- **Delete recordings you no longer need**: "List tl;dv recordings older than 90 days that are shorter than 5 minutes or titled "test". Show me the list, and delete only the ones I approve." → `list_meetings`, `get_meeting`, `delete_meeting`

## Can tl;dv automations run on a schedule in n8n, Make or Zapier?

Yes. Cotlet does not replace your automation platform: it gives it a tl;dv connection it does not have, with the same API key as your agent. Write actions ask for your OK by default; switch that off in your dashboard for the tools you choose, for example to share new recordings with the right people, and the schedule runs on its own. Cotlet runs in the cloud, so it keeps going while your computer is off.

| Where | How to connect | How to schedule |
|---|---|---|
| Your AI agent | Add https://cotlet.dev/mcp/v1 with your API key. | A scheduled agent run, for example a Claude Code routine. |
| n8n | MCP Client node with https://cotlet.dev/mcp/v1, or an HTTP Request node with the endpoint's method and URL, such as GET https://cotlet.dev/api/v1/tldv/meetings. | Schedule Trigger node. |
| Make | HTTP module: the endpoint's method and URL with an Authorization: Bearer header, and a JSON body for POST, PUT and PATCH. | Scenario schedule. |
| Zapier | Webhooks by Zapier, Custom Request: the same method, URL, header and body. | Schedule by Zapier trigger. |
| Your own script | GET https://cotlet.dev/api/v1/tldv/meetings with your API key. | cron or GitHub Actions. |

## Tools

**For AI agents:** Every endpoint and its schema is public. The 13 endpoints on this page, with parameters and example responses, can be listed without an account. Calling one returns 401 without an API key and 403 while the key has no access to tl;dv.

### list_meetings

Meetings in your library with title, date, duration, your role and folder, newest first. Access: read. REST: `GET /api/v1/tldv/meetings`. MCP: `tldv_read → list_meetings`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `query` | string | no | Text to find in meeting titles. |
| `from` | date | no | Only meetings on or after this date. |
| `to` | date | no | Only meetings on or before this date. |
| `folder_id` | string | no | Only meetings in this folder, from list_folders. |
| `limit` | integer | no | 1 to 50. Default: 20. |
| `cursor` | string | no | Next page cursor from the previous call. |

Lists meetings in your tl;dv library, newest first. Filter by a text query, a date range or a folder. Each item shows your role on the meeting (admin, editor or viewer), which decides what you can change. Pages hold up to 50 meetings; pass next_cursor back as cursor for the next page. A meeting still being processed shows status processing.

Example response:

```json
{
  "meetings": [
    {
      "meeting_id": "mt_4f21a9",
      "title": "Acme discovery call",
      "started_at": "2026-10-15T14:00:00Z",
      "duration_minutes": 42,
      "organizer": "You",
      "role": "admin",
      "participants": 3,
      "folder": null,
      "status": "ready"
    }
  ],
  "next_cursor": "eyJvZmZzZXQiOjUwfQ"
}
```

### get_meeting

One meeting with participants, link, folder and who can open it. Access: read. REST: `GET /api/v1/tldv/meetings/{meeting_id}`. MCP: `tldv_read → get_meeting`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `meeting_id` | string | yes | Meeting ID from list_meetings. |

Returns one meeting: title, date, duration, organizer, participants with their emails, the tl;dv URL and the access list. The access list names the link level (Anyone with the link, or People with access) and each person or domain with Admin, Editor or Viewer. Use it before share_meeting to see who can already open the call.

Example response:

```json
{
  "meeting_id": "mt_4f21a9",
  "title": "Acme discovery call",
  "started_at": "2026-10-15T14:00:00Z",
  "duration_minutes": 42,
  "organizer": "You",
  "participants": [
    {
      "name": "Dana Whitfield",
      "email": "dana@acme.io"
    },
    {
      "name": "Sam Okafor",
      "email": "sam@acme.io"
    }
  ],
  "url": "https://tldv.io/app/meetings/mt_4f21a9",
  "status": "ready",
  "folder": null,
  "access": {
    "link": "people_with_access",
    "people": [
      {
        "who": "You",
        "level": "admin"
      }
    ]
  }
}
```

### get_transcript

Full transcript of a meeting with speaker and time per line. Access: read. REST: `GET /api/v1/tldv/meetings/{meeting_id}/transcript`. MCP: `tldv_read → get_transcript`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `meeting_id` | string | yes | Meeting ID from list_meetings. |

Returns the transcript of one meeting, one line per speaker turn with its timestamp. While tl;dv is still processing the recording, the call returns status processing and no text, so try again later. Use the timestamps with create_clip and add_note.

Example response:

```json
{
  "meeting_id": "mt_4f21a9",
  "status": "ready",
  "lines": [
    {
      "time": "00:12:05",
      "speaker": "Dana Whitfield",
      "text": "We have the budget confirmed for Q4, but we need SSO before launch."
    },
    {
      "time": "00:12:21",
      "speaker": "You",
      "text": "Understood, SSO is on the plan for November."
    }
  ]
}
```

### get_meeting_notes

AI notes grouped by topic, plus the notes people added by hand, with timestamps. Access: read. REST: `GET /api/v1/tldv/meetings/{meeting_id}/notes`. MCP: `tldv_read → get_meeting_notes`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `meeting_id` | string | yes | Meeting ID from list_meetings. |

Returns the notes of one meeting: each topic has a short gist and timestamped notes that point to the moment in the recording. Notes added by hand are listed with their author. The status field says whether the AI notes are ready or still processing.

Example response:

```json
{
  "meeting_id": "mt_4f21a9",
  "status": "ready",
  "topics": [
    {
      "title": "Budget and timeline",
      "gist": "Budget is confirmed for Q4; SSO is required before launch.",
      "notes": [
        {
          "time": "00:12:05",
          "text": "Budget confirmed for Q4.",
          "source": "ai"
        }
      ]
    }
  ],
  "manual_notes": [
    {
      "time": "00:27:40",
      "text": "Ask about SSO provider.",
      "author": "You"
    }
  ]
}
```

### list_clips

Clips in your Clips library with title, meeting and length, newest first. Access: read. REST: `GET /api/v1/tldv/clips`. MCP: `tldv_read → list_clips`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `meeting_id` | string | no | Only clips from this meeting. |
| `limit` | integer | no | 1 to 50. Default: 20. |
| `cursor` | string | no | Next page cursor from the previous call. |

Lists the clips you saved, newest first, each with the meeting it was cut from and its length. Use it to avoid cutting the same moment twice. Pass next_cursor back as cursor for the next page.

Example response:

```json
{
  "clips": [
    {
      "clip_id": "cl_71d0",
      "title": "Budget confirmed for Q4",
      "meeting_id": "mt_4f21a9",
      "from_time": "00:12:05",
      "to_time": "00:12:53",
      "duration_seconds": 48
    }
  ],
  "next_cursor": null
}
```

### list_folders

Your folders with who can open them, version and number of meetings. Access: read. REST: `GET /api/v1/tldv/folders`. MCP: `tldv_read → list_folders`.

No parameters.

Lists the folders you can see in Meetings & Folders. Each folder shows who it is shared with (you only, users, a Team or the organization), your role in it and whether it is a new or a previous version folder. Previous version folders cannot be edited or shared with new users anymore, so add_to_folder does not accept them.

Example response:

```json
{
  "folders": [
    {
      "folder_id": "fo_31c2",
      "name": "Acme",
      "version": "new",
      "shared_with": "Sales team",
      "role": "admin",
      "meetings": 6
    },
    {
      "folder_id": "fo_08aa",
      "name": "2025 calls",
      "version": "previous",
      "shared_with": "only you",
      "role": "admin",
      "meetings": 41
    }
  ]
}
```

### add_note

Add a timestamped note to a finished meeting, under your name. Access: write. REST: `POST /api/v1/tldv/meetings/{meeting_id}/notes`. MCP: `tldv_write → add_note`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `meeting_id` | string | yes | Meeting ID from list_meetings. |
| `time` | string | yes | Timestamp in the recording, hh:mm:ss. |
| `text` | string | yes | Note text. |

Adds a note at a timestamp of a finished meeting, the same as selecting transcript text and clicking Add note. The note is stored with the recording and shown to everyone who can open it. It sends no alert, since tl;dv sends Slack mentions only for notes added during a meeting. It reaches no one directly and you edit or delete it from the note's menu in tl;dv, so it runs without asking first.

Example response:

```json
{
  "meeting_id": "mt_4f21a9",
  "note_id": "nt_2b90",
  "time": "00:12:05",
  "text": "Budget confirmed for Q4: \"We have the budget confirmed for Q4.\"",
  "status": "added"
}
```

### create_clip

Save a segment of a meeting as a clip in your Clips library. Access: write. REST: `POST /api/v1/tldv/meetings/{meeting_id}/clips`. MCP: `tldv_write → create_clip`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `meeting_id` | string | yes | Meeting ID from list_meetings. |
| `from_time` | string | yes | Start of the segment, hh:mm:ss. |
| `to_time` | string | yes | End of the segment, hh:mm:ss. |
| `title` | string | no | Clip title. Default: the meeting title. |

Cuts a clip from a start and an end time of one meeting, the same as Create clip on the recording, and saves it in your Clips library under the title you give. The call returns the clip ID and its link, and nothing is shared: tl;dv lets anyone who gets a clip link view it, so you decide where the link goes. It reaches no one, so it runs without asking first.

Example response:

```json
{
  "clip_id": "cl_71d0",
  "meeting_id": "mt_4f21a9",
  "title": "Budget confirmed for Q4",
  "from_time": "00:12:05",
  "to_time": "00:12:53",
  "duration_seconds": 48,
  "url": "https://tldv.io/app/clips/cl_71d0"
}
```

### rename_meeting

Change the title of a meeting. Access: write. REST: `PATCH /api/v1/tldv/meetings/{meeting_id}`. MCP: `tldv_write → rename_meeting`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `meeting_id` | string | yes | Meeting ID from list_meetings. |
| `title` | string | yes | New meeting title. |

Renames one meeting, so it is easier to find later. Everyone who can open the meeting sees the new title. It sends no message and one more call restores the old title, so it runs without asking first. The response returns the previous title.

Example response:

```json
{
  "meeting_id": "mt_4f21a9",
  "title": "Acme, discovery call, 15 Oct",
  "previous_title": "Quick sync"
}
```

### add_to_folder

File a meeting in one of your folders. Needs the Editor or Admin role on the meeting. Access: write, asks the user first. REST: `POST /api/v1/tldv/meetings/{meeting_id}/folders/{folder_id}`. MCP: `tldv_write → add_to_folder`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `meeting_id` | string | yes | Meeting ID from list_meetings. |
| `folder_id` | string | yes | Folder ID from list_folders. |

Adds one meeting to a folder. Only a meeting's Editor or Admin can do it, and the folder must be a new version folder. Anyone with access to the folder can view every meeting in it, so filing into a shared folder shows the meeting to its members. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "meeting_id": "mt_4f21a9",
  "folder_id": "fo_31c2",
  "folder": "Acme",
  "status": "added"
}
```

### share_meeting

Give people or a whole domain access to a meeting. Needs the Admin or Editor role on the meeting. Access: write, asks the user first. REST: `POST /api/v1/tldv/meetings/{meeting_id}/share`. MCP: `tldv_write → share_meeting`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `meeting_id` | string | yes | Meeting ID from list_meetings. |
| `share_with` | string[] | yes | Email addresses, or a domain as '*@company.com'. |
| `access` | enum | no | viewer, editor or admin. Default: viewer. |

Adds people to a meeting's access list at a level you choose. Pass emails, or a domain as *@company.com for everyone at that company. Each person added gets an email from tl;dv. Only an admin or editor of the meeting can change its sharing. Existing access is kept. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "meeting_id": "mt_4f21a9",
  "shared_with": [
    {
      "who": "dana@acme.io",
      "access": "viewer"
    },
    {
      "who": "sam@acme.io",
      "access": "viewer"
    }
  ],
  "notified": 2
}
```

### set_link_access

Make a meeting public to anyone with the link, or limit it to the people with access. Access: write, asks the user first. REST: `PUT /api/v1/tldv/meetings/{meeting_id}/link-access`. MCP: `tldv_write → set_link_access`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `meeting_id` | string | yes | Meeting ID from list_meetings. |
| `link_access` | enum | yes | anyone_with_link or people_with_access. |

Sets the overall access level of a meeting. anyone_with_link makes the recording viewable without signing in, and tl;dv says it is not indexed by search engines. people_with_access limits it to the access list again. Needs admin or editor on the meeting. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "meeting_id": "mt_9c3e17",
  "link_access": "people_with_access",
  "previous": "anyone_with_link"
}
```

### delete_meeting

Permanently delete a recording. It cannot be recovered. Access: write, asks the user first. REST: `DELETE /api/v1/tldv/meetings/{meeting_id}`. MCP: `tldv_write → delete_meeting`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `meeting_id` | string | yes | Meeting ID from list_meetings. |

Deletes one recording. tl;dv says a deleted recording cannot be recovered and that it keeps no backups. tl;dv does not document which roles may delete, so a call without the right is refused with the app's own error. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "meeting_id": "mt_1d77c0",
  "status": "deleted"
}
```

## How do I connect tl;dv to Claude Code, Codex or Cursor?

Connecting tl;dv takes three steps: sign up, sign in to tl;dv once in your Cloud Browser and enable it for agents, then add one MCP server or call the REST API with the same key.

### Connect tl;dv to your agent.

1. **Create an account** Sign up and add tl;dv in the console. Your API key is there too.

2. **Sign in to tl;dv in your Cloud Browser** Open your Cloud Browser in the console: your own Chrome in the cloud. Sign in to tl;dv there yourself, the way you always do, then press Enable for agents, read only or read and write. We never save your password, and your agent keeps working even when your computer is off.

3. **Add Cotlet to your agent** Paste the snippet for your client. The same server and key serve every app you connect, so you do this once.

   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"
```

4. **Ask your agent** Ask in plain words. Your agent finds the tl;dv tools on the server and calls them for you; anything that reaches other people waits for your OK unless you switch that off for a tool.

```
List today's tl;dv recordings. Share customer calls with everyone at acme.io as viewers, share internal syncs only with their attendees, and tell me which meetings still have a public link.
```

### Call tl;dv from your scripts.

1. **Export your API key** Your scripts use the same API key as your agent. Keep it in an environment variable, never in your code.

```
export COTLET_API_KEY="cotlet_..."
```

2. **Call a tool** Every tool is an endpoint under /api/v1/tldv with its own method and path, listed with the endpoints above. Path parameters go in the URL; the other parameters go in the query for GET and DELETE and in a JSON body otherwise.

```
curl -X POST https://cotlet.dev/api/v1/tldv/meetings/mt_4f21a9/share \
  -H "Authorization: Bearer $COTLET_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"share_with":["dana@acme.io","sam@acme.io"],"access":"viewer"}'
```

3. **Read the result** You get plain JSON back, ready for your script. A failed call costs nothing.

```
{
  "meeting_id": "mt_4f21a9",
  "shared_with": [
    {
      "who": "dana@acme.io",
      "access": "viewer"
    },
    {
      "who": "sam@acme.io",
      "access": "viewer"
    }
  ],
  "notified": 2
}
```

## Why use Cotlet for tl;dv?

**Built for agents**

- One MCP server for every app you connect.
- The same tools as a REST API for scripts and cron jobs.
- Works with Claude Code, Codex and Cursor.

**Your login stays yours**

- You sign in to tl;dv yourself, in your own Cloud Browser. We never save your password; the profile is encrypted with AES-256-GCM, the cipher 1Password uses.
- A+ on Qualys SSL Labs, securityheaders.com and Mozilla Observatory.
- The model never sees a login.
- No stored passwords, no CAPTCHA solving, no MFA bypass.

**You stay in control**

- Scope each API key: its apps, its tools, read only or read and write.
- Anything that reaches other people waits for your OK, so a leaked key cannot post or message as you.
- Every background request listed in your Background activity. Disable for agents in one click.

**Kept working for you**

- We test every integration every 6 hours.
- When tl;dv changes, the tool pauses until we fix it.
- Failed calls cost nothing.

## Is it safe to connect tl;dv to Cotlet?

Yes. You sign in to tl;dv yourself, in your own Cloud Browser, and we never save your password. Your agents only get tl;dv once you enable it, and every background request is listed. The browser profile is stored encrypted with AES-256-GCM, the same cipher 1Password uses for its vaults and Apple for iCloud Keychain. Independent public scanners grade cotlet.dev A+ and find it clean; click a result to rerun it yourself.

- **A+ on Qualys SSL Labs**: Encryption in transit: TLS setup and certificates, on all four server addresses. [Live result](https://www.ssllabs.com/ssltest/analyze.html?d=cotlet.dev)
- **A+ on securityheaders.com**: Browser protections sent with every page, all six headers present. [Live result](https://securityheaders.com/?q=cotlet.dev&followRedirects=on)
- **A+ on Mozilla Observatory**: Mozilla's web security baseline: score 120 of 100, 12 of 12 tests passed. [Live result](https://developer.mozilla.org/en-US/observatory/analyze?host=cotlet.dev)
- **Clean on Sucuri SiteCheck**: No malware, spam or defacement, and not on any of 9 blocklists, Google Safe Browsing included. [Live result](https://sitecheck.sucuri.net/results/cotlet.dev)

[How Cotlet protects your access](https://cotlet.dev/security.md)

### Common concerns

**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 this an official tl;dv integration?**

No, Cotlet is independent of tl;dv. tl;dv's own API is too limited for this work. Cotlet works through your own tl;dv account, the way you use tl;dv in the browser, so you need no partner approval and no developer setup.

**What about client data and GDPR?**

Cotlet is run from the EU and follows the GDPR. Cloud Browsers run in Finland, a Tier 1 country in the ITU Global Cybersecurity Index 2024. Data passes through a call and is not kept after it.

**Can I start with read only?**

Yes. Enable the app for agents as read only, or make the API key read only, and anything that reaches other people waits for your OK unless you switch that off per tool.

**Is it reliable?**

Every Cotlet service is checked every 3 minutes from Europe, North America, Asia and Australia. The live results and any outage are public at status.cotlet.dev.

**How do I stop?**

Press Disable for agents next to tl;dv in your console: your agents lose access at once and you stay signed in. Signing out of tl;dv in the browser works too, and Reset browser deletes the whole profile.

## Is there a tl;dv MCP server on GitHub?

Yes, tl;dv ships its own hosted MCP server and a REST API. The MCP server connects through OAuth in Claude or ChatGPT on Pro or higher, the API uses a key from your settings, and both only read. Cotlet works in your own account and adds the writes: share, clip, note, rename, file and delete.

|  | Official tl;dv MCP | Cotlet |
|---|---|---|
| Setup | Add the tl;dv connector in Claude or ChatGPT, sign in with OAuth, approve the scopes | Sign up, sign in to tl;dv once, add one MCP server or API key |
| What it does | Reads: search meetings, metadata, transcripts, notes. It cannot create, edit, delete or share | The same reads, plus share, clip, note, rename, file in folders and delete |
| When tl;dv changes | tl;dv maintains it; the API is alpha and its docs warn of upcoming changes | Our team tests it daily and fixes it for you; failed calls are free |
| Your tl;dv access | Scoped OAuth tokens that last five minutes, revocable from your tl;dv account | Signed in inside your own Cloud Browser in the EU, profile encrypted, only for the apps you enable, disabled for agents in one click |
| Plan needed | tl;dv Pro or higher, and the meeting organizer must be on Pro or higher too | Works in your own account; what it can do follows your role on each meeting |
| Where it runs | Claude and ChatGPT connectors | Hosted: Claude Code, Codex, Cursor, n8n and scripts, also on a schedule |
| Price | Included in your tl;dv plan | Free 7-day trial, then pay-as-you-go credit packs, no subscription |

### Which one fits you

**Pick Cotlet if**

- you are not a developer, or you do not want to maintain a server
- you need it to keep working when tl;dv changes, without checking it yourself
- your agent or a script should run it on a schedule, also while your computer is off

**Pick an open-source server if**

- you are comfortable installing, updating and fixing it yourself
- you want your sign-in to stay on your own computer
- you only need it now and then, from one MCP client

## How much does the tl;dv API cost?

Free 7-day trial with 2,000 credits, no card needed. After that, the tl;dv API is pay as you go with no limit on apps: Credit packs from $29 for 5,000 credits, one-time, no subscription. A successful call uses 20 to 30 credits (25 for most tools, about $0.10 to $0.15), your Cloud Browser uses 50 credits a day while it has an app enabled for agents, however many apps that is, and an agent driving the browser itself uses 5 credits a minute. Credit packs stay valid for 12 months and stack, so unused credits carry over.

| 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. [See full pricing](https://cotlet.dev/pricing.md)

## How Cotlet holds your access

Cotlet hosts MCP servers and REST APIs for apps with no usable API. Your agent works in your own tl;dv account.

- **Company details:** Cotlet is run by Take Group sp. z o.o., a company registered in Poland. Its full address and registration numbers are in the Terms of service. [Terms of service](https://cotlet.dev/terms)
- **Your sign-in:** You sign in to tl;dv yourself, in your own Cloud Browser: a Chrome we run for you in the EU, one per app. We never save your password (password saving is off), the profile is stored encrypted with AES-256-GCM, and your agents get tl;dv only after you enable it. When tl;dv signs you out, your agent gives you a link to sign in again. [Security](https://cotlet.dev/security.md)
- **Revoking access:** Press Disable for agents next to tl;dv, sign out of tl;dv in your Cloud Browser, or reset the browser. Every background request is listed in your Background activity. Actions that reach other people wait for your OK unless you switch that off per tool.
- **What we never do:** Store passwords, solve CAPTCHAs or bypass MFA.
- **tl;dv's terms:** You use your own tl;dv account and stay responsible for following tl;dv's terms. Cotlet is independent and not affiliated with tl;dv. [Terms](https://cotlet.dev/terms)
- **Contact:** Questions about the company, security or an app: [contact@cotlet.dev](mailto:contact@cotlet.dev)

## Frequently asked questions

**How do I get access?**

Sign up free, open tl;dv in the console and press Request access. Then you create your API key and connect tl;dv there.

**Do I need to be technical?**

No. You sign in to tl;dv once in your Cloud Browser, a normal Chrome you open from the console, and paste one command into your agent, or one URL into n8n. Your agent can walk you through it. There is no server to install, update or fix.

**Is it safe to connect tl;dv to Cotlet?**

Yes. You sign in to tl;dv yourself, in your own Cloud Browser in the EU, and we never save your password. Your agents only get tl;dv once you enable it, every background request is listed, and the browser profile is stored encrypted with AES-256-GCM, the cipher 1Password uses for its vaults. The AI model never sees a login, posts and messages wait for your OK, and Disable for agents cuts access in one click. Independent scanners grade cotlet.dev A+ on Qualys SSL Labs, securityheaders.com and Mozilla Observatory; live results are on https://cotlet.dev/security.

**Is a hosted server safer than a local one? My tl;dv sign-in would leave my computer.**

On Cotlet you sign in inside your own Cloud Browser, which only you open, and its profile is stored encrypted with AES-256-GCM in the EU. Agents get only the apps you enable, and every background request is listed. A local server keeps your tl;dv cookie in a plain file on your computer, readable by any program you run, and stops when your computer is off.

**Why does Cotlet send requests instead of clicking in my browser?**

To be fast, Cotlet doesn't click through tl;dv's pages. It sends the same requests your browser would, from your browser's IP with its cookies, without opening a window. tl;dv sees the same browser and IP you signed in with, and every request is listed in your Background activity.

**What if someone gets my Cotlet API key?**

The key holds no tl;dv login or cookies, it only asks Cotlet to run a tool. It can call only the apps and tools you gave it, and a read-only key changes nothing. Anything that reaches other people, like posts, comments or messages, waits for your OK in the dashboard by default, so a leaked key cannot post or message as you. When you switch approval off for a scheduled job, give that job its own key limited to that one tool. Every call is in your activity log, and deleting the key ends access at once.

**Why a signed-in browser and not OAuth, like other integration platforms?**

tl;dv offers no OAuth token you can simply grant for these tools: its official API leaves them out or needs a developer app, a plan or an approval first (see the official API section above). That is why Cotlet sets the limits itself: per key, per tool, with your approval before anything reaches other people. Cotlet is run by Take Group sp. z o.o., an EU company (VAT PL6342984273).

**Do I need a paid tl;dv plan or an API key?**

No key. Cotlet works in your own tl;dv account, so what your agent can do follows your role on each meeting: changing sharing needs admin or editor, and filing in a folder needs Editor or Admin. tl;dv's own API and MCP server are different: they need an organizer on a paid plan, and the MCP server needs Pro or higher.

**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.

**Can my agent post or send messages in tl;dv without asking me?**

No. Every call to add_to_folder, share_meeting, set_link_access or delete_meeting waits for your OK by default. For scheduled automations you can switch confirmation off per tool in your dashboard, for example only for approvals. add_note, create_clip, rename_meeting runs without asking, because it sends nothing to anyone and one call undoes it.

**Can I use the tl;dv API in n8n?**

Yes. Add https://cotlet.dev/mcp/v1 with your API key in n8n's MCP Client node, or call its endpoints under https://cotlet.dev/api/v1/tldv from the HTTP Request node.

---

Give your AI agents your signed-in browser.

**Product:** [Integrations](https://cotlet.dev/integrations.md) · [Use cases](https://cotlet.dev/use-cases.md) · [How it works](https://cotlet.dev/how-it-works.md) · [Pricing](https://cotlet.dev/pricing.md) · [Security](https://cotlet.dev/security.md)

**Resources:** [Blog](https://cotlet.dev/blog.md) · [API docs](https://cotlet.dev/docs.md) · [Help center](https://cotlet.dev/help.md) · [Changelog](https://cotlet.dev/changelog.md) · [GitHub](https://github.com/cotletdev/cotlet)

**Solutions:** [For developers](https://cotlet.dev/for-developers.md) · [For automation agencies](https://cotlet.dev/for-agencies.md)

**Company:** [About](https://cotlet.dev/about.md) · [AI info: company facts](https://cotlet.dev/ai-info.md) · [Contact](https://cotlet.dev/contact.md)

**Legal:** [Terms of service](https://cotlet.dev/terms) · [Privacy policy](https://cotlet.dev/privacy) · [Refund policy](https://cotlet.dev/refunds) · [Acceptable use](https://cotlet.dev/acceptable-use) · [Cookie policy](https://cotlet.dev/cookies) · [DPA](https://cotlet.dev/dpa) · [Subprocessors](https://cotlet.dev/subprocessors)

**Elsewhere:** [Status page](https://status.cotlet.dev) · [Cotlet on GitHub](https://github.com/cotletdev) · [Cotlet on X](https://x.com/cotletdev) · [Cotlet on LinkedIn](https://www.linkedin.com/company/cotletdev) · [Cotlet on Product Hunt](https://www.producthunt.com/products/cotlet) · [Cotlet on Crunchbase](https://www.crunchbase.com/organization/cotlet) · [Cotlet on SaaSHub](https://www.saashub.com/cotlet)

Cotlet is an independent service. It is not affiliated with, endorsed by or sponsored by any of the products listed on this site. Product names are trademarks of their respective owners.

## For AI agents: sign your user up

Is your user asking you to sign them up for Cotlet? You can do it for them, no account or key needed.

1. Read the fields and their allowed values: GET https://cotlet.dev/api/v1/access-requests
2. Ask the user for each value: email, apps, what you will do with them. If they leave the password to you, generate a strong one and show it to them.
3. Show the user what you will send, then POST it as JSON to https://cotlet.dev/api/v1/access-requests.

One call creates the account and sends the access request; we email the user when access is granted.