Because it mirrors AnkiConnect action for action, the shape is the API's rather than a study workflow's: create_flashcard is the one convenience, and everything richer goes through add_note with a note type and named fields you have to look up first. The GUI half acts on the app on screen, which is the point when you want a person to see the deck, and worth remembering when the card you answer is whichever one is showing.
A bridge to a running Anki desktop, 46 tools mirroring AnkiConnect actions across decks, note types, notes, cards, tags and the reviewer windows.
- Notes added singly or in batches with a deck, note type, fields, tags and audio, and can_add_notes to check them before they are written
- create_flashcard for the plain case, taking just a front and a back
- Search by Anki query string in two directions — find_notes and find_cards — then bulk detail through notes_info and cards_info
- Scheduling state read and changed: suspend, unsuspend, are_suspended, are_due and get_intervals
- The reviewer driven step by step: open a deck for review, show question, show answer, answer with an ease, start the card timer
- Anki's own windows opened where a person needs to look — the browser with a search query, the deck browser, a deck overview, the add-cards dialog
- Deck inventory and moves: names, names with ids, the cards in a deck, moving cards between decks, deleting decks
- Deck option groups cloned, saved, assigned to decks and removed
- Note types inspected before you write to them, down to field names and which fields appear on which templates
- Tags listed and added to or removed from a set of notes, and multi to batch several actions into one call
Anki running on this machine with AnkiConnect reachable. There is no account or key: the reviewer and browser tools act on the application in front of you, and gui_exit_anki closes it.
One command — npx @spacholski1225/anki-connect-mcp