FluidMeet MCP Server
Related Servers
Alternatives to FluidMeet MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseAqualityDmaintenanceEnables AI assistants to query local Migas meeting transcripts, including searching, listing meetings, and retrieving speaker contributions, all read-only.56 npmMIT
- AlicenseNot gradedqualityBmaintenanceProvides read-only access to local meeting notes, enabling search across summaries and transcripts, retrieval of meeting summaries, pending action items, decisions, projects, syntheses, and period summaries.224 npmMIT
- AlicenseAqualityCmaintenanceEnables Claude Desktop and MCP clients to access Fathom meeting intelligence, including listing meetings, retrieving summaries and transcripts, and searching by title.466 npmMIT
- AlicenseNot gradedqualityBmaintenanceEnables MCP clients to search and read recorded meeting data, including transcripts, notes, action items, and participants, from Walkie's local database.1MIT
- AlicenseNot gradedqualityFmaintenanceProvides read-only access to Google Drive meeting transcripts and Google Calendar events, enabling AI assistants to search, analyze, and retrieve meeting insights.538 npm2MIT
- FlicenseAqualityDmaintenanceEnables Claude to interact with Jamie AI meeting assistant: list meetings, read summaries and transcripts, search, and manage tasks.61-
TDQS
Scored across 6 tools
The four meet_* tools have clearly separated roles: list for discovery, show for transcript windows, search for locating mentions, and summary for saved summaries. status and skill are meta tools with distinct diagnostic and usage-guide purposes, and the descriptions explicitly guide sequencing and fallbacks.
Core tools consistently follow a meet_ + action/noun pattern: meet_list, meet_show, meet_summary, meet_search. However, status and skill break the prefix pattern with bare nouns, which is a minor inconsistency but still readable.
Six tools is well-scoped for a read-only meeting transcript server. Each tool supports a distinct access path or diagnostic need, with no redundant endpoints.
The surface covers discovery, transcript reading, search, saved summaries, and accessibility diagnostics, which is strong for a read-only integration. Minor gaps include no explicit single-meeting metadata tool beyond list and no way to create or update summaries, though that may be outside the server's scope.