tldv

This MCP server exposes tl;dv integration capabilities through the Model Context Protocol. It enables clients to list meetings across Google Meet, Zoom, and Microsoft Teams, fetch meeting metadata, retrieve transcripts, and obtain AI-generated highlights for any given meeting. The server can be run either via Docker or directly with Node.js, allowing MCP clients (such as Claude Desktop or Cursor) to connect using a consistent interface across platforms. Configure your MCP client to point to the appropriate server entry (e.g., the tldv entry) and provide your tl;dv API key when prompted. Once connected, you can perform operations like listing meetings with filters, getting detailed metadata for a specific meeting by ID, and requesting transcripts and highlights with standardized response formats.

Prerequisites:

• tl;dv account (Business or Enterprise)
• tl;dv API key
• Docker (if using Docker)
• Node.js and npm (if using Node.js installation)

Installation options:

Option A: Docker

1. Build the Docker image in the repository (or pull if published): docker build -t tldv-mcp-server .
2. Run the container with your API key: docker run -i --init --rm -e TLDV_API_KEY=YOUR_API_KEY tldv-mcp-server
3. Point your MCP client to the running server (using the tldv-docker configuration example).

Option B: Node.js

1. Install dependencies and build: npm install npm run build
2. Start the server locally: node dist/index.js
3. Configure your MCP client to connect to the local server, ensuring the TLDV_API_KEY is provided (env or config).

Prerequisites recap:

• Ensure your API key is securely stored and available to the server process (env variables or a .env file).
• For development, you can use npm run watch to rebuild on changes if supported by the project.

Note: Replace placeholder API keys with your actual tl;dv API key in the environment or configuration files.

Tips and common issues:

• Ensure the TLDV_API_KEY is accessible to the MCP client or server process (use environment variables or dedicated config files).
• If changing client configuration, restart the MCP client to reload updated server connections.
• When using Docker, remember to expose or mount any required configuration files if your client expects local paths.
• Enable verbose/debug logging during setup (e.g., DEBUG=tldv-mcp:*) to troubleshoot requests and responses.
• The server currently supports listing meetings, retrieving metadata, transcripts, and highlights across all supported platforms; the import feature is indicated as Coming Soon.