Anki Connect MCP Server
Related Servers
Alternatives to Anki Connect MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables AI assistants to create and manage Anki cards through AnkiConnect, including decks, card creation, search, updates, deletion, and mobile sync.MIT
- AlicenseNot gradedqualityCmaintenanceEnables interaction with the Anki desktop flashcard application through the Anki-Connect plugin. Supports managing decks, cards, notes, and models, allowing AI assistants to create and query flashcards through natural language.5 npm1ISC
- AlicenseAqualityDmaintenanceEnables AI assistants to manage Anki flashcard collections by creating, searching, and updating cards through a standardized interface. It supports media handling, batch operations, and review scheduling via the AnkiConnect add-on.62MIT
- AlicenseNot gradedqualityDmaintenanceEnables LLMs to interact with Anki via AnkiConnect for creating, searching, and managing flashcards, decks, and note types.1MIT
- 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.-
- AlicenseAqualityDmaintenanceEnables AI tools to manage Anki flashcards, including deck management, card search, creation, editing, deletion, and statistics.1045 npm3Apache 2.0
TDQS
Scored across 33 tools
The notes-vs-cards split is explicitly flagged in nearly every relevant description (find_notes/find_cards, notes_info/cards_info, cards_to_notes), which heads off the biggest confusion risk. A few near-duplicate pairs remain (deck_names vs deck_names_and_ids, model_names vs model_names_and_ids), and get_decks misleadingly takes card IDs rather than returning decks, but descriptions disambiguate them.
Conventions are mixed: verb_noun (get_tags, add_note, delete_decks, find_cards), bare noun phrases (deck_names, model_names, version, notes_info, cards_info), and bare verbs (suspend, unsuspend). The get_ prefix is applied inconsistently (get_tags but not deck_names) and get_decks is semantically misleading, though all names stay snake_case and readable.
33 tools is heavy; the domain is genuinely broad (decks, note types, notes, cards, media, scheduling), but several slots are consolitable duplicates such as deck_names/deck_names_and_ids and model_names/model_names_and_ids that could be one parameterized call. It sits at the upper edge of practical for an agent to scan.
Strong read/create/update coverage for notes, tags, cards, media and decks, but there is no note deletion tool and no way to grade/answer a card or set due dates, so the review lifecycle and cleanup are dead ends. Deck config is readable but not writable, and deck creation only happens implicitly via change_deck.