tl;dv MCP for Zoom, Google Meet and MS Teams
OfficialYou can use this server to give AI assistants read-only access to your tl;dv meeting library for searching meetings and retrieving metadata, transcripts, and highlights.
Search/list meetings with filters for date range, query, meeting type, participation status, and pagination (up to 50 results per query).
Get meeting metadata by ID: title, date, duration, status, organizer, participants, and meeting URL.
Get a full meeting transcript by meeting ID, returned in Markdown with timestamps and speakers.
Get highlights from a meeting by ID.
Access is read-only and scoped to meetings you can already open in tl;dv; it cannot create, edit, delete, or share meetings.
The hosted remote MCP version also supports retrieving meeting notes and user profile.
Enables integration with Google services (specifically Google Meet) for accessing and analyzing meeting data through the tl;dv API
Enables access to Google Meet meeting data through the tl;dv API, including listing meetings, retrieving meeting metadata, transcripts, and AI-generated highlights
Provides access to Zoom meeting data through the tl;dv API, allowing retrieval of meeting lists, detailed metadata, transcripts, and meeting highlights
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@tl;dv MCP for Zoom, Google Meet and MS Teams summarize my last team meeting"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Official MCP Server for tl;dv API
Connect your tl;dv meeting library to AI assistants through the Model Context Protocol.
tl;dv hosts this server. Connect it from the connector directory in Claude or ChatGPT, authorize it with OAuth, and start querying your library. No installation or API key is required. This repository holds the local build for anyone who would rather run the server themselves.
This is the only official tl;dv MCP repository. Any tl;dv MCP server you find on GitHub, GitLab, npm, or elsewhere is not maintained by tl;dv. If you find one, please report it to tl;dv at support@tldv.io. Last updated September 2026.
Official MCP
Official tl;dv documentation: https://tldv.notion.site/tl-dv-MCP-Official-Documentation-330cce15f3ba80638f5ac0253e3b8fd4
Related MCP server: Granola MCP Server
At a glance
Availability: included on the tl;dv Pro plan and above.
Hosting: hosted by tl;dv. No local install required.
Authentication: OAuth, not an API key. Access tokens last for five minutes.
Permissions: scoped, approved in your browser, and revocable at any time from your tl;dv account without changing your password. The connector inherits your existing tl;dv library permissions and cannot reach any meeting you could not already open in the app. That limit is enforced server-side rather than described in the tool text.
Connecting: available in the Claude and ChatGPT connector directories. On ChatGPT, connectors require a paid plan, and on workspace plans, an admin may need to enable them first.
Access: read-only. The server cannot create, edit, delete, or share meetings.
Default scope: searches cover meetings you took part in. To widen this, ask for it, such as "include meetings I wasn't part of."
Meeting organizer's plan: you can only reach a meeting through the server if its organizer is also on Pro or above.
Results per query: a search returns up to 50 meetings.
Admin controls: organization admins can block MCP access through integration policies.
Security: the API and the MCP endpoint are both covered by tl;dv's SOC 2 program and included in the pentest scope. See trust.tldv.io.
Features
Search Meetings: retrieve meetings based on filters, including query, date range, participation status, and type, with pagination.
Get Meeting Metadata: fetch details for a specific meeting by ID, including title, date, duration, status, organizer, participants, and meeting URL.
Get Meeting Transcript: obtain the full transcript for any meeting ID, returned in Markdown.
Get Meeting Notes: retrieve AI-generated notes, manual notes, timestamps, and AI-processing status.
Get User Profile: retrieve your tl;dv profile, role, registration date, and team size. (Only available on the Remote MCP server)
How meetings get into your library
The MCP server reads meetings that tl;dv has already recorded. They get there in two ways.
The tl;dv bot joins Google Meet, Zoom, and Microsoft Teams calls as a visible participant. With calendar sync, it joins scheduled meetings automatically and captures video and audio.
The tl;dv desktop app records system audio from your Mac or Windows machine without a bot joining. Because it captures device audio rather than meeting data, it works on any platform that produces sound, including Slack huddles, Discord, WhatsApp, Google Meet, Zoom, and Teams. Bot-free recordings are audio only, so they contain no video, screen sharing, or chat.
The tl;dv mobile app records in-person audio from your mobile device running iOS and Android. Works offline and syncs to your workspace when the device is back online. These recordings are audio only.
Recording without a bot removes the visible participant, not the obligation to tell people they are being recorded. Consent requirements apply to in-person conversations too, and they vary by jurisdiction.
Running the server locally
This repository is a local build you run yourself and authenticate with a tl;dv API key rather than OAuth. Most people should use the hosted connector described above; if your MCP client doesn't support remote connectors, you can use this local version.
Disclaimer
Although this is the official local MCP server repo maintained by the tl;dv team, we don't update it regularly because we are prioritizing remote MCP servers.
Prerequisites
tl;dv Account: A Pro plan or above.
tl;dv API Key: You need an API key, which can be requested from your tl;dv settings: https://tldv.io/app/settings/personal-settings/api-keys.
Node.js and npm (for Node installation): If installing via Node.js, make sure Node.js and npm are installed.
Docker (for Docker installation): If installing via Docker, make sure Docker is installed and running.
Installation and Configuration
You can run this MCP server using either Docker or Node.js. Configure your MCP client (e.g., Claude Desktop, Cursor) to connect to the server.
Using Docker
Go in the repo.
Build the Docker image:
docker build -t tldv-mcp-server .Configure your MCP Client: Update your MCP client's configuration file (e.g.,
claude_desktop_config.json). The exact location and format may vary depending on the client.{ "mcpServers": { "tldv": { "command": "docker", "args": [ "run", "-i", "--init", "--rm", "-e", "TLDV_API_KEY=<your-tldv-api-key>", "tldv-mcp-server" ] } } }Replace
<your-tldv-api-key>with your actual tl;dv API key.
Using Node.js
Install dependencies:
npm installBuild the server:
npm run buildThis command creates a
distfolder containing the compiled server code (index.js).Configure your MCP Client: Update your MCP client's configuration file.
{ "mcpServers": { "tldv": { "command": "node", "args": ["/absolute/path/to/tldv-mcp-server/dist/index.js"], "env": { "TLDV_API_KEY": "your_tldv_api_key" } } } }Replace
/absolute/path/to/tldv-mcp-server/dist/index.jswith the correct absolute path to the built server file andyour_tldv_api_keywith your tl;dv API key.
Refer to your specific MCP client's documentation for detailed setup instructions (e.g., Claude Tools).
Disclaimer Once you are updating this config file, you will need to kill your MCP client and restart it for the changes to be effective.
Development
Install dependencies:
npm installSet up Environment Variables: Copy the example environment file:
cp .env.example .envEdit the
.envfile and add yourTLDV_API_KEY. Other variables can be configured as needed.Run in development mode: This command starts the server with auto-reloading on file changes:
npm run watchUpdate client for local development: Configure your MCP client to use the local development server path (typically
/path/to/your/project/dist/index.js). Ensure theTLDV_API_KEYis accessible, either through the client'senvconfiguration or loaded via the.envfile by the server process.Reload your MCP Client Since you are running the watch command, it will recompiled a new version. Reloading your Client (e.g Claud Desktop App), your changes will be effective.
Debugging
Console Logs: Check the console output when running
npm run devfor detailed logs. The server uses thedebuglibrary; you can control log levels via environment variables (e.g.,DEBUG=tldv-mcp:*).Node.js Debugger: Utilize standard Node.js debugging tools (e.g., Chrome DevTools Inspector, VS Code debugger) by launching the server process with the appropriate flags (e.g.,
node --inspect dist/index.js).MCP Client Logs: Check the logs provided by your MCP client, which might show the requests sent and responses received from this server.
Learn More
Available Tools
4 toolsget-highlightsC
Allows you to get highlights from a meeting by providing a meeting ID.
Inputs: meetingId (required).
get-meeting-metadataC
Get a meeting by its ID. The meeting ID is a unique identifier for a meeting. It will return the meeting metadata, including the name, the date, the organizer, participants and more.
Inputs: id (required).
get-transcriptC
Get transcript by meeting ID. The transcript is a list of messages exchanged between the participants in the meeting. It's time-stamped and contains the speaker and the message
Inputs: meetingId (required).
list-meetingsC
List all meetings based on the filters provided. You can filter by date, status, and more. Those meetings are the sames you have access to in the TLDV app.
Inputs: query, page, limit, from, +3 more.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 4 tools
Each tool has a clearly distinct purpose: get-highlights retrieves highlights, get-meeting-metadata provides metadata, get-transcript fetches the transcript, and list-meetings lists meetings with filters. There is no overlap in functionality, making it easy for an agent to select the correct tool.
All tool names follow a consistent verb_noun pattern (e.g., get-highlights, get-meeting-metadata, get-transcript, list-meetings). The naming is uniform and predictable, using snake_case throughout with clear action prefixes.
With 4 tools, the count is reasonable for a meeting-focused server, covering key operations like listing, retrieving metadata, transcripts, and highlights. It is slightly lean but well-scoped, as each tool serves a distinct purpose without being overwhelming.
The tool set covers essential read operations for meetings (list, metadata, transcript, highlights), which aligns well with the server's purpose of accessing meeting data. A minor gap exists in write operations (e.g., creating or updating meetings), but agents can still perform core workflows effectively.
Maintenance
Related MCP Connectors
Ask Claude about your meetings: summaries, action items and transcripts from Roomtone
Connect Claude to Fathom meeting recordings, transcripts, and summaries
Bring meeting decisions, tasks and user stories into your AI editor (Claude, Cursor, Copilot).
Connect your team's living knowledge base — docs, data, issues, CRM — to Claude and ChatGPT.
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceIntegrates with Claude to enable intelligent querying of documentation data, transforming crawled technical documentation into an actionable resource that LLMs can directly interact with.2,106Apache 2.0
- AlicenseAqualityDmaintenanceIntegrates local Granola.ai meeting intelligence with Claude Desktop to enable searching and analyzing meeting transcripts, notes, and summaries. Users can perform natural language queries to retrieve meeting details, analyze participant patterns, and access full speaker-identified conversations.5MIT
- AlicenseNot gradedqualityDmaintenanceBring your Plaud Note recordings into Claude Desktop. Search meetings, pull transcripts, and ask Claude about your notes — directly from chat.1MIT
- AlicenseNot gradedqualityDmaintenanceBridges Granola.ai meeting intelligence with Claude Desktop, enabling natural language access to meeting transcripts, notes, and insights.94MIT