Tl;dv MCP Server for Zoom, Google Meet and MS Teams

Created By

tldv-public8 months ago

Interact with your meeting data (to list, ask, summarize, extract - virtually anything about your meetings) through Claude’s desktop client across Zoom, Google Meet and MS Teams via tl;dv.

# zoom

# google meet

Overview Content Tools Comments

Content

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",

            "--rm",        
            "--init",      
            "-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 build

This command creates a dist folder 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.js with the correct absolute path to the built server file and your_tldv_api_key with 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 .env

Edit the .env file and add your TLDV_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 the TLDV_API_KEY is accessible, either through the client's env configuration or loaded via the .env file 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 dev for detailed logs. The server uses the debug library; 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.