meetings-mcp
Related Servers
Alternatives to meetings-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityDmaintenanceRead-only access to your Gilbert meetings, transcripts and summaries over MCP — list, search, and fetch transcripts and summaries.525 npm1MIT

Roomtone MCPofficial
AlicenseAqualityCmaintenanceEnables AI agents and MCP clients to browse Roomtone meeting notes, add YouTube or pasted-text sources, generate summaries, ask questions answered from transcripts, and retrieve raw transcript text. Recording itself stays in the Roomtone app, so the server only reads and adds to existing meetings.74 npmMIT- 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.-
- AlicenseNot gradedqualityDmaintenanceRead-only MCP server for searching and retrieving LogicNotes meeting notes, including summaries, transcripts, and action items.MIT
- AlicenseNot gradedqualityBmaintenanceEnables MCP-capable agents to browse, search, and retrieve Meetily meeting transcripts and summaries on demand through read-only tools.1MIT
- AlicenseNot gradedqualityBmaintenanceEnables MCP clients to search and read recorded meeting data, including transcripts, notes, action items, and participants, from Walkie's local database.1MIT
TDQS
Scored across 3 tools
Each tool has a clearly distinct purpose: list_meetings enumerates meetings, get_transcript fetches paginated transcript content for a known meeting id, and search_transcripts performs a global substring search. There is no overlap in resource or action, so selection errors are unlikely.
All three names follow a consistent snake_case verb_noun pattern (list_meetings, get_transcript, search_transcripts). The singular/plural difference reflects the object cardinality well and does not break the convention.
Three tools is on the low end but well-scoped for a read-only transcript server: listing, reading paginated content, and searching. No functionality feels redundant or missing enough to warrant extra tools.
The read-only surface covers the core workflows: discover meetings, read a transcript, and search across all transcripts. Minor gaps exist, such as filtering meetings by date or retrieving per-speaker data, but agents can work around these using the provided tools.