memoket
Memoket — access your recording transcripts, summaries, and key takeaways over MCP.
- 1.0.0
- Version
- remote
- Transport
- 7
- Tools
Security review
Review passedReviewed Jan 1, 2000.
- tools: 7 tools scanned
- metadata: scanned
No findings.
Tools (7)
get_conversations
[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.
get_transcripts_by_participant
[content_fetch] Transcript lines associated with participant_ids in conversation_ids. Turns participant metadata into transcript evidence for exposed search results.
get_brief
[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.
get_summaries
[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).
get_transcripts
[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.
list_conversations
[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.
search_recordings
[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.