Anki MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ANKI_HOST | No | AnkiConnect host | localhost |
| ANKI_PORT | No | AnkiConnect port | 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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| test_connectionB | Test connection to AnkiConnect |
| create_cardC | Create a new flashcard in Anki |
| search_cardsC | Search for cards in Anki using Anki query syntax |
| update_cardC | Update an existing card in Anki |
| delete_notesB | Delete notes (and their cards) from Anki |
| list_decksB | List all available decks in Anki |
| create_deckC | Create a new deck in Anki |
| get_deck_statsC | Get statistics for a specific deck |
| get_cards_for_reviewC | Get cards that are due for review |
| get_model_namesB | Get all available note types/models |
| get_model_fieldsC | Get field names for a specific note type/model |
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 11 tools
Each tool has a largely distinct purpose, but there is an entity inconsistency: create_card/update_card/search_cards operate on 'cards' while delete_notes operates on 'notes'—a distinction that matters in Anki (a note generates multiple cards) and could cause misselection. search_cards and get_cards_for_review are close but still distinguishable.
All 11 tools follow a clean verb_noun pattern (create_card, list_decks, get_deck_stats, get_model_fields, etc.) with consistent snake_case. No deviations or mixed conventions.
11 tools is well within the ideal 3-15 range and each earns its place across cards, decks, review, and model introspection. No bloat or redundancy.
Covers card lifecycle (create/search/update/review), deck management (list/create/stats), and model introspection, but there is no card-level delete (only delete_notes), no deck update/delete, and no note-level update, leaving minor gaps an agent must work around.