The project publishes the entire Anki-Connect action surface as a checklist, and only a handful of boxes are ticked. What is there covers the workflow most people actually want: turn something you just learned into a card, in the right deck, with the right note type. Suspending, rescheduling and bulk edits appear on the list but are not built.
A Node server that talks to a running Anki desktop through the Anki-Connect plugin. The project tracks the whole Anki-Connect action list with checkboxes and marks which ones it has implemented so far.
- A new note added to a deck — `note.addNote`
- Your deck names, and the note types with their names — `deck.deckNames`, `model.modelNames`, `model.findModelsByName`
- Card details for cards you name — `card.cardsInfo`
- Review history — `statistic.cardReviews`
- The Anki browser opened on a query, so a result set appears in the app itself — `graphical.guiBrowse`
- A version check against Anki-Connect — `miscellaneous.version`
Anki desktop installed and running, with the Anki-Connect plugin installed — nothing works while Anki is closed. Node.js 18 or newer. The client launches `npx` with `@loonskai/anki-mcp-server@latest`; there is no key or account. Docker support, tool configuration and tests are listed on the project's roadmap as not yet done.
One command — npx @loonskai/anki-mcp-server@latest
