Anki MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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 | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_decksA | Get all deck names from Anki |
| list_cardsC | List card sides in a deck (uses Basic model). |
| create_cardsA | Add Basic note(s) to a deck. Duplicates skipped (null noteId in results). |
| update_cardC | Update an existing card's content |
| delete_cardsB | Delete one or more cards from Anki by their note IDs |
| create_deckC | Create a new deck in Anki |
| delete_deckA | Delete deck, nested decks, and all their cards. |
| rename_deckC | Rename a deck in Anki |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 8 tools
Each tool targets a distinct operation on either decks or cards. There is no overlap: deck tools (create, delete, rename, list) are clearly separate from card tools (create, update, delete, list). No two tools could be confused.
All tools follow a consistent verb_noun pattern with lowercase and underscores. Verbs like create, delete, get, list, rename, update are used appropriately. No style mixing or inconsistent naming.
With 8 tools, the server covers essential deck and card operations without being excessive. The number is well-scoped for a focused Anki integration, neither too thin nor too heavy.
Core CRUD operations for decks and cards are present, but notable gaps exist: there is no way to retrieve a single card's details (only list cards in a deck), and card creation is limited to the Basic model. Features like moving cards between decks or searching are missing, leaving some workflows incomplete.