meeting-recording-access-via-mcp, transcript-retrieval-and-search, meeting-summary-and-insights-retrieval, multi-platform-meeting-metadata-aggregation, mcp-protocol-transport-abstraction, oauth-credential-management-for-video-platforms

Tldv

MCP Server

** - Connect your AI agents to Google-Meet, Zoom & Microsoft Teams through [tl;dv](https://tldv.io)

/ 100

6 capabilities

Capabilities6 decomposed

meeting-recording-access-via-mcp

Medium confidence

Exposes Google Meet, Zoom, and Microsoft Teams meeting recordings and metadata through the Model Context Protocol (MCP), allowing AI agents to query and retrieve meeting data without direct API integration. The server acts as a unified abstraction layer that translates MCP tool calls into authenticated requests to the tl;dv backend service, which handles OAuth token management and platform-specific API translation for each video conferencing provider.

Solves for

I want my AI agent to access meeting recordings from multiple platforms through a single standardized interfaceI need to retrieve meeting metadata and recordings programmatically without managing separate OAuth flows for each platformI want to integrate meeting data into my agent's context without building custom API connectors for Google Meet, Zoom, and Teams

Best for

AI agent developers building multi-platform meeting analysis workflows

Teams building internal tools that need to access meeting recordings across Google Workspace, Microsoft 365, and Zoom

Developers integrating meeting intelligence into LLM-powered applications

Requires

tl;dv account with active subscription

OAuth credentials configured for at least one of: Google Workspace, Microsoft 365, or Zoom

MCP-compatible client (Claude Desktop, custom agent framework, etc.)

Limitations

Requires active tl;dv account with authenticated connections to each platform (Google Meet, Zoom, Teams) — cannot access recordings without prior setup

No built-in caching or local storage of recordings — all queries route through tl;dv service, introducing network latency

Read-only access to recordings; no capability to delete, modify, or re-upload meeting data

What makes it unique

Implements a unified MCP abstraction layer for three major video conferencing platforms (Google Meet, Zoom, Microsoft Teams) through tl;dv's backend, eliminating the need for agents to manage separate OAuth flows and platform-specific API differences. Uses tl;dv's existing recording infrastructure and transcription pipeline rather than requiring direct platform API access.

vs alternatives

Simpler than building custom integrations for each platform's API because tl;dv handles OAuth, transcription, and platform-specific translation; more accessible than raw platform APIs because it uses standardized MCP protocol instead of REST endpoints.

transcript-retrieval-and-search

Medium confidence

Retrieves full or partial meeting transcripts from tl;dv's indexed recording library and enables semantic or keyword-based search across meeting content. The MCP server translates search queries into tl;dv backend calls, which leverage pre-processed transcripts stored in tl;dv's database, returning matching segments with timestamps and speaker attribution for context-aware agent reasoning.

Solves for

I want to search across all my meeting transcripts to find discussions about a specific topicI need to retrieve exact quotes or segments from meetings with precise timestamps for my agent to referenceI want my agent to access meeting transcripts without downloading or storing full recording files locally

Best for

Knowledge workers building agents that need to reference past meeting discussions

Teams using AI to analyze meeting patterns, decisions, or action items across multiple recordings

Developers building meeting-aware chatbots or search interfaces

Requires

tl;dv account with at least one completed and processed recording

MCP client with transcript search tool support

Authenticated connection to tl;dv backend

Limitations

Search quality depends on tl;dv's transcription accuracy — OCR or speaker diarization errors will propagate to search results

No full-text indexing control from the MCP client — search capabilities limited to what tl;dv backend exposes

Transcript availability depends on recording completion and processing time — newly recorded meetings may not be immediately searchable

What makes it unique

Leverages tl;dv's pre-processed transcript database and indexing infrastructure rather than requiring agents to parse raw audio or video, enabling fast search across multiple meetings without local storage or processing overhead. Integrates speaker diarization and timestamp alignment from tl;dv's transcription pipeline.

vs alternatives

Faster than agents transcribing recordings on-demand because transcripts are pre-computed; more accurate than keyword-only search if tl;dv uses semantic indexing; eliminates need for agents to manage local transcript storage or search indices.

meeting-summary-and-insights-retrieval

Medium confidence

Retrieves AI-generated summaries, key points, action items, and meeting insights from tl;dv's analysis engine through MCP tool calls. The server queries tl;dv's backend for pre-computed summaries and structured insights derived from meeting transcripts and recordings, returning formatted data that agents can use for decision-making or context enrichment without re-analyzing the full recording.

Solves for

I want my agent to quickly understand the outcome and key decisions from a meeting without reading the full transcriptI need to extract action items and owners from meetings programmatically for task management integrationI want my agent to access meeting insights (decisions, risks, next steps) for downstream reasoning or reporting

Best for

Agents building automated meeting follow-up workflows or action item tracking

Teams using AI to synthesize insights from large numbers of meetings

Developers building meeting-aware project management or CRM integrations

Requires

tl;dv account with summary/insights feature enabled (may require premium tier)

Completed and processed recordings with analysis results available

MCP client supporting summary retrieval tools

Limitations

Summary quality depends on tl;dv's AI model and analysis pipeline — hallucinations or missed context possible

Insights are pre-computed and static — cannot customize summary length, focus, or analysis approach per query

Unknown whether summaries are available for all recordings or only recent/premium-tier meetings

What makes it unique

Exposes tl;dv's proprietary meeting analysis engine (which generates summaries, action items, and insights) through MCP, allowing agents to access pre-computed intelligence without running their own summarization models. Integrates tl;dv's multi-platform transcript processing and AI analysis pipeline.

vs alternatives

More efficient than agents summarizing transcripts themselves because analysis is pre-computed; more consistent than prompt-based summarization because it uses tl;dv's trained models; eliminates token overhead of passing full transcripts to LLMs for analysis.

multi-platform-meeting-metadata-aggregation

Medium confidence

Aggregates meeting metadata (participants, duration, date, platform source) across Google Meet, Zoom, and Microsoft Teams recordings through a unified MCP interface. The server queries tl;dv's backend to fetch and normalize metadata from each platform's API, presenting a consistent schema regardless of source platform, enabling agents to reason about meetings without platform-specific logic.

Solves for

I want to query all meetings across my organization's platforms (Google Meet, Zoom, Teams) with a single API callI need to filter or analyze meetings by participant, date, or duration without writing separate queries for each platformI want my agent to understand which platform a meeting came from without exposing platform-specific details

Best for

Enterprise teams using multiple video conferencing platforms

Agents building cross-platform meeting analytics or reporting

Developers building unified meeting management interfaces

Requires

tl;dv account with OAuth connections configured for desired platforms

MCP client supporting metadata query tools

Authenticated access to tl;dv backend

Limitations

Metadata normalization may lose platform-specific fields or capabilities (e.g., Zoom breakout rooms, Teams recording settings)

Metadata freshness depends on tl;dv's sync frequency — real-time updates not guaranteed

Requires OAuth setup for each platform independently — cannot access meetings from platforms without configured credentials

What makes it unique

Normalizes metadata across three major platforms (Google Meet, Zoom, Teams) into a unified schema through tl;dv's backend, eliminating the need for agents to handle platform-specific metadata structures or API differences. Uses tl;dv's existing OAuth infrastructure and platform connectors.

vs alternatives

Simpler than querying each platform's API separately because it abstracts platform differences; more maintainable than custom normalization logic because tl;dv handles platform API changes; enables cross-platform queries that would require multiple API calls otherwise.

mcp-protocol-transport-abstraction

Medium confidence

Implements the Model Context Protocol (MCP) server specification, translating MCP tool calls and resource requests into tl;dv backend API calls and returning results in MCP-compliant formats. The server handles MCP transport (stdio, SSE, or HTTP), request/response serialization, and error handling, allowing any MCP-compatible client (Claude Desktop, custom agents, etc.) to interact with tl;dv meeting data without direct API knowledge.

Solves for

I want to use Claude or another MCP client to access my tl;dv meetings without writing custom API codeI need to integrate tl;dv into my existing MCP-based agent frameworkI want to expose tl;dv capabilities to multiple clients through a standardized protocol

Best for

Developers building MCP-compatible agents or tools

Teams using Claude Desktop or other MCP clients who want tl;dv integration

Organizations standardizing on MCP for AI tool integration

Requires

MCP-compatible client (Claude Desktop, custom MCP framework, etc.)

Node.js or runtime environment supporting the MCP server implementation

Network connectivity to tl;dv backend service

Limitations

MCP transport type (stdio, SSE, HTTP) unknown — may limit deployment scenarios

Error handling and timeout behavior not documented — unknown how server handles tl;dv backend failures

No built-in request queuing or retry logic documented — transient failures may propagate to clients

What makes it unique

Implements the MCP server specification to expose tl;dv as a standardized tool for any MCP-compatible client, rather than requiring custom API bindings. Abstracts tl;dv's REST API behind MCP's tool/resource model, enabling protocol-agnostic client integration.

vs alternatives

More flexible than direct API integration because clients don't need tl;dv SDK knowledge; more portable than custom integrations because MCP is a standard protocol; enables use with Claude Desktop and other MCP clients without custom code.

oauth-credential-management-for-video-platforms

Medium confidence

Manages OAuth authentication flows and credential storage for Google Meet, Zoom, and Microsoft Teams through tl;dv's backend, allowing agents to access recordings without storing or managing platform-specific API keys. The MCP server delegates authentication to tl;dv's OAuth handlers, which refresh tokens and maintain secure credential storage, exposing only authenticated meeting data to the agent.

Solves for

I want my agent to access meetings from multiple platforms without managing separate OAuth tokensI need secure credential storage for video platform integrations without exposing keys to my agent codeI want to set up platform access once in tl;dv and reuse it across multiple agents or tools

Best for

Teams managing multi-platform meeting access across multiple agents

Developers building agents that need secure, centralized credential management

Organizations with compliance requirements for API key storage and rotation

Requires

tl;dv account with OAuth app credentials configured for each platform

User authorization completed in tl;dv UI for Google Meet, Zoom, and/or Teams

Active OAuth tokens maintained by tl;dv backend

Limitations

Credential management is opaque — no visibility into token refresh cycles or expiration handling

OAuth setup must be completed in tl;dv UI before MCP server can access meetings — no programmatic OAuth flow from MCP client

Token revocation or permission changes in source platforms may not propagate immediately to MCP server

What makes it unique

Centralizes OAuth credential management in tl;dv's backend rather than requiring agents to handle token refresh, storage, or rotation. Provides agents with authenticated access to three platforms without exposing API keys or tokens, improving security posture.

vs alternatives

More secure than agents managing their own OAuth tokens because credentials are stored server-side; simpler than implementing OAuth flows in agent code because tl;dv handles token lifecycle; more maintainable than embedding platform-specific auth logic in multiple agents.

Capabilities are decomposed by AI analysis. Each maps to specific user intents and improves with match feedback.

Related Artifactssharing capabilities

Artifacts that share capabilities with Tldv, ranked by overlap. Discovered automatically through the match graph.

Product33

MinutesLink

AI tool automates meeting attendance, transcription, and...

searchable-meeting-archiveautomatic-meeting-audio-transcription

2 shared capabilities

Product32

Avoma

Revolutionize meetings with AI-driven automation and...

meeting-search-and-retrievalmeeting-recording-storage-and-access

2 shared capabilities

Product34

tl;dv

The meeting recorder that transcribes & summarizes your calls with customers, prospects, and your team....

meeting-recording-storage-and-accesstranscript-search-and-retrieval

2 shared capabilities

Product31

TMate

Revolutionize project management with AI-driven meeting insights and actionable...

meeting-content-search-and-retrieval

1 shared capability

Product33

Zoom AI Companion

Streamline meetings with AI summaries, chat assistance, and multilingual...

meeting-transcript-search-and-retrieval

1 shared capability

Product33

Circleback.ai

Streamline meeting notes and action items with AI, ensuring efficiency and data...

meeting-recording-storage-and-search

1 shared capability

Best For

✓AI agent developers building multi-platform meeting analysis workflows
✓Teams building internal tools that need to access meeting recordings across Google Workspace, Microsoft 365, and Zoom
✓Developers integrating meeting intelligence into LLM-powered applications
✓Knowledge workers building agents that need to reference past meeting discussions
✓Teams using AI to analyze meeting patterns, decisions, or action items across multiple recordings
✓Developers building meeting-aware chatbots or search interfaces
✓Agents building automated meeting follow-up workflows or action item tracking
✓Teams using AI to synthesize insights from large numbers of meetings

Known Limitations

⚠Requires active tl;dv account with authenticated connections to each platform (Google Meet, Zoom, Teams) — cannot access recordings without prior setup
⚠No built-in caching or local storage of recordings — all queries route through tl;dv service, introducing network latency
⚠Read-only access to recordings; no capability to delete, modify, or re-upload meeting data
⚠Rate limits and quota restrictions unknown — dependent on tl;dv service tier and platform API limits
⚠Search quality depends on tl;dv's transcription accuracy — OCR or speaker diarization errors will propagate to search results
⚠No full-text indexing control from the MCP client — search capabilities limited to what tl;dv backend exposes

Requirements

tl;dv account with active subscriptionOAuth credentials configured for at least one of: Google Workspace, Microsoft 365, or ZoomMCP-compatible client (Claude Desktop, custom agent framework, etc.)Network connectivity to tl;dv backend servicetl;dv account with at least one completed and processed recordingMCP client with transcript search tool supportAuthenticated connection to tl;dv backendtl;dv account with summary/insights feature enabled (may require premium tier)

Input / Output

Accepts: meeting identifiers (platform-specific IDs or URLs), query parameters (date range, participant filters, etc.), structured MCP tool call schemas, search query strings (keywords or phrases), optional filters (date range, participants, meeting title), structured search parameters (if MCP schema supports), meeting identifiers or recording IDs, optional parameters (summary type, detail level, if configurable), filter parameters (date range, participant name, platform type, meeting title), pagination parameters (limit, offset), structured query schemas (if MCP supports), MCP tool call requests with parameters, MCP resource read/list requests, MCP protocol messages (initialization, capability negotiation), platform selection (Google Meet, Zoom, Teams), optional scope/permission parameters (if configurable)

Produces: meeting metadata (title, participants, duration, timestamps), transcript text or structured transcript objects, recording URLs or streaming endpoints, summary or key points (if tl;dv service provides), transcript segments with timestamps, speaker attribution and turn-taking data, relevance scores or match confidence (if provided), meeting metadata linked to transcript matches, structured summary text, action items with owner/assignee information, key decisions or discussion points, risk flags or follow-up items, meeting metadata and timestamp references, normalized meeting metadata objects, participant lists with roles/permissions, recording availability status, platform source attribution, timestamps and duration information, MCP tool call results with structured data, MCP resource content (text, JSON, etc.), MCP protocol responses and error messages, authenticated access to platform-specific meeting data, implicit token management (no tokens exposed to MCP client)

UnfragileRank

Adoption15%(25% weight)

Quality14%(25% weight)

Ecosystem15%(15% weight)

Match Graph25%(30% weight)

Freshness75%(5% weight)

UnfragileRank is computed from adoption signals, documentation quality, ecosystem connectivity, match graph feedback, and freshness. No artifact can pay for a higher rank.

Type: MCP Server

6 capabilities

Visit Tldv→

About

** - Connect your AI agents to Google-Meet, Zoom & Microsoft Teams through [tl;dv](https://tldv.io)

Alternatives to Tldv

IntelliCode46Extension

AI-assisted development

Compare →

GitHub Copilot Chat49Extension

AI chat features powered by Copilot

Compare →

GitHub Copilot48Extension

Your AI pair programmer

Compare →

Claude Code for VS Code48Extension

Claude Code for VS Code: Harness the power of Claude Code without leaving your IDE

Compare →

Are you the builder of Tldv?

Claim this artifact to get a verified badge, access match analytics, see which intents users search for, and manage your listing.

Claim this artifact →Verification via email

Get the weekly brief

New tools, rising stars, and what's actually worth your time. No spam.

Data Sources

github awesome

Looking for something else?

Search →

Capabilities6 decomposed

meeting-recording-access-via-mcp

Medium confidence

Solves for

Best for

AI agent developers building multi-platform meeting analysis workflows

Teams building internal tools that need to access meeting recordings across Google Workspace, Microsoft 365, and Zoom

Developers integrating meeting intelligence into LLM-powered applications

Requires

tl;dv account with active subscription

OAuth credentials configured for at least one of: Google Workspace, Microsoft 365, or Zoom

MCP-compatible client (Claude Desktop, custom agent framework, etc.)

Limitations

Requires active tl;dv account with authenticated connections to each platform (Google Meet, Zoom, Teams) — cannot access recordings without prior setup

No built-in caching or local storage of recordings — all queries route through tl;dv service, introducing network latency

Read-only access to recordings; no capability to delete, modify, or re-upload meeting data

What makes it unique

vs alternatives

transcript-retrieval-and-search

Medium confidence

Solves for

Best for

Knowledge workers building agents that need to reference past meeting discussions

Teams using AI to analyze meeting patterns, decisions, or action items across multiple recordings

Developers building meeting-aware chatbots or search interfaces

Requires

tl;dv account with at least one completed and processed recording

MCP client with transcript search tool support

Authenticated connection to tl;dv backend

Limitations

Search quality depends on tl;dv's transcription accuracy — OCR or speaker diarization errors will propagate to search results

No full-text indexing control from the MCP client — search capabilities limited to what tl;dv backend exposes

Transcript availability depends on recording completion and processing time — newly recorded meetings may not be immediately searchable

What makes it unique

vs alternatives

meeting-summary-and-insights-retrieval

Medium confidence

Solves for

Best for

Agents building automated meeting follow-up workflows or action item tracking

Teams using AI to synthesize insights from large numbers of meetings

Developers building meeting-aware project management or CRM integrations

Requires

tl;dv account with summary/insights feature enabled (may require premium tier)

Completed and processed recordings with analysis results available

MCP client supporting summary retrieval tools

Limitations

Summary quality depends on tl;dv's AI model and analysis pipeline — hallucinations or missed context possible

Insights are pre-computed and static — cannot customize summary length, focus, or analysis approach per query

Unknown whether summaries are available for all recordings or only recent/premium-tier meetings

What makes it unique

vs alternatives

multi-platform-meeting-metadata-aggregation

Medium confidence

Solves for

Best for

Enterprise teams using multiple video conferencing platforms

Agents building cross-platform meeting analytics or reporting

Developers building unified meeting management interfaces

Requires

tl;dv account with OAuth connections configured for desired platforms

MCP client supporting metadata query tools

Authenticated access to tl;dv backend

Limitations

Metadata normalization may lose platform-specific fields or capabilities (e.g., Zoom breakout rooms, Teams recording settings)

Metadata freshness depends on tl;dv's sync frequency — real-time updates not guaranteed

Requires OAuth setup for each platform independently — cannot access meetings from platforms without configured credentials

What makes it unique

vs alternatives

mcp-protocol-transport-abstraction

Medium confidence

Solves for

Best for

Developers building MCP-compatible agents or tools

Teams using Claude Desktop or other MCP clients who want tl;dv integration

Organizations standardizing on MCP for AI tool integration

Requires

MCP-compatible client (Claude Desktop, custom MCP framework, etc.)

Node.js or runtime environment supporting the MCP server implementation

Network connectivity to tl;dv backend service

Limitations

MCP transport type (stdio, SSE, HTTP) unknown — may limit deployment scenarios

Error handling and timeout behavior not documented — unknown how server handles tl;dv backend failures

No built-in request queuing or retry logic documented — transient failures may propagate to clients

What makes it unique

vs alternatives

oauth-credential-management-for-video-platforms

Medium confidence

Solves for

Best for

Teams managing multi-platform meeting access across multiple agents

Developers building agents that need secure, centralized credential management

Organizations with compliance requirements for API key storage and rotation

Requires

tl;dv account with OAuth app credentials configured for each platform

User authorization completed in tl;dv UI for Google Meet, Zoom, and/or Teams

Active OAuth tokens maintained by tl;dv backend

Limitations

Credential management is opaque — no visibility into token refresh cycles or expiration handling

OAuth setup must be completed in tl;dv UI before MCP server can access meetings — no programmatic OAuth flow from MCP client

Token revocation or permission changes in source platforms may not propagate immediately to MCP server

What makes it unique

vs alternatives

Capabilities are decomposed by AI analysis. Each maps to specific user intents and improves with match feedback.

Alternatives to Tldv

IntelliCode46Extension

AI-assisted development

Compare →

GitHub Copilot Chat49Extension

AI chat features powered by Copilot

Compare →

GitHub Copilot48Extension

Your AI pair programmer

Compare →

Claude Code for VS Code48Extension

Claude Code for VS Code: Harness the power of Claude Code without leaving your IDE

Compare →

Tldv

Capabilities6 decomposed

meeting-recording-access-via-mcp

transcript-retrieval-and-search

meeting-summary-and-insights-retrieval

multi-platform-meeting-metadata-aggregation

mcp-protocol-transport-abstraction

oauth-credential-management-for-video-platforms

Related Artifactssharing capabilities

MinutesLink

Avoma

tl;dv

TMate

Zoom AI Companion

Circleback.ai

Best For

Known Limitations

Requirements

Input / Output

UnfragileRank

About

Categories

Alternatives to Tldv

Are you the builder of Tldv?

Get the weekly brief

Data Sources

Tldv

Capabilities6 decomposed

meeting-recording-access-via-mcp

transcript-retrieval-and-search

meeting-summary-and-insights-retrieval

multi-platform-meeting-metadata-aggregation

mcp-protocol-transport-abstraction

oauth-credential-management-for-video-platforms

Related Artifactssharing capabilities

MinutesLink

Avoma

tl;dv

TMate

Zoom AI Companion

Circleback.ai

Best For

Known Limitations

Requirements

Input / Output

UnfragileRank

About

Categories

Alternatives to Tldv

Are you the builder of Tldv?

Get the weekly brief

Data Sources