A
licenseC
qualityB
maintenanceServer that enables programmatic interaction with Anki through the Model Context Protocol, allowing users to manage flashcards, decks, and review processes.
3
9 npm
39
MIT
anki-mcp
by ujisati
Related Servers
Alternatives to anki-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceA Model Context Protocol server that enables LLMs to interact with Anki flashcard software through AnkiConnect, allowing for creation and management of flashcards, decks, and note types.1686 npm252MIT
- AlicenseBqualityCmaintenanceA Model Context Protocol server for managing Anki flashcards via AnkiConnect, enabling AI assistants to create, read, and update cards.813 npmMIT
- AlicenseNot gradedqualityCmaintenanceA Model Context Protocol server that allows LLMs to interact with Anki flashcard software, enabling functions like creating decks, adding notes, searching cards, and managing flashcard content through natural language.86 npm1MIT
- AlicenseAqualityDmaintenanceA server implementation that connects to a locally running Anki, enabling card review and creation through the Model Context Protocol.4184MIT
- AlicenseBqualityDmaintenanceA Model Context Protocol (MCP) server that integrates with Anki flashcard application, allowing LLM applications like Claude to interact with your Anki decks and cards.1186 npm1MIT
TDQS
B3.4/5.0
Scored across 40 tools
Disambiguation5/5
Every tool has a clearly distinct purpose with no ambiguity, as they are organized by resource type (card, deck, media, model, note) and specific actions, making it easy for an agent to differentiate between them. For example, card_suspend and card_unsuspend are clearly opposites, and note_addNote and note_addNotes handle single vs. multiple notes without overlap.
Naming Consistency5/5
Tool names follow a highly consistent verb_noun pattern with a resource prefix (e.g., card_findCards, deck_createDeck, note_updateNote), all using snake_case throughout. This predictable structure makes the tool set easy to navigate and understand at a glance.
Tool Count2/5
With 40 tools, the count is excessive for the Anki domain, likely overwhelming for agents and indicating over-fragmentation of operations. A more streamlined set of 10-20 tools could cover the same functionality without sacrificing completeness, making this borderline heavy and inefficient.
Completeness5/5
The tool set provides comprehensive CRUD and lifecycle coverage for all key Anki resources (cards, decks, media, models, notes), with no obvious gaps. It includes creation, retrieval, updating, deletion, and specialized actions like suspension and tagging, ensuring agents can handle full workflows without dead ends.
Maintenance
ActivityInactive
ResponsivenessNo issues