MCP.so
Sign In

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

@tldv-public

Basic information

Category

Communication

Transports

stdio

Author

tldv-public

Submitted by

Pedro Marzagão

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

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.

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

Add this server to your MCP-compatible client using the configuration below.

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

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

Tool list not available yet

This listing does not currently have a tool list to display. This does not mean the server has no tools; check its documentation for supported capabilities.

We auto-extract tools from the README. The maintainer can list them under a ## Tools heading to populate this section.

Overview

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

An MCP server that connects to the tl;dv meeting intelligence platform, enabling AI-driven access to meeting data from Zoom, Google Meet, and Microsoft Teams. It is designed for users of MCP-compatible clients (e.g., Claude Desktop, Cursor) who want to leverage meeting transcripts, summaries, and insights in their AI workflows.

How to use Tl;dv MCP Server for Zoom, Google Meet and MS Teams?

Run the server via Docker (build the image and run with TLDV_API_KEY) or Node.js (install dependencies, build, then point your MCP client to the compiled dist/index.js). Configure your client’s JSON config file (e.g., claude_desktop_config.json) with the server command and environment variable TLDV_API_KEY. After updating the config, kill and restart your MCP client for changes to take effect.

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

  • Connects to tl;dv’s meeting intelligence API
  • Supports deployment via Docker or Node.js
  • Works with MCP-compatible clients (Claude, Cursor)
  • Requires only a tl;dv API key for configuration

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

—

Frequently asked questions

1

What API key is needed?

A valid tl;dv API key (`TLDV_API_KEY`) is required. It must be passed as an environment variable in the Docker command or in the MCP client’s env configuration.

2

How do I install the server?

You can install using Docker (build the image and run it) or Node.js (run `npm install` and `npm run build` to produce the server in the `dist` folder).

3

Where do I configure the MCP client?

Update your MCP client’s configuration file (e.g., `claude_desktop_config.json`) with the server command, arguments, and the `TLDV_API_KEY` environment variable. The exact path and format depend on the client.

4

How do I restart the client after configuration changes?

You must kill the MCP client process and restart it for the new configuration to be applied.

5

Is there a development mode?

Yes. Run `npm run watch` to start the server with auto-reloading. For debugging, set `DEBUG=tldv-mcp:*` or use Node.js debugging tools (`node --inspect`).

Comments

More Communication MCP servers