tl;dv MCP server

The Official MCP Server for tl;dv API enables seamless interaction with the tl;dv API, providing a standardized interface for AI models and MCP clients to access meeting intelligence across Google Meet, Zoom, and Microsoft Teams. This integration allows you to retrieve, analyze, and derive insights from meetings across all major platforms in a 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
• Get Transcript: Obtain the transcript for any meeting ID with consistent formatting
• 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

Before installing the MCP server, ensure you have:

• A Business or Enterprise tl;dv account
• A tl;dv API key (request from tl;dv settings)
• Node.js & npm (for Node.js installation method)
• Docker (for Docker installation method)

Installation Options

Using Docker

1. Build the Docker image:

docker build -t tldv-mcp-server .

2. Configure your MCP Client: Update your MCP client's configuration file (e.g., claude_desktop_config.json):

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

1. Install dependencies:

npm install

2. Build the server:

npm run build

This command creates a dist folder containing the compiled server code (index.js).

3. 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.

Configuration Notes

After updating your configuration file, you will need to restart your MCP client for the changes to take effect. Refer to your specific MCP client's documentation for detailed setup instructions (e.g., Claude Tools).

Debugging Tips

If you encounter issues, consider these debugging approaches:

• Console Logs: Check the console output when running the server for detailed logs
• MCP Client Logs: Review the logs provided by your MCP client, which show the requests sent and responses received

Additional Resources

• tl;dv Developer API Documentation
• Model Context Protocol (MCP) Specification

How to add this MCP server to Cursor

There are two ways to add an MCP server to Cursor. The most common way is to add the server globally in the ~/.cursor/mcp.json file so that it is available in all of your projects.

If you only need the server in a single project, you can add it to the project instead by creating or adding it to the .cursor/mcp.json file.

Adding an MCP server to Cursor globally

To add a global MCP server go to Cursor Settings > MCP and click "Add new global MCP server".

When you click that button the ~/.cursor/mcp.json file will be opened and you can add your server like this:

{
    "mcpServers": {
        "cursor-rules-mcp": {
            "command": "npx",
            "args": [
                "-y",
                "cursor-rules-mcp"
            ]
        }
    }
}

Adding an MCP server to a project

To add an MCP server to a project you can create a new .cursor/mcp.json file or add it to the existing one. This will look exactly the same as the global MCP server example above.

How to use the MCP server

Once the server is installed, you might need to head back to Settings > MCP and click the refresh button.

The Cursor agent will then be able to see the available tools the added MCP server has available and will call them when it needs to.

You can also explictly ask the agent to use the tool by mentioning the tool name and describing what the function does.