Skip to content
tl;dv logo

tl;dv MCP server

Record meetings, get transcripts, and access meeting notes automatically.

tl;dv is not a separate install. One Activepieces MCP server exposes it alongside 760+ other apps, behind a single URL.

Tools
5
Works with
Any MCP client
Auth
API key
License
MIT, open source
Updated
August 2026

About the tl;dv MCP server

Connect tl;dv once in Activepieces and every action it ships becomes a tool your assistant can call, behind the same server URL as the rest of your apps. Your agent reaches tl;dv and 760+ other apps over a single connection, on our cloud or a self-hosted install.

Tools

tl;dv tools your AI can run

Once connected, your assistant can call any of these tl;dv actions by asking in plain language.

  • Upload Recording

    Import a meeting or recording from a URL

    5 fields

  • List Meetings

    Search and list meetings

    7 fields

  • Get Meeting

    Get meeting details by ID

    1 field

  • Get Transcript

    Get meeting transcript by meeting ID

    1 field

  • Get Highlights

    Get meeting highlights (notes) by meeting ID

    1 field

Triggers

tl;dv events your agent can watch

These start a run the moment something happens in tl;dv, so work gets picked up on its own.

  • Meeting Ready

    Triggers when a meeting has finished processing and is ready

    1 field

  • Transcript Ready

    Triggers when a meeting transcript has been generated

    1 field

tl;dv MCP, answered.

No. That is the point of it. One Activepieces server exposes tl;dv alongside every other piece you connect, so your client keeps a single connection.

Yes. Activepieces is open source and free to start, and the MCP server is included on every plan, from the free cloud tier to any self-hosted deployment.

Connect tl;dv in Activepieces, enable the server under Settings → MCP Server, then paste your server URL into your client config. It authenticates over OAuth on first use.

It can call 5 tools, including Upload Recording, List Meetings, Get Meeting, and chain them with steps in other apps inside the same run.

Connections use OAuth2 with limited scopes and are stored under 256-bit encryption, with no API to read them back, so an agent gets scoped access rather than your keys.