anki-mcp-server
Related Servers
Alternatives to anki-mcp-server
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceEnables AI agents to work with a local Anki collection through MCP while Anki stays open in the background, listing and creating decks, listing note types, searching notes, and previewing or creating Basic and Cloze notes in batches. Deletion of cards or decks requires explicit confirmation in Anki and completes only after a recovery backup finishes.15AGPL 3.0
- AlicenseAqualityCmaintenanceEnables reading and writing to your local Anki collection through AnkiConnect, allowing creation, update, and search of notes and decks from MCP clients like Claude Desktop.11MIT
- AlicenseBqualityCmaintenanceEnables AI assistants to manage Anki flashcards, decks, note types, tags, and media via AnkiConnect. Supports operations like adding, editing, finding, and syncing cards through a local MCP server.100MIT
- FlicenseNot gradedqualityDmaintenanceProvides programmatic access to Anki flashcard operations through the AnkiConnect API, allowing users to list and create decks and cards. It enables seamless management of flashcards directly from MCP-compatible clients like Claude Desktop.-
- FlicenseNot gradedqualityNot gradedmaintenanceEnables AI assistants like Claude to interact with Anki flashcard decks through AnkiConnect. Supports creating and managing decks, basic and cloze deletion cards, searching existing cards, and organizing content with tags.-
- FlicenseNot gradedqualityAmaintenanceExposes Anki flashcard collections to AI assistants via MCP, enabling AI-powered study sessions, card creation, deck management, and review workflows. Supports comprehensive collection operations including search, media management, and note type customization.102-
TDQS
Scored across 17 tools
Most tools have clearly distinct purposes (add/find/update/delete notes, create/rename/delete decks, sync, audio generation). Minor overlaps exist: anki_status and anki_tts_status both report environment features, and anki_add_notes vs anki_import_file both add notes (bulk API vs file), but the descriptions distinguish them adequately. The repeated two-step confirm_token pattern across destructive tools is uniform and predictable.
Every tool uses the anki_ prefix followed by a snake_case verb_noun (anki_create_deck, anki_find_notes, anki_move_notes, anki_delete_notes). A couple of noun-only names (anki_status, anki_sync) are conventional and readable. No mixing of casing or verb styles anywhere in the set.
17 tools is on the heavy side but each covers a distinct operation in the Anki collection lifecycle, and the domain (decks, notes, tags, audio, sync, backups, bridge install) genuinely warrants this breadth. Slightly over the ideal 3-15 range but without obvious padding or redundant tools.
Strong coverage: notes have find/add/import/update/move/delete with backups and dry-run, decks have create/rename/delete, plus sync, TTS, and bridge install. Gaps are minor but real: no explicit list_decks or create/rename tags tools (tags are only listable, modified indirectly via update_notes), and no card review/study operation beyond search filters like is:due.