Skip to main content
Glama
Mouxy

Teams Transcript MCP

by Mouxy

Related Servers

Alternatives to Teams Transcript MCP

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      C
      maintenance
      Exposes meeting transcripts to any MCP-capable AI client so it can list meetings, page through a single transcript, and search across all of them for a topic with exact timestamps. Speaker labels, emails, phone numbers, and paths are pseudonymized or redacted before anything crosses the protocol, and transcripts are read-only.
      3
      MIT
    • F
      license
      Not graded
      quality
      D
      maintenance
      A remote Model Context Protocol server that retrieves and cleans Microsoft Teams meeting transcripts via the Microsoft Graph API using delegated OAuth 2.0 authentication. It enables AI agents to discover meetings, extract speaker-attributed text, and save transcripts to SharePoint for analysis and automation.
      27
      -
    • 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
      47 npm
      1
      MIT
    • 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
      93 npm
      1
      MIT

    TDQS

    A4.3/5.0

    Scored across 5 tools

    Disambiguation5/5

    Each tool maps to a distinct concern: authentication state, sign-in, sign-out, meeting listing, and transcript retrieval. No overlap or ambiguous selection between them.

    Naming Consistency4/5

    Four tools follow clear verb-based snake_case patterns (sign_in, sign_out, list_recent_meetings, get_transcript), while auth_status is a noun-phrase status query rather than get_auth_status. Naming is still consistent and predictable overall.

    Tool Count5/5

    Five tools is appropriate for a focused Teams transcript server: the auth lifecycle plus list/fetch covers the core task without bloat. Every tool earns its place.

    Completeness4/5

    The auth and transcript-retrieval workflows are well covered, and the transcript_status guidance prevents dead-end calls. The only minor gap is the lack of a direct meeting lookup or search outside the recent-meetings list.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues