migas-mcp
Related Servers
Alternatives to migas-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityFmaintenanceProvides read-only access to Google Drive meeting transcripts and Google Calendar events, enabling AI assistants to search, analyze, and retrieve meeting insights.12,723 npm2MIT
- AlicenseNot gradedqualityAmaintenanceProvides read-only access to what you have dictated and what was said in your recorded meetings, so coding agents like Codex, Claude Code, Pi or LM Studio can search your local transcripts and notes.MIT
- FlicenseNot gradedqualityBmaintenanceEnables an AI agent to list, read, and search local meeting transcript files, returning structured transcript information and search hits. The server enforces read-only access confined to a transcripts directory with .txt and .md files only.-
- AlicenseAqualityCmaintenanceExposes 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.3MIT
- AlicenseNot gradedqualityBmaintenanceEnables MCP-capable agents to browse, search, and retrieve Meetily meeting transcripts and summaries on demand through read-only tools.1MIT
- AlicenseAqualityCmaintenanceProvides read-only access to finished meeting transcripts for AI assistants like Claude Code or Codex, enabling them to answer questions or draft summaries based on the transcriptions.43Apache 2.0
TDQS
Scored across 5 tools
Each tool has a clearly distinct purpose: listing meetings, retrieving a transcript, searching transcripts, finding speakers, and aggregating speaker contributions. There is no functional overlap or ambiguity between tools.
All tool names follow the same verb_noun pattern in snake_case (e.g., list_meetings, get_meeting_transcript, search_transcripts), which makes the naming scheme predictable and consistent across the entire set.
Five tools is a well-scoped count for a meeting transcription and speaker analytics server. Each tool covers a distinct functional area without redundancy or excessive granularity.
The server provides complete coverage of its core domain: browsing meetings, reading transcripts, full-text search, and per-speaker contribution analysis. There are no obvious gaps or dead ends in the workflow.