anki-web-mcp
Related Servers
Alternatives to anki-web-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceEnables LLMs to interact with Anki flashcard collections, including deck management, note search, viewing contents, and editing fields.16 npmMIT
- AlicenseAqualityBmaintenanceEnables AI chat clients to search, create, and edit notes, manage decks and cards, preview card HTML/CSS, design your cards and work with media and .apkg deck packages through AnkiConnect.73560 npmMIT
- AlicenseAqualityBmaintenanceEnables AI agents to access a local Anki collection through AnkiConnect: list decks, search and retrieve notes/cards, identify weak cards, and batch-add validated flashcards with optional pronunciation audio.5MIT
- FlicenseBqualityCmaintenanceEnables AI assistants to directly manage Anki flashcards, decks, notetypes, tags, and media, with support for batch operations, searches, and deck exports via file-based input/output.23-
- AlicenseNot gradedqualityDmaintenanceEnables LLMs to interact with Anki via AnkiConnect for creating, searching, and managing flashcards, decks, and note types.1MIT
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to create and manage Anki cards through AnkiConnect, including decks, card creation, search, updates, deletion, and mobile sync.MIT
TDQS
Scored across 11 tools
Each tool has a clear, distinct role: search/get/download shared decks are separate stages, list_my_decks and list_my_shared_decks are clearly differentiated, and share/unshare/delete are distinct account actions. Status, session cleanup, and local conversion do not overlap with the AnkiWeb catalogue tools.
Names use consistent snake_case and mostly follow verb_noun patterns such as search_shared_decks, download_shared_deck, and delete_deck. The main exception is server_status, which is a noun phrase rather than an action verb.
The set has 11 tools, which is well within a reasonable range and each tool corresponds to a meaningful AnkiWeb or deck-conversion operation. There is no obvious padding or missing category that would justify a different count.
The surface covers the shared-deck lifecycle well: search, inspect, download, share, unshare, and delete, plus account deck listings and local conversion. Minor gaps remain around account/session setup or deck update/import operations, but core workflows are covered.