Home / MCP / tl;dv MCP Server

tl;dv MCP Server

Provides cross-platform access to tl;dv meeting data via MCP, enabling listing, metadata, transcripts, and highlights.

typescript

7stars

View on GitHub

Installation

Add the following to your MCP client configuration file.

Configuration

View docs

{
    "mcpServers": {
        "tldv_mcp": {
            "command": "docker",
            "args": [
                "run",
                "--rm",
                "--init",
                "-e",
                "TLDV_API_KEY=<your-tldv-api-key>",
                "tldv-mcp-server"
            ],
            "env": {
                "TLDV_API_KEY": "<your-tldv-api-key>"
            }
        }
    }
}

You deploy this MCP server to enable seamless access to tl;dv meeting data across Google Meet, Zoom, and Microsoft Teams. It provides a standardized interface to list meetings, fetch metadata and transcripts, and retrieve AI-generated highlights, so your AI models and MCP clients can operate across platforms in one unified way.

How to use

Connect your MCP client to the server using the provided runtime configurations. The server exposes endpoints and a local runtime you can run, either via Docker or from Node.js. Your client will interact with the server to list meetings, get meeting details, fetch transcripts, and obtain highlights across supported platforms.

How to install

Prerequisites you need to prepare before installation: Node.js and npm for a Node.js installation, or Docker for a Docker-based setup. You also need a tl;dv Business or Enterprise account and a tl;dv API key.

docker build -t tldv-mcp-server .

Configure your MCP client to connect to the server. If you use Docker, the following example shows how to run the server with your tl;dv API key included as an environment variable.

{
  "mcpServers": {
    "tldv": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "--init",
        "-e",
        "TLDV_API_KEY=<your-tldv-api-key>",
        "tldv-mcp-server"
      ]
    }
  }
}

If you prefer a Node.js installation, build and run the server from source. First install dependencies, then build the project, and finally wire up your MCP client to the built server.

npm install
npm run build

Then configure your MCP client to point at the built server. Use the absolute path to the compiled entry point and provide your API key.

{
  "mcpServers": {
    "tldv": {
      "command": "node",
      "args": ["/absolute/path/to/tldv-mcp-server/dist/index.js"],
      "env": {
        "TLDV_API_KEY": "your_tldv_api_key"
      }
    }
  }
}

Additional configuration and tips

Development workflow encourages using a watch mode to auto-recompile on changes. Run the development server and reload your MCP client to apply changes.

npm install
cp .env.example .env
# Add your TLDV_API_KEY to .env
npm run watch

Tools and endpoints

The server provides the following capabilities across all supported platforms:

List Meetings: Retrieve meetings using filters such as query, date range, participation status, and type across all platforms.
Get Meeting Metadata: Fetch detailed information for a specific meeting by ID regardless of platform.
Get Transcript: Retrieve the transcript for a meeting by ID with consistent formatting across platforms.
Get Highlights: Obtain AI-generated highlights for meetings from any supported platform.
Import Meeting (Coming Soon): Import meetings via URL from any supported platform.

Available tools

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.

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

Prepare for upcoming functionality to import meetings via URL from any supported platform.