mcp-anki-connect
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
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 56 tools
Many tools have similar purposes (e.g., add_note vs add_notes, deck_names vs deck_names_and_ids) and lack descriptions, increasing the risk of misselection. However, most tool names are specific enough to hint at their function, and distinct categories like GUI control and media management are identifiable.
Most names follow a snake_case pattern, but verbs vary (create_, get_, add_, gui_, batch_) and some are standalone nouns (version, multi) or verbs without objects (upgrade). This mix is readable but not fully consistent.
With 56 tools, the server is far above the recommended 3-15 range and even exceeds the 'heavy' threshold of 25. The scope is broad, but this volume is overwhelming for agents and likely to cause selection fatigue.
The tool set covers most major Anki workflows: decks, notes, cards, tags, media, GUI control, and configuration. However, there are notable gaps such as no explicit delete_note or rename_deck, and update_note_fields exists but no full CRUD for cards beyond suspend/unsuspend.