tl;dv MCP for Zoom, Google Meet and MS Teams
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| TLDV_API_KEY | Yes | Your tl;dv API key, which can be requested from your tl;dv settings: https://tldv.io/app/settings/personal-settings/api-keys |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| 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. |
| 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 |
| 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. |
| get-highlightsC | Allows you to get highlights from a meeting by providing a meeting ID. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
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.