How to Connect Meeting Notes to Claude MCP Using tl;dv

TL;DR

Claude can’t join your calls, so it can’t answer questions about a meeting it never saw a transcript of. MCP fixes that by giving Claude a live line into your meeting data instead of a pasted-in wall of text.

Path	Tempo de configuração	O que você recebe	Who it's for
tl;dv directory connector	Under a minute	5 tools, hosted at mcp.tldv.io	Most people, most of the time
tl;dv self-hosted MCP server	15–20 minutes	4 tools, code you can read before it runs	Teams who want to see how it works and control it themselves

tl;dv connects to Claude two ways: a one-click directory connector for fast setup, or an open-source MCP server you run yourself for full tool access and full visibility into what it’s doing. I set up and timed the self-hosted route myself, tool by tool, and tested the actual output against a real meeting to confirm it wasn’t guessing. Both paths, step by step, below.

This guide shows how to connect meeting notes to Claude MCP using tl;dv, so Claude can work directly with your meeting data instead of relying on transcripts you manually paste into chat.

How MCP Works with Claude

Claude works with text and has no record of your meetings unless you connect a tool. MCP (Model Context Protocol) is the standard Anthropic built for that. It gives Claude a way to reach a tool like tl;dv and pull real meeting data directly into the conversation, rather than relying on transcripts you paste in manually.

The protocol is open, not exclusive to Claude. The same standard powers connectors for Voicenotes, Zoho, and many other AI assistants, which is why tl;dv only had to build one MCP server instead of a separate integration for every chatbot. tl;dv MCP server launched in 2025, before the directory connector existed. The same server that talks to Claude works with any other MCP-compatible client too.

How to Connect Meeting Notes to Claude with tl;dv

You can choose the directory connector if you want to be set up in a couple of clicks. Choose the self-hosted server if you’d rather run the code yourself and see what it does before it connects to your account. Both connect Claude to your tl;dv meeting library, but they expose slightly different tools and have different tl;dv plan requirements.

Anthropic’s docs on connectors to extend Claude’s capabilities confirm connectors are available on every Claude plan, including free. Any plan requirement you run into comes from tl;dv, not Claude.

This guide covers tl;dv’s two connectors. For the general steps of linking any tool this way, see our guide on how to add a custom connector in Claude.

Option 1: The Directory Connector

tl;dv is listed in Claude’s connectors directory with a verified badge, running on a hosted server at mcp.tldv.io/mcp. Connecting it works the same way as connecting Gmail or Notion, and it includes five tools, one more than the self-hosted route below. You need a tl;dv Pro plan or higher to use it. Free accounts see an upgrade prompt instead of the connect option.

Ferramenta	O que faz
`search-meetings`	Find meetings by keyword, date, or participant
`get-meeting-transcript`	Full transcript for a specific meeting, speaker-labeled
`get-meeting-notes`	AI-generated meeting notes, organized by topic
`get-meeting-metadata`	Details for one meeting by ID: date, duration, attendees
`get-user-profile`	Pulls your tl;dv account info

In Claude, open the + button or Customize > Connectors, and search tldv.
Click Connect to Claude. This opens the tl;dv MCP consent screen and asks you to sign in to your tl;dv account.
Before you click through, read what it’s asking for: the consent screen lists meeting metadata, meeting transcripts, and meeting notes as what it can access. Click Grant access.

Once it’s connected, you can ask things like “summarize yesterday’s client call” or “find every meeting where we talked about pricing,” and Claude pulls the answer from your library, the same way it would for any other connected app like Gmail or Google Drive.

Option 2: The Self-Hosted MCP Server

This is the route I set up and ran for this guide. It’s open source (github.com/tldv-public/tldv-mcp-server) and connects through Claude Desktop rather than the web directory, so it won’t appear in the Connectors directory on claude.ai. It has four tools, one fewer than the directory connector, because it doesn’t include the profile lookup:

Ferramenta	O que faz
List meetings	Filter by date, keyword, or participants across Zoom, Meet, and Teams
Get meeting metadata	Pull details for one specific meeting by ID
Get transcript	Full transcript, consistent formatting across platforms
Get highlights	AI-generated highlights for a meeting, timestamped against the recording

Here’s what you need before you start. The Business or Enterprise requirement exists because the connector uses the same API that powers tl;dv’s reporting and admin tools, which are part of those higher tiers.

Before you start:

Requirement	Detail
tl;dv conta	Business or Enterprise (stated directly in the repo)
tl;dv API key	Generate under Settings → Personal Settings → API Keys
Node.js and npm, or Docker	I tested the Node.js path
Claude Desktop	Free to use. No plan requirement for local config-based servers

