anki-connect-mcp
Related Servers
Alternatives to anki-connect-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceExposes Anki as a set of tools for LLM clients, enabling note creation, search, review, and deck management via AnkiConnect.16 npmMIT
- AlicenseAqualityBmaintenanceEnables AI agents to work with a local Anki collection through MCP while Anki stays open in the background, listing and creating decks, listing note types, searching notes, and previewing or creating Basic and Cloze notes in batches. Deletion of cards or decks requires explicit confirmation in Anki and completes only after a recovery backup finishes.15AGPL 3.0
- AlicenseBqualityCmaintenanceEnables AI assistants to manage Anki flashcards, decks, note types, tags, and media via AnkiConnect. Supports operations like adding, editing, finding, and syncing cards through a local MCP server.100MIT
- FlicenseNot gradedqualityDmaintenanceProvides programmatic access to Anki flashcard operations through the AnkiConnect API, allowing users to list and create decks and cards. It enables seamless management of flashcards directly from MCP-compatible clients like Claude Desktop.-
- FlicenseNot gradedqualityAmaintenanceExposes Anki flashcard collections to AI assistants via MCP, enabling AI-powered study sessions, card creation, deck management, and review workflows. Supports comprehensive collection operations including search, media management, and note type customization.102-
- AlicenseAqualityBmaintenanceLets Claude and other MCP clients manage an Anki collection through AnkiConnect: create decks, add notes, import TSV/CSV files, search, edit, move, rename and delete cards, generate text-to-speech pronunciation audio into note fields, and sync with AnkiWeb. Changes are guarded by preview-and-confirm tokens, automatic backups, dry runs, and read-only or delete-disabled modes.1733 PyPI1MIT
TDQS
Scored across 95 tools
Tools are organized by resource namespace and most actions are explicitly scoped, but with 95 operations there are many near-neighbors such as get vs getMany, validate vs validateMany, scheduling.answer vs reviewer.answer, and media.get vs media.list. The detailed descriptions usually resolve these boundaries, so an agent can distinguish them, though not effortlessly.
Every tool follows a predictable resource_action convention, with the resource namespace followed by a camelCase action such as notes_create, cards_setSuspended, deckPresets_list, and advanced_cards_update. Suffix variants like getMany or deleteUnused remain systematic and consistent.
95 tools is far beyond an appropriate MCP surface for agent selection; even for a full Anki desktop integration, many granular and long-tail operations are exposed as separate tools. This forces agents to navigate an extremely large toolset rather than a well-scoped set of workflows.
The surface comprehensively covers collection, notes, cards, decks, note types, deck presets, tags, media, scheduling, reviews, statistics, GUI/browser/editor actions, profiles, packages, operations, and advanced maintenance. There are no obvious domain lifecycle gaps.