anki-mcp-server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ANKI_BASE | No | Anki's data folder, used to install the bridge (Anki: Tools → Add-ons → View Files, one level up) | |
| ANKI_AUTO_LAUNCH | No | Start Anki if it isn't running | 1 |
| ANKI_CONNECT_URL | No | AnkiConnect address (must be localhost) | http://127.0.0.1:8765 |
| ANKI_DEFAULT_MODEL | No | Default note type for adds/imports | |
| ANKI_MCP_READ_ONLY | No | `1` = read tools only | 0 |
| ANKI_LAUNCH_COMMAND | No | Custom command to start Anki, e.g. `flatpak run net.ankiweb.Anki` | |
| ANKI_MCP_BACKUP_DIR | No | Where backups go | ~/.anki-mcp-server/backups |
| ANKI_MCP_BRIDGE_URL | No | Bridge add-on address (must be localhost) | http://127.0.0.1:8766 |
| ANKI_CONNECT_API_KEY | No | Set this if you configured `apiKey` in AnkiConnect | |
| ANKI_MCP_ALLOW_DELETE | No | `0` = hide the delete tools | 1 |
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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| anki_statusA | Check the connection. Returns the AnkiConnect version, current profile (if the bridge add-on is installed), decks, note types with their fields, and which optional features are available. |
| anki_find_notesA | Search notes with Anki search syntax, e.g. 'deck:"Spanish"', 'tag:verbs', 'Front:hola', 'added:1', 'is:due'. Returns each note's id, note type, deck(s), tags and fields. |
| anki_list_tagsA | List all tags in the collection. |
| anki_open_browserA | Open Anki's Browse window filtered by an Anki search, so the user can look at or act on those cards. |
| anki_create_deckA | Create a deck. Use "Parent::Child" for subdecks. Does nothing if it already exists. |
| anki_add_notesA | Add notes to an existing deck. Existing notes are never overwritten; duplicates are skipped and reported. notes: list of {field: value}, e.g. [{"Front": "hola", "Back": "hello"}]. Field names are matched to the note type case-insensitively, and a unique prefix works ("Example" -> "Example sentence"). model: note type. Default: ANKI_DEFAULT_MODEL, else the note type most used in that deck. tags: tags for every note. duplicate_scope: "collection" (Anki's default: same first field + same note type anywhere) or "deck". allow_html: if false (default), text is HTML-escaped and newlines become . dry_run: report what would be added/skipped without writing. |
| anki_import_fileA | Import a .txt/.tsv/.csv file into an existing deck, one note per row. Columns map to fields: from |
| anki_generate_audioA | Add text-to-speech audio to notes matching an Anki search (e.g. 'deck:"Spanish" added:1'). Only notes whose dest_field is empty are processed; nothing is overwritten. source_field: field whose text is spoken. dest_field: field that receives [sound:...] (e.g. "Back" or an "Audio" field). Works out of the box. engine: "google" = built-in, free Google Translate voices, needs internet; the text is sent to Google. "awesometts" = your AwesomeTTS add-on voice (needs AwesomeTTS + the bridge add-on). "auto" (default) = AwesomeTTS if available, else google. lang: language code for google (e.g. "en", "es", "fr", "de", "ja", "zh-CN"); see anki_tts_status. accent: Google domain for regional accents with lang "en": "com" (US), "co.uk", "com.au", "ca", "co.in". preset: AwesomeTTS preset name (or "group:"); default = the voice last used in AwesomeTTS. |
| anki_tts_statusA | Which text-to-speech engines are available: built-in Google voices (with language codes) and, if the AwesomeTTS add-on + bridge are installed, its presets and last used voice (never options or API keys). |
| anki_syncA | Sync the collection with AnkiWeb (requires being logged in to AnkiWeb in Anki). |
| anki_update_notesA | Edit existing notes' fields and/or tags. Two-step: without confirm_token it returns a before/after preview and a token; call again with the same arguments + confirm_token to apply (notes are backed up first). updates: [{"note_id": 123, "fields": {"Back": "new text"}, "add_tags": ["x"], "remove_tags": ["y"]}] Only the listed fields change; "" clears a field (except the first field). |
| anki_move_notesA | Move notes (all their cards, keeping review history) to another existing deck. Give note_ids OR an Anki search query. Two-step: preview + token, then call again with confirm_token. |
| anki_rename_deckA | Rename a deck (subdecks follow; cards, review history and option presets are kept). "A::B" nests it under A. Two-step: preview + token, then call again with confirm_token. Uses the bridge add-on if installed, otherwise moves the cards to a new deck with the new name. |
| anki_rename_profileA | Rename the current Anki profile (e.g. the default "User 1"). Anki briefly closes and reopens the collection, like File -> Switch Profile, and syncs if sync-on-open/close is enabled. Cards, history, add-ons and the AnkiWeb login are kept. Two-step: preview + token. Needs the bridge add-on. |
| anki_install_bridgeA | Install (or update) the optional Anki MCP Bridge add-on into Anki's add-ons folder. It enables renaming the Anki profile, exact deck renames, and AwesomeTTS audio. Two-step: preview + token. The user must restart Anki afterwards. |
| anki_delete_notesA | Delete notes with all their cards and review history. Give note_ids OR an Anki search query. Two-step: preview + token, then call again with confirm_token. A JSON backup is written first. |
| anki_delete_deckA | Delete a deck, its subdecks and all their cards. Two-step: preview + token, then call again with confirm_token. The deck is first exported (with review history) to an .apkg in the backup folder, which can be re-imported via Anki's File -> Import. |
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 17 tools
Most tools have clearly distinct purposes (add/find/update/delete notes, create/rename/delete decks, sync, audio generation). Minor overlaps exist: anki_status and anki_tts_status both report environment features, and anki_add_notes vs anki_import_file both add notes (bulk API vs file), but the descriptions distinguish them adequately. The repeated two-step confirm_token pattern across destructive tools is uniform and predictable.
Every tool uses the anki_ prefix followed by a snake_case verb_noun (anki_create_deck, anki_find_notes, anki_move_notes, anki_delete_notes). A couple of noun-only names (anki_status, anki_sync) are conventional and readable. No mixing of casing or verb styles anywhere in the set.
17 tools is on the heavy side but each covers a distinct operation in the Anki collection lifecycle, and the domain (decks, notes, tags, audio, sync, backups, bridge install) genuinely warrants this breadth. Slightly over the ideal 3-15 range but without obvious padding or redundant tools.
Strong coverage: notes have find/add/import/update/move/delete with backups and dry-run, decks have create/rename/delete, plus sync, TTS, and bridge install. Gaps are minor but real: no explicit list_decks or create/rename tags tools (tags are only listable, modified indirectly via update_notes), and no card review/study operation beyond search filters like is:due.