anker-xinlidou-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ANKER_XINLIDOU_HOME | No | Overrides the data directory. By default all data (`db.sqlite3`, `audio/`, `config.json`, `glossary.txt`) is stored in `~/.anker-xinlidou/`. | |
| ANKER_XINLIDOU_CLOUD_KEY | No | Cloud transcription key. Only needed if you set `backend` to `cloud` in `~/.anker-xinlidou/config.json` instead of using local whisper.cpp transcription; audio is then uploaded to the service you configure. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| sync_nowA | 连录音豆、把还没拉过的录音整段取下来并转成文字(原始版)。用户需在电脑旁、关掉手机飞书。返回新增与待纠错数量。 |
| list_segmentsA | 按时间段列出录音段。start/end 用 2026-11-13 或 2026-11-13 14:30,可只给一个或都不给。 |
| get_transcriptA | 取某一段录音的完整文字(优先纠错版,没纠错则原始版)。 |
| searchC | 按关键词搜录音文字,返回命中的段。 |
| pending_correctionsA | 列出已转写、还没纠错的段,给出原始文字供你纠正。纠正前先看 correction_guide 和 glossary。 |
| save_correctionA | 把纠错后的文字写回某一段,标记为已纠错。只应写入纠正识别错误后的文字,不要改写内容。 |
| correction_guideB | 纠错规则:只纠语音识别错误(同音字、听错的词、空格、专名),不改写、不润色、不总结。 |
| glossaryA | 读术语表(人名、产品名、黑话的正确写法),纠错时照它改专名。 |
| set_glossaryB | 更新术语表,整段覆盖。 |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
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.