Speak AI MCP Serverofficial
A
licenseA
qualityB
maintenanceConnects Speak AI transcription and insight data to Claude and ChatGPT, enabling natural language queries for summaries, action items, and quotes from recordings.
100
153 npm
MIT
ktalk-mcp
by mdemyanov
Related Servers
Alternatives to ktalk-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceEnables searching meetings, retrieving transcripts and summaries from Fathom AI via Claude.11 npmMIT
- AlicenseNot gradedqualityBmaintenanceEnables Claude to access your Fathom meetings, transcripts, and AI summaries.16 npm16MIT
- AlicenseNot gradedqualityDmaintenanceConnects your Plaud voice recorder to Claude, giving access to recordings, transcripts, and AI summaries so you can query your notes via natural language.16MIT
- AlicenseAqualityAmaintenanceEnables Claude Desktop and MCP clients to access Fathom meeting intelligence, including listing meetings, retrieving summaries and transcripts, and searching by title.424 npmMIT
- FlicenseBqualityDmaintenanceEnables Claude Code to search and retrieve documents from an Outline knowledge base.2-
TDQS
A4/5.0
Scored across 15 tools
Disambiguation4/5
Most tools are clearly separated by resource and action, and the ktalk_ prefix keeps the set coherent. The only mild overlap is among recording-content tools (get_transcript vs get_summary vs get_summary_by_type) and between list_recordings/list_archive/list_calendar, but the descriptions clarify those boundaries.
Naming Consistency4/5
The ktalk_ prefix plus a verb_object pattern is largely consistent (get_, list_, download_, search_, preview_). Minor deviations exist: ktalk_auth_status lacks a verb, and ktalk_preview_cancel_meeting is slightly awkward compared to a pattern like cancel_meeting_preview.
Tool Count5/5
Fifteen tools is within the well-scoped range for a server covering recordings, meetings, rooms, contacts, and auth. Each tool addresses a distinct capability, and none feels redundant enough to remove.
Completeness2/5
The read surface is thorough, covering recordings, transcripts, summaries, participants, chat, calendar, rooms, contacts, and auth. However, the write lifecycle is essentially absent: preview_meeting and preview_cancel_meeting explicitly cannot create or cancel anything, and there are no create/update/delete tools for any resource. Agents trying to schedule, modify, or cancel meetings will hit a hard dead end.
Maintenance
ActivityActive
ResponsivenessResponsive