AnkiWeb
- Rating
- 1 (π 0 Β· π 1)
- Updated
- 2020-10-04
- Anki versions
- unknown
- Description language
- en
AnkiWeb addon 1724518526
Connects one or more Anki profiles to a Djankiserv Anki-compatible sync server with a limited note manipulation API.
Open on AnkiWeb GitHub Ask about alternatives
abandoned
| Min Anki | Max Anki | Updated |
|---|---|---|
| 2.1.0 | β | 2020-10-04 |
Loadingβ¦
Syncs vocabulary and cloze phrases saved in a language-learning reader into Anki notes, returning review states and daily activity counts via a scoped API token.
Lets users easily run Anki's built-in self-hosted sync server over local Wi-Fi, auto-starting and closing with Anki for faster syncing.
Runs an MCP server inside Anki so Claude and other LLM clients can create cards, quiz you, and analyze retention locally.
Fork of Anki-Connect adding features for syncing with projects like FMA, while maintaining compatibility and exposing Anki through a local HTTP API.
Generates editable Anki flashcards from topics or notes using your own API key, with review, duplicate checks, and batch import.
Generates multiple-choice pop quizzes from recent review batches every 20 cards using Codex, with configurable questions, sign-in, local scores, and privacy controls.
djankiserv is an open source Django-based implementation of a synchronisation server for Anki 2.1+. It includes a user manager (the native Django user system).
Installation -Β Connecting Anki to the sync server - Development - Contributing
This implementation was initially developed in order to support the spaced repetition functionality for Transcrobes, an open source language learning platform/ecosystem.
Any requests or functionality that don't interfere with using this project for that will definitely be entertained. Ideally the server would do everything that Ankiweb does, and much more. PRs are obviously always welcome!
Unlike the other popular open source Anki synchronisation server anki-sync-server, djankiserv stores the user data in a "proper" RDBMS. There are two 'database connections' that can be set - those for the 'system' (sessions, users, etc.) and those for user data. The 'system' stuff is just plain old Django, so any supported database can be used. The user data part currently uses either postgresql schemas or mysql databases, and currently only supports those two, though supporting other RDBMSes will definitely be considered later. sqlite3 is an embedded database and works great for that. It is not appropriate for use in modern web applications in the opinion of the maintainer, so will never be supported by djankiserv.
There is a basic API for getting certain, per-user collection-related information (decks, deck configuration, models, tags) and also notes for a given user. It may evolve to include other functions, statistics and even doing cards, though the focus is currently on getting and maintaining proper synchronisation as well as the basic API for notes.
This is alpha software with some occasional data loss bugs. It works, sorta, if you hold it right. If it kills your kittens then you were forewarned!
Current known limitations (bugs!):