You’ll generate the API key from your tl;dv settings, and the pricing page confirms your tier if you’re unsure whether you’re on Business or Enterprise.

Step 1: Clone it and install

				
					git clone https://github.com/tldv-public/tldv-mcp-server.git
cd tldv-mcp-server
npm install

I timed this: 236 packages, 8–9 seconds. One thing the README doesn’t mention is that npm install also runs the build automatically through a prepare hook, so you end up with a compiled server, not just a node_modules folder.

Before you connect any MCP server to your account, run npm audit and read what it reports. It’s a quick check for something that will hold your API key.

Step 2: Confirm the build

Check for dist/index.js:

				
					ls dist/

I also tried running the server without an API key set, to see what would happen. It failed right away with a clear error naming the missing field, rather than a vague crash or an empty result. That means a setup mistake shows up clearly instead of leaving you to figure it out.

Step 3: Get your absolute path

Claude Desktop needs the full path to the built file, not a relative one:

pwd

Add /dist/index.js to whatever that returns. On macOS or Linux, pwd alone gives you the directory. On Windows, use the full path shown in File Explorer’s address bar instead, since Windows paths use backslashes and the JSON config needs them escaped.

Step 4: Edit the Claude Desktop config

Go to Settings → Developer → Edit Config in Claude Desktop, following Anthropic’s guide on local MCP servers on Claude Desktop. This opens (or creates) claude_desktop_config.json:

Add tl;dv as a server:

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

Prefer Docker? The repo supports that too. Build the image with docker build -t tldv-mcp-server., then replace node with docker run in the config and pass the API key as an environment variable. One difference in the Dockerfile: it runs npm ci --ignore-scripts and builds separately, so the automatic prepare hook from Step 1 doesn’t apply here.

Step 5: Restart and check the connection

Fully quit Claude Desktop, not just the window, then reopen it, because config changes only load on a full restart. Open a new chat, check the Connectors panel to confirm tl;dv is active, and ask Claude to use it. The first time it runs a tool, you’ll get a permission prompt naming the tool it wants to use. Approve it once, or set it to always allow so you don’t have to approve it every session. The prompt applies to one tool at a time, not the whole server at once.

I tested this with “What did we cover in my last meeting?” Claude named the meeting, gave the date, and pulled three points directly from the transcript. When the details match your real transcript, the connection is working. If Claude gives a generic or vague answer with no specific names or dates, check that the connector shows as active in the Connectors panel first, since that’s the most common cause.

So, What Can You Ask Claude?

You don’t need any special commands. You can ask in normal, everyday language, whether you’re in a regular chat, working inside Claude Projects, or handing the task to Claude Cowork. Claude works out which tool to use based on your question.

The last example is the one a single pasted transcript can’t handle: reasoning across several meetings in one answer. You can get more specific too. “Find every meeting in the last 30 days where we discussed contract renewal” is a valid search-meetings query. So is “Get the transcript from my call with [name] on [date] and pull out any action items they committed to.” The more specific the question, the more directly Claude can map it to a single tool call rather than chaining several.

How Claude Handles a Cross-Meeting Question

Say you ask, “Have [client]’s priorities shifted over our last five calls?” Claude calls search-meetings filtered to that client, gets back five meeting IDs, then calls get-meeting-transcript or get-meeting-notes on each one in turn. Once it has all five, it reads across them and answers the question. That’s five separate API calls before you see a response. The permission prompt on your first call each session names the specific tool being called, not the whole server, so you can see exactly what’s running.

tl;dv vs Tactiq vs Noota vs Zoom for Claude

Zoom’s connector is the quickest to set up if you’re fully on Zoom with AI Companion turned on, but it only sees Zoom meetings. Our tl;dv vs Zoom AI Companion comparison covers the two in more detail. For what wider Zoom MCP support would involve, or a standalone Zoom AI Companion review, both are worth reading. tl;dv vs Tactiq and Noota are as quick to set up as tl;dv’s directory connector on the Claude side. tl;dv adds coverage across all three platforms and the option to self-host and read the code, which none of the tl;dv alternatives currently offer. A few other meeting tools, including Fellow and MeetGeek, also run their own directory connectors, and the setup steps are close to identical across all of them. If you’re choosing between tl;dv’s two routes, start with the directory connector, since it’s faster and covers what most people need. Use the self-hosted server if you want to read the code first or need a tool the directory connector doesn’t include. Neither adds a cost beyond the tl;dv and Claude plans you already pay for.

What tl;dv's Connector Can and Can't Do

Giving an AI assistant access to meeting transcripts is something that can feel uneasy (especially when you have confidential information being discussed.) The important questions are what Claude can access, what actions the connector can perform, and whether you can revoke that access later. With tl;dv, those boundaries are relatively easy to inspect.

Both routes are read-only. None of the nine tools across the two servers (list-meetings, search-meetings, get-transcript, get-meeting-notes, get-meeting-metadata, get-highlights, get-user-profile) can edit, delete, or create anything in your tl;dv account.

So, Claude can indeed read your data, but it can’t change it. It can’t rename a meeting, delete a recording, or change a transcript, even if you ask, because there’s no tool on either server that does that.

You can confirm this yourself: the directory connector’s consent screen lists the exact access it’s requesting before you approve it, tl;dv’s security commitment page explains the encryption and certification behind it, and the self-hosted server’s code is public, so you can check that no write or delete function exists.

Revoking access is different for each route:

Route	How to revoke
Directory connector	In Claude, go to Customize > Connectors, find tl;dv, and click Disconnect. Or revoke from tl;dv's own account settings under connected apps
Self-hosted server	Delete or rotate the tl;dv API key from Settings → Personal Settings → API Keys, then remove the tldv block from claude_desktop_config.json and restart

Either way, revoking access on tl;dv’s side ends the connection even if you don’t change anything in Claude, because the API key or OAuth token stops working.

Setting this up for a team works differently from connecting it yourself. For a company-wide rollout on Team or Enterprise, an Owner or Primary Owner first enables the connector at Organization settings > Connectors. Each person then authenticates their own tl;dv account before they can use it. Enabling it for the organization doesn’t automatically give anyone access.

Updating or Removing Either Connector Later

When tl;dv releases a new version of the self-hosted server, it doesn’t update on its own. Pull the latest code with git pull, run npm install again, and restart Claude Desktop. The directory connector updates on its own, because Anthropic and tl;dv push changes to the hosted mcp.tldv.io server for you. To remove the directory connector, go to Customize > Connectors > tl;dv > Disconnect. To remove the self-hosted one, delete its block from the config file and restart, or delete the tldv-mcp-server folder if you no longer need it.

Troubleshooting tl;dv's Claude MCP Connection

Problema	Likely cause
Claude shows the server as disconnected	Relative path in the config instead of an absolute one, or Claude Desktop wasn't fully restarted after the edit
Server fails to start	TLDV_API_KEY set in a local.env file the server can't see, instead of the config's env block
Tool calls return no meetings	API key belongs to a Pro account, not Business or Enterprise, or the key was copied with extra whitespace
Config changes don't take effect	Needs a full app restart, not just a new chat window
Docker container exits immediately	Missing TLDV_API_KEY in the docker run environment flags, same root cause as the Node.js path
Directory connector shows connected but returns nothing	tl;dv account's Pro plan lapsed or downgraded, so check whether the upgrade prompt reappears when you open tl;dv directly

Connect Your Meeting Notes to Claude with MCP

Connecting meeting notes to Claude with MCP removes the need to hunt through transcripts or paste meeting context into every new chat. For most users, tl;dv’s directory connector is the quickest route. If you want more control over how the connection works, the open-source MCP server gives you that option too.

Either way, Claude can work directly with your meeting history, making it far more useful for finding decisions, comparing conversations, and spotting changes across calls.

FAQs About Connect Meeting Notes to Claude

What plan do I need, on Claude's side and tl;dv's side?

Claude doesn’t require a paid plan for either route. Connectors are available on every Claude plan, including free. tl;dv does require a paid plan: the directory connector needs tl;dv Pro or higher, and the self-hosted server needs Business or Enterprise, because that’s the tier the API key belongs to.

Is my meeting data used to train Claude or tl;dv's models?

No, customer content, including recordings, transcripts, and notes, isn’t used to train, fine-tune, or improve any AI model, for tl;dv or any third party. Metadata shared with Anthropic to process a meeting is anonymized first, and meetings are processed in chunks rather than sent as one continuous file.

Is the self-hosted MCP server safer than the directory connector?

It’s a different setup, not automatically safer. The directory connector runs on tl;dv’s own hosted server (mcp.tldv.io), and the consent screen shows what it can access before you approve it. The self-hosted route is for people who want to read the server code themselves before connecting it, which takes about fifteen extra minutes to set up.

Does it work on Claude's mobile app?

The directory connector does. Connect it once on web or desktop, and it will be available in Claude for iOS and Android the next time you log in. The self-hosted server works on Desktop only, because it runs on your own machine.

Can I connect tl;dv and Tactiq or Noota at the same time?

Yes. Connectors work alongside each other. Claude picks whichever one fits your question, or you can name the one you want if you have more than one meeting tool connected. That can help if your team is still comparing Tactiq alternatives and hasn’t decided yet.

How to Connect Meeting Notes to Claude with MCP