Meet MCP Server
Related Servers
Alternatives to Meet MCP Server
No user-submitted related servers found.
Related Servers
- FlicenseBqualityCmaintenanceEnables 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.242-
- AlicenseNot gradedqualityFmaintenanceProvides read-only access to Google Drive meeting transcripts and Google Calendar events, enabling AI assistants to search, analyze, and retrieve meeting insights.69 npm3MIT
- AlicenseNot gradedqualityBmaintenanceOpen-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.4 npm2,811Apache 2.0
- AlicenseAqualityBmaintenanceEnables listing a signed-in user's recent meetings and retrieving speaker-attributed transcripts or raw WebVTT through Microsoft Graph with secure delegated authentication.5MIT
- AlicenseAqualityDmaintenanceEnables access to Fireflies.ai meeting transcripts with capabilities to retrieve, search, filter, and generate AI-powered summaries of meeting content through the Fireflies API.465 npm1MIT
- AlicenseAqualityDmaintenanceRead-only access to your Gilbert meetings, transcripts and summaries over MCP — list, search, and fetch transcripts and summaries.523 npm1MIT
TDQS
Scored across 8 tools
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.
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.
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.
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.