Skip to main content
Glama

Anki MCP 服务器

一个模型上下文协议 (MCP) 服务器,通过 AnkiConnect 使 LLM 能够与 Anki 抽认卡软件交互。

Anki 图标

功能

工具

  • list_decks - 列出所有可用的 Anki 牌组

  • create_deck - 创建一个新的 Anki 牌组

  • create_note - 创建一个新的笔记(基础或填空题)

  • batch_create_notes - 一次性创建多个笔记

  • search_notes - 使用 Anki 查询语法搜索笔记

  • get_note_info - 获取笔记的详细信息

  • update_note - 更新现有笔记

  • delete_note - 删除笔记

  • list_note_types - 列出所有可用的笔记类型

  • create_note_type - 创建一个新的笔记类型

  • get_note_type_info - 获取笔记类型的详细结构

资源

  • anki://decks/all - 所有可用牌组的完整列表

  • anki://note-types/all - 所有可用笔记类型的列表

  • anki://note-types/all-with-schemas - 所有笔记类型的详细结构信息

  • anki://note-types/{modelName} - 特定笔记类型的详细结构信息

Related MCP server: Anki MCP Server

先决条件

  1. 系统中已安装 Anki

  2. Anki 中已安装 AnkiConnect 插件

配置

通过桌面扩展 (.mcpb) 安装

本仓库支持 Anthropic 桌面扩展 (MCPB)。在 Claude Desktop 中使用此服务器最简单的方法是安装打包好的 .mcpb 捆绑包。

  1. 使用提供的脚本在本地生成 .mcpb 文件:

npm run pack
  1. 打开 Claude Desktop 设置 → 扩展,拖入生成的 .mcpb 文件,然后点击安装。

这将验证 manifest.json 并输出一个可按上述方式安装的 .mcpb 归档文件。了解更多关于桌面扩展的信息,请参阅 Anthropic 的公告:桌面扩展:为 Claude Desktop 提供一键式 MCP 服务器安装。

在 Claude Desktop 中使用

将服务器添加到你的 claude_desktop_config.json 中:

{
  "mcpServers": {
    "anki": {
      "command": "npx",
      "args": ["--yes", "anki-mcp-server"]
    }
  }
}

使用自定义 AnkiConnect 端口

如果你的 AnkiConnect 运行在不同的端口上,可以使用 --port 参数指定它:

{
  "mcpServers": {
    "anki": {
      "command": "npx",
      "args": ["--yes", "anki-mcp-server", "--port", "8080"]
    }
  }
}

Cline 配置

将服务器添加到 VSCode 设置文件 cline_mcp_settings.json 中的 Cline MCP 设置里:

{
  "mcpServers": {
    "anki": {
      "command": "npx",
      "args": ["--yes", "anki-mcp-server"]
    }
  }
}

使用自定义 AnkiConnect 端口

对于 Cline,你也可以指定自定义端口:

{
  "mcpServers": {
    "anki": {
      "command": "npx",
      "args": ["--yes", "anki-mcp-server", "--port", "8080"]
    }
  }
}

智能体技能 (Claude Code)

安装 Anki 技能,让 Claude Code 具备所有 Anki 工具和工作流的内置知识:

npx skills add nailuoGG/anki-mcp-server@anki

安装完成后,当你要求 Claude Code 创建抽认卡、管理牌组或批量导入笔记时,它会自动使用该技能。

注意: 不要将 .mcpb 打包版本用作 MCP 服务器 — 它会将 Electron 元数据输出到标准输出 (stdout),这会破坏 MCP stdio 协议。请改用 npx -y anki-mcp-server。

开发

打包桌面扩展 (.mcpb)

为 Claude Desktop 创建可分发的桌面扩展捆绑包:

npm run pack

这将构建项目并从当前仓库生成一个 .mcpb 归档文件,同时验证 manifest.json。通过将其拖入 Claude Desktop 的扩展设置中进行测试。参考:桌面扩展:为 Claude Desktop 提供一键式 MCP 服务器安装。

发布到 MCP 注册表

当发布新版本时,此服务器会自动发布到 MCP 注册表。发布过程包括:

  1. 自动化 CI/CD:GitHub Actions 在成功发布时会自动发布到 NPM 和 MCP 注册表

  2. 模式验证:server.json 文件在发布前会根据 MCP 模式进行验证

  3. 版本同步:package.json、manifest.json 和 server.json 之间的版本保持同步

  4. 全面测试:在发布前进行多版本 Node.js 测试、代码检查和验证

  5. Beta 支持:用于测试新功能的自动化 Beta 版本发布

手动验证

你可以在本地验证 MCP 服务器配置:

npm run validate-mcp

这将下载最新的 MCP 模式并验证你的 server.json 文件。

手动发布

如果你需要手动发布,可以使用 MCP 发布者 CLI:

# Install MCP Publisher
curl -L "https://github.com/modelcontextprotocol/registry/releases/download/v1.1.0/mcp-publisher_1.1.0_$(uname -s | tr '[:upper:]' '[:lower:]')_$(uname -m | sed 's/x86_64/amd64/;s/aarch64/arm64/').tar.gz" | tar xz mcp-publisher
chmod +x mcp-publisher
sudo mv mcp-publisher /usr/local/bin/

# Login to MCP Registry
mcp-publisher login github-oidc

# Publish to MCP Registry
mcp-publisher publish

设置

  1. 安装依赖:

npm install
  1. 构建服务器:

npm run build
  1. 用于自动重建的开发模式:

npm run watch

测试

运行测试套件:

npm test

这将执行以下测试:

  • 服务器初始化

  • AnkiConnect 通信

  • 笔记操作(创建/读取/更新/删除)

  • 牌组管理

  • 错误处理

调试

由于 MCP 服务器通过 stdio 进行通信,我们建议使用 MCP Inspector:

npm run inspector

它提供了一个基于浏览器的界面,用于:

  • 监控 MCP 消息

  • 测试工具调用

  • 查看服务器日志

  • 调试通信问题

使用示例

  1. 创建一个新牌组:

Create a new Anki deck called "Programming"
  1. 添加一张基础卡片:

Create an Anki card in the "Programming" deck with:
Front: What is a closure in JavaScript?
Back: A closure is the combination of a function and the lexical environment within which that function was declared.
  1. 添加一张填空题卡片:

Create a cloze card in the "Programming" deck with:
Text: In JavaScript, {{c1::const}} declares a block-scoped variable that cannot be {{c2::reassigned}}.

贡献

  1. Fork 本仓库

  2. 创建你的功能分支

  3. 运行测试:npm test

  4. 提交 Pull Request

星标历史

Star History Chart

致谢

图标由 macOS Icons 提供

许可证

MIT 许可证 - 详情请参阅 LICENSE 文件

Available Tools

16 tools
anki_add_note_tagsAdd Tags To Anki NotesA
Idempotent

Use when the user wants to add one or more tags to existing notes for organization. Do not use when the user wants to remove tags (use anki_remove_note_tags) or update note content (use anki_update_note). Safety: confirm before adding tags to a large number of notes.

Inputs: tags (required), noteId, noteIds. Returns: tags, noteIds, success, operation, +1 more

anki_batch_create_notesBatch Create Anki NotesA

Use when the user wants to create multiple study cards at once (2–50 notes). Prefer this over repeated anki_create_note calls. Returns per-note success and error details. Safety: ask the user to confirm before creating a large batch of notes.

Inputs: notes (required), stopOnError, allowDuplicate. Returns: total, failed, results, successful

anki_check_connectionCheck Anki ConnectionA
Read-only

Check whether AnkiConnect is reachable and return the API version.

Inputs: no named parameters. Returns: version, connected

anki_create_deckCreate Anki DeckB
Idempotent

Create an Anki deck by name.

Inputs: name (required). Returns: name, deckId

anki_create_noteCreate Anki NoteA

Use when the user wants to create a single new study card (note) in an existing deck. Creates user study content — not a schema change. Do not use when the user only wants to inspect existing notes, decks, tags, or note types. To define a new note structure, use anki_create_note_type instead. Call anki_get_note_type_info first for custom fields. For multiple notes, use anki_batch_create_notes. Safety: confirm with the user before creating notes if intent is unclear.

Inputs: deck (required), type (required), fields (required), tags, +1 more. Returns: deck, noteId, modelName

anki_create_note_typeCreate Anki Note TypeA

Use when the user wants to define a new note schema/model with custom fields and card templates. Modifies the Anki collection structure — not for creating study content. Do not use when the user wants to create notes (use anki_create_note) or inspect an existing note type (use anki_get_note_type_info). Safety: confirm with the user before creating a new note type, as this changes the collection schema.

Inputs: name (required), fields (required), templates (required), css. Returns: fields, success, modelName, templates

anki_delete_noteDelete Anki NotesA
DestructiveIdempotent

Use when the user explicitly asks to permanently delete one or more notes. Do not use when the user only wants to inspect, search, or update notes. Safety: always confirm with the user before deleting any note — this action is irreversible.

Inputs: noteId, noteIds. Returns: noteIds, success, deletedCount

anki_get_note_infoGet Anki Note InfoA
Read-only

Get detailed information for one note ID.

Inputs: noteId (required). Returns: tags, fields, noteId, modelName

anki_get_note_type_infoGet Anki Note Type InfoA
Read-only

Use when inspecting a note type before creating or updating notes, especially for non-standard models. Returns fields and card templates. Call this before anki_create_note when using a custom note type. Do not use when the user wants to create notes or modify a note type.

Inputs: modelName (required), includeCss. Returns: css, fields, modelName, templates

anki_list_decksList Anki DecksA
Read-only

List all available Anki decks, optionally with deck IDs.

Inputs: includeIds. Returns: count, decks, deckIds

anki_list_note_typesList Anki Note TypesA
Read-only

List all available Anki note types/models.

Inputs: no named parameters. Returns: count, noteTypes

anki_list_tagsList Anki TagsA
Read-only

List all tags currently used in the Anki collection.

Inputs: no named parameters. Returns: tags, count

anki_remove_note_tagsRemove Tags From Anki NotesA
DestructiveIdempotent

Use when the user wants to remove specific tags from one or more existing notes. Do not use when the user wants to add tags (use anki_add_note_tags) or clear all tags (use anki_update_note with an empty tags array). Safety: confirm with the user before removing tags, as this modifies note metadata.

Inputs: tags (required), noteId, noteIds. Returns: tags, noteIds, success, operation, +1 more

anki_search_notesSearch Anki NotesA
Read-only

Search notes with Anki query syntax and return paginated note details.

Inputs: query (required), limit, offset. Returns: limit, notes, query, total, +3 more

anki_syncSync AnkiA

Request AnkiWeb sync. Requires {"confirm": true}: without it the call is refused, because a full sync can merge or overwrite local and remote collections. Success means Anki accepted the request, not that AnkiWeb completed it.

Inputs: confirm. Returns: message, success

anki_update_noteUpdate Anki NoteA
DestructiveIdempotent

Use when the user wants to edit the fields or replace the tags of an existing note. Do not use when the user only wants to inspect note content (use anki_get_note_info) or delete it (use anki_delete_note). Safety: confirm with the user before overwriting note content.

Inputs: noteId (required), tags, fields. Returns: noteId, success, updatedTags, updatedFields

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A4/5.0

    Scored across 16 tools

    Disambiguation4/5

    Each tool targets a distinct resource+action, and descriptions explicitly say when NOT to use a tool (e.g. update vs inspect vs delete notes), which strongly aids selection. Minor potential confusion exists between anki_create_note/anki_batch_create_notes and anki_list_note_types/anki_get_note_type_info, but the descriptions disambiguate these well.

    Naming Consistency5/5

    All 16 tools consistently follow anki_<verb>_<noun> snake_case (get_note_info, list_decks, create_note, add_note_tags, remove_note_tags). The pattern is predictable throughout with no stylistic deviations.

    Tool Count4/5

    16 tools is at the upper end of the comfortable range but each earns its place across notes, decks, tags, and note types. Slightly heavy, but not excessive for a full collection-management surface.

    Completeness4/5

    Strong coverage: notes have create/batch-create/get/update/delete/search, plus deck and tag management, note-type inspection/creation, sync, and connection check. Minor gaps remain (no deck delete/rename, no note-type update/delete, no single-note get by search shortcut), but core workflows are covered.

    Maintenance

    ActivityMaintained
    ResponsivenessLimited data

    Related MCP Connectors

    Related MCP Servers