anki-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DRAFT_DB_PATH | No | Backward-compatible fallback for ANKI_MCP_DB_PATH. | |
| ANKI_CONNECT_URL | No | The URL of the AnkiConnect server (default: http://127.0.0.1:8765). | http://127.0.0.1:8765 |
| ANKI_MCP_DB_PATH | No | Path to the internal SQLite database (default varies by OS). | |
| ANKI_GATEWAY_MODE | No | Set to 'memory' for deterministic local tests without Anki. | |
| ANKI_ACTIVE_PROFILE | No | Fallback profile name for read tools. |
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
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_runtime_statusA | Report whether AnkiConnect is reachable and whether preview can use the optional extension path. |
| list_decksA | List available Anki decks using official hierarchical deck names. |
| list_note_typesB | Return available Anki note types with field and template summaries. |
| get_note_type_schemaA | Inspect fields, templates, CSS, and field bindings for one note type. |
| search_notesA | Search existing notes by Anki query, note type, deck, or tag filters. |
| get_notesA | Read concrete note fields and metadata by note ID. |
| ensure_deckA | Create a deck if missing. Safe and idempotent. |
| upsert_note_typeA | Dry-run by default. Create or update a note type with additive-safe constraints. |
| add_noteB | Create a review-pending note directly from deck, note type, fields, and tags. |
| add_notes_batchA | Create multiple review-pending notes with stable per-item outcomes. |
| update_noteA | Update note fields or tags with optimistic mod-timestamp conflict detection. |
| delete_noteA | Delete a note directly by note ID. Idempotent when already missing. |
| delete_notes_batchB | Delete multiple notes with stable per-item outcomes. |
| open_note_previewA | Open the existing note in Anki Browser preview for human review. |
| set_note_cards_suspendedB | Suspend or unsuspend all cards generated from one note. |
| import_media_assetA | Import a local audio or image file into Anki media and return an Anki-ready field value. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| tool_contracts_v1 | Frozen tool schemas and shared type registry for the note-centric public API. |
TDQS
Scored across 16 tools
Each tool targets a distinct resource and action. The batch variants (add_notes_batch, delete_notes_batch) are clearly differentiated from their singular counterparts by name and description, and get_note_type_schema vs list_note_types are distinct in detail level.
All tool names follow a consistent snake_case verb_noun pattern (e.g., list_decks, ensure_deck, add_note, delete_notes_batch). The use of 'batch' suffix is uniform and predictable.
At 16 tools, the count is slightly above the typical 3-15 range, but each tool covers a meaningful aspect of Anki management (decks, note types, notes, media, runtime). The batch operations and preview tool add breadth without feeling redundant.
The tool surface provides robust CRUD for notes (add/get/update/delete/batch/suspend) and reasonable coverage for note types (list/get/upsert). Missing operations like deck deletion or note type deletion are minor gaps that can be worked around, but do not severely hinder typical Anki workflows.