Skip to main content
Glama
Sign In
Meet MCP Server

Meet MCP Server

by silkweave
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to Meet MCP Server

No user-submitted related servers found.

    Related Servers

    • Google Calendar and Meet MCP

      INSIDE-HAIR
      A
      license
      B
      quality
      C
      maintenance
      Enables comprehensive Google Meet and Calendar management through Google Calendar API v3 and Google Meet API v2, supporting calendar event creation with Meet links, space management, transcription, recording, attendance tracking, and meeting moderation controls.
      24
      2
      ISC
    • Vexa

      Vexaofficial

      Vexa-ai
      A
      license
      Not graded
      quality
      B
      maintenance
      Open-source meeting bot API with MCP server. Search, retrieve, and analyze meeting transcripts from Google Meet, Zoom, and Microsoft Teams directly from your AI tools.
      5 npm
      2,938
      Apache 2.0

    • Fireflies MCP Server

      cassler
      A
      license
      A
      quality
      D
      maintenance
      Enables access to Fireflies.ai meeting transcripts with capabilities to retrieve, search, filter, and generate AI-powered summaries of meeting content through the Fireflies API.
      4
      210 npm
      1
      MIT

    • gilbert-mcp

      HugoF1234
      A
      license
      A
      quality
      D
      maintenance
      Read-only access to your Gilbert meetings, transcripts and summaries over MCP — list, search, and fetch transcripts and summaries.
      5
      69 npm
      1
      MIT
    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

    A3.9/5.0

    Scored across 8 tools

    Disambiguation4/5

    The live vs persisted transcript distinction is clear between MeetTranscriptGet/List and TranscriptGet/List, though the names are similar enough to cause slight hesitation. Backfill, Reembed, Search, and Status are distinct services.

    Naming Consistency4/5

    All names use camelCase and follow an object-action pattern, but the prefix varies (McpStatus vs MeetTranscript* vs Transcript*). The 'Meet' prefix inconsistently indicates live Google data, while plain 'Transcript' indicates persisted data.

    Tool Count5/5

    Eight tools is a well-scoped count for managing Meet transcript ingestion, retrieval, search, and embedding. Each tool addresses a distinct stage in the transcript lifecycle without bloat.

    Completeness4/5

    The toolset covers the core lifecycle: list, get, backfill, persist, search, and embed. Missing delete/update operations for persisted transcripts are minor gaps, as they may not be core to the server's purpose.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources