Skip to main content
Glama
tldv-public

tl;dv MCP for Zoom, Google Meet and MS Teams

Official
by tldv-public
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to tl;dv MCP for Zoom, Google Meet and MS Teams

No user-submitted related servers found.

    Related Servers

    • Plaud MCP

      Humanly-Labs
      A
      license
      Not graded
      quality
      D
      maintenance
      Bring your Plaud Note recordings into Claude Desktop. Search meetings, pull transcripts, and ask Claude about your notes — directly from chat.
      1
      MIT

    • OmniContext

      h4sht
      A
      license
      A
      quality
      B
      maintenance
      Connects Claude Desktop to Notion and YouTube transcripts with one-click installation, enabling natural language queries about your pages and video content.
      5
      2
      MIT

    • GranolaAI MCP Server

      proofsh
      A
      license
      Not graded
      quality
      C
      maintenance
      Bridges Granola.ai meeting intelligence with Claude Desktop, enabling natural language access to meeting transcripts, notes, and insights.
      95
      MIT

    • Granola MCP Server

      maxgerlach1
      A
      license
      A
      quality
      C
      maintenance
      Integrates local Granola.ai meeting intelligence with Claude Desktop to enable searching and analyzing meeting transcripts, notes, and summaries. Users can perform natural language queries to retrieve meeting details, analyze participant patterns, and access full speaker-identified conversations.
      5
      MIT

    • DevDocs MCP Server

      cyberagiinc
      A
      license
      Not graded
      quality
      F
      maintenance
      Integrates with Claude to enable intelligent querying of documentation data, transforming crawled technical documentation into an actionable resource that LLMs can directly interact with.
      2,104
      Apache 2.0
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    B3.2/5.0

    Scored across 4 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: get-highlights retrieves highlights, get-meeting-metadata provides metadata, get-transcript fetches the transcript, and list-meetings lists meetings with filters. There is no overlap in functionality, making it easy for an agent to select the correct tool.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern (e.g., get-highlights, get-meeting-metadata, get-transcript, list-meetings). The naming is uniform and predictable, using snake_case throughout with clear action prefixes.

    Tool Count4/5

    With 4 tools, the count is reasonable for a meeting-focused server, covering key operations like listing, retrieving metadata, transcripts, and highlights. It is slightly lean but well-scoped, as each tool serves a distinct purpose without being overwhelming.

    Completeness4/5

    The tool set covers essential read operations for meetings (list, metadata, transcript, highlights), which aligns well with the server's purpose of accessing meeting data. A minor gap exists in write operations (e.g., creating or updating meetings), but agents can still perform core workflows effectively.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources