AnkiConnect MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ALLOWED_DECKS | No | Optional allowlist of deck names the server is allowed to access | |
| ANKI_CONNECT_URL | No | The URL of the AnkiConnect add-on server | http://127.0.0.1:8765 |
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_decksA | List Anki deck names only. Read-only. Never call in parallel with other tools. |
| list_deck_cardsA | List numbered cards in a deck for systematic review sessions. Read-only. Use with chat analysis (verb forms, declension, etc.). Never call in parallel with other tools. |
| get_cardA | Get one card's full content. Read-only. Never call in parallel with other tools. |
| add_cardA | Add a card to Anki after Cursor Run. Never call in parallel with other tools. |
| search_cardsA | Search notes — read-only, for targeted lookups (verbs, tags, text). For full deck walkthrough use list_deck_cards instead. Never call in parallel with other tools. |
| edit_cardA | Apply one approved edit. Show BEFORE/AFTER in chat first, then call with new values. Used during systematic deck review when the user approves a specific card (#N). If the user sends new context, revise — do not ignore their message. Never call in parallel with other tools. |
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 6 tools
Most tools have clearly distinct purposes: listing decks, listing cards in a deck, fetching one card, adding, searching, and editing. list_deck_cards and search_cards overlap somewhat as card-retrieval operations, but their descriptions explicitly separate systematic review from targeted lookup.
All tool names follow a consistent lower_snake_case verb_noun pattern: list_decks, list_deck_cards, get_card, add_card, search_cards, edit_card. The naming is predictable and easy to navigate.
Six tools is a well-scoped set for an Anki card and deck workflow. Each tool covers a distinct functional action without unnecessary redundancy and the count feels appropriate for the server's purpose.
The server covers core card lifecycle operations well: listing decks, viewing cards, adding cards, searching, and editing cards. The main gap is the lack of a delete_card tool, and there is minimal deck-management coverage beyond listing, but the primary review-oriented workflow is well supported.