anker-xinlidou-mcp
Related Servers
Alternatives to anker-xinlidou-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to locally transcribe audio, search transcripts, proofread uncertain words, and apply corrections through MCP.GPL 3.0
- AlicenseAqualityCmaintenanceEnables any MCP client to start, poll, and stop microphone recordings from within a conversation, returning the accumulating transcript on demand. All transcription runs locally on-device, so no audio leaves the machine.5MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to submit and manage durable long-form audio transcription jobs, and read or export structured transcripts via MCP tools.1MIT
- AlicenseNot gradedqualityCmaintenanceEnables memo, upload, and transcription workflows through MCP tools.29 npmMIT
- AlicenseAqualityDmaintenanceProvides voice transcription control and polling for MCP-compatible agents, enabling start/stop/pause/resume and retrieval of new text via tools.8MIT
- AlicenseAqualityCmaintenanceEnables an assistant to transcribe video or podcast recordings, then read, search, summarize, and manage the resulting transcripts through MCP tools.10MIT
TDQS
Scored across 9 tools
Each tool targets a distinct step in the sync → list → read → correct → save pipeline, and the descriptions clearly separate reading rules (correction_guide) from reading terms (glossary). The only mild overlap is pending_corrections versus list_segments, since both enumerate segments, but the pending-only filter and correction context make the boundary clear.
Most names follow a snake_case verb_noun or noun_resource pattern (sync_now, list_segments, get_transcript, save_correction, set_glossary). A few deviate: 'search' is a bare verb and 'glossary'/'correction_guide' are bare nouns, but all remain readable and predictable.
Nine tools map cleanly onto one workflow: ingest, browse, read, search, identify pending work, save corrections, and manage reference docs. No tool feels redundant or bolted on.
The transcription-correction lifecycle is covered end to end, including glossary read/write and the rules doc. Minor gaps: set_glossary only overwrites whole, with no incremental add/remove entry, and there is no way to skip or dismiss a segment that does not need correction.