Anki MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| API_KEY | No | Optional: API key for external tools | |
| API_URL | No | Optional: External tools API configuration | |
| ANKI_API_KEY | Yes | Your Anki API key | |
| ANKI_BASE_URL | No | Anki API base URL | http://localhost:3000 |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
| logging | {} |
| resources | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| listDecksB | List all Anki decks with optional pagination |
| createDeckB | Create a new Anki deck |
| addCardsBatchB | Add multiple cards to a deck in batch |
| addBasicCardB | Add a single basic card to a deck |
| addClozeCardB | Add a cloze deletion card to a deck |
| getReviewQueueB | Get cards due for review with filtering options |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| Server Status |
TDQS
Scored across 6 tools
Tools are mostly distinct: addBasicCard, addClozeCard, and addCardsBatch target different card types or batch operations; createDeck, listDecks, and getReviewQueue are clearly separate. However, addCardsBatch could overlap with addBasicCard or addClozeCard if used for multiple cards of a specific type.
All tools follow a verb_noun pattern with imperative verbs (add, create, get, list). Minor inconsistencies: 'CardsBatch' uses plural and compound noun, while others use singular (BasicCard, ClozeCard). Capitalization is consistent with CamelCase.
With 6 tools, the server is well-scoped for basic Anki operations: deck creation, card addition (basic, cloze, batch), deck listing, and review queue retrieval. The number is appropriate for a focused subset.
Significant gaps exist: no update or delete operations for cards or decks, no ability to list cards within a deck, and no support for managing models or tags. Agents can create and add but cannot modify or remove content.