memoket
Server Details
Memoket — access your recording transcripts, summaries, and key takeaways over MCP.
TDQS
Scored across 7 tools
Each tool maps to a distinct retrieval action: metadata by ID, metadata listing, transcripts, participant-filtered transcripts, briefs, summaries, and unified search. Even the two report-fetching tools, get_brief and get_summaries, are clearly separated by their descriptions.
All tools follow a consistent snake_case verb_noun pattern: get_*, list_*, and search_recordings. The names are predictable and the resource being operated on is always clear.
Seven tools is a well-scoped size for a recording/conversation retrieval and search server. Each tool earns its place and there is no obvious redundancy.
The surface covers metadata listing/lookup, transcript retrieval, participant-level transcript evidence, brief/summary content, and unified search. A minor gap is that search returns memory-atom, topic-segment, and action-item IDs without dedicated fetchers for those individual report types.
Available Tools
7 toolsget_briefARead-onlyInspect
[content_fetch] Per-conversation compact report body for the given conversation_ids using Brief -> Summary -> Standard, where Standard is the first completed non-empty type=0 report.
Inputs: offset, brief_ids, conversation_ids. Returns: tool, result, took_ms
get_conversationsARead-onlyInspect
[metadata_query] Conversation-level metadata for the given conversation_ids: id, title, started_at, ended_at, duration_seconds, participants, language_code. No transcript, brief, or summary body.
Inputs: conversation_ids. Returns: tool, result, took_ms
get_summariesARead-onlyInspect
[content_fetch] Per-conversation summary body. With summary_ids, fetch exact summary reports from search_recordings. With conversation_ids only, fetch the latest summary report for each conversation. Paginated (offset).
Inputs: offset, summary_ids, conversation_ids. Returns: tool, result, took_ms
get_transcriptsARead-onlyInspect
[content_fetch] Verbatim transcript of ONE recording; at most 100 lines / 4000 characters per page. Resume using both next_offset and next_text_offset from the returned item, including within a long line.
Inputs: offset, text_offset, conversation_id. Returns: tool, result, took_ms
get_transcripts_by_participantBRead-onlyInspect
[content_fetch] Transcript lines associated with participant_ids in conversation_ids. Turns participant metadata into transcript evidence for exposed search results.
Inputs: limit, query, participant_ids, conversation_ids. Returns: tool, result, took_ms
list_conversationsARead-onlyInspect
[metadata_query] List recordings by time window / participants. Returns id, title, started_at, ended_at, duration_seconds, participants, language_code (no content). Paginated (count default 100, max 200; offset). order_by ranks within the window. NOTE: participants are speaker labels — placeholders ('Speaker A/B') unless the user tagged them, not necessarily real names.
Inputs: desc, count, offset, end_time, +3 more. Returns: tool, result, took_ms
search_recordingsARead-onlyInspect
[search] Unified recording search. Runs bounded searches over transcript lines, topic segments, memory atoms, participant metadata, titles, briefs, summaries, and action items in one call. Returns typed hits plus conversation_ids, line_ids, segment_ids, memory_atom_ids, participant_ids, brief_ids, summary_ids, action_item_ids. Chat execution expands hits into readable evidence automatically; external callers can fetch returned ids where a matching fetcher is advertised.
Inputs: query, end_time, start_time, search_types, +1 more. Returns: tool, result, took_ms
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Related MCP Connectors
Search, read, analyze and create HappyScribe transcripts and meeting notes from any MCP client
Persistent, verbatim, searchable memory for AI assistants — one memory across every MCP client.
Personal knowledge graph as an AI memory layer over MCP - read, save, and link your memories.
Your memory, everywhere AI goes. Build knowledge once, access it via MCP anywhere.
Related MCP Servers
- FlicenseNot gradedqualityDmaintenanceEnables AI assistants to access Plaud Note recordings, providing direct access to speaker-diarized transcripts and AI-generated meeting summaries. Users can search, list, and retrieve recording details directly within MCP-compatible clients like Claude and Cursor.1-

SeaMeet MCPofficial
AlicenseAqualityCmaintenanceSeaMeet MCP connects Claude, Cursor, Codex, and other AI agents to SeaMeet meeting recordings, transcripts, AI summaries, screenshots, action items, webhooks, and desktop recording controls. Use it to search meeting memory, read synced cloud recordings, and automate meeting notes through the Model Context Protocol.1019 npm1MIT- AlicenseNot gradedqualityCmaintenanceMeeting Summarizer AI - MCP server providing AI-powered tools and automation by MEOK AI LabsMIT
- AlicenseAqualityBmaintenanceLets MCP clients such as Claude list, read, search and compare transcripts of Apple Voice Memos on macOS, keeping word-level confidence marks so uncertain words stay visibly flagged. Adds speaker separation, optional local voiceprint recognition, and independent second-reader comparisons that highlight where two engines disagreed.10MIT
Glama MCP Gateway
Add one secure layer between your agents and this server.