Official MCP Server for tl;dv API
🚀 The First and Only MCP Server for Google Meet, Zoom, and Microsoft Teams Integration
This project provides a Model Context Protocol (MCP) server enabling seamless interaction with the tl;dv API. As the pioneering MCP solution for video conferencing platforms, it unlocks the power of tl;dv's meeting intelligence across Google Meet, Zoom, and Microsoft Teams through a standardized interface. This integration allows AI models and MCP clients to access, analyze, and derive insights from your meetings across all major platforms in one unified way.
Features
- List Meetings: Retrieve meetings based on filters (query, date range, participation status, type) across all supported platforms.
- Get Meeting Metadata: Fetch detailed information for a specific meeting by ID, regardless of the platform it was hosted on.
- Get Transcript: Obtain the transcript for any meeting ID, with consistent formatting across all platforms.
- Get Highlights: Retrieve AI-generated highlights for meetings from any supported platform.
- Import Meeting (Coming Soon): Functionality to import meetings via URL from any supported platform.
Prerequisites
- tl;dv Account: A Business or Enterprise tl;dv account is required.
- 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 & npm (for Node installation): If installing via Node.js, ensure Node.js and npm are installed.
- Docker (for Docker installation): If installing via Docker, ensure 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 install -
Build 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 install -
Set 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 watch -
Update 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.