anki-mcp-server
Provides an MCP server (with optional local STDIO or remote HTTP mode) that lets AI assistants interact with an Anki collection via the AnkiConnect plugin—supporting sync, deck management, note CRUD, media management, and note model/template retrieval.
Score Breakdown
⚙ Agent Friendliness
🔒 Security
Security posture depends heavily on transport and network exposure. Local STDIO mode is safer than exposing an HTTP server publicly via ngrok. The README warns that anyone with the ngrok URL can access the Anki data, implying weak access control when tunneling. Optional AnkiConnect API key support exists via ANKI_CONNECT_API_KEY, but there is no evidence of fine-grained authorization scopes. TLS is not explicitly described; default HTTP mode suggests loopback by default (127.0.0.1), but remote hosting and ngrok exposure can increase risk. Dependency hygiene is inferred from manifest only; no CVE/SBOM info provided in the supplied content.
⚡ Reliability
Best When
You want an AI assistant to read and (optionally) update your local Anki collection through an MCP client, with AnkiConnect running and (preferably) using local STDIO mode or a tightly controlled HTTP setup.
Avoid When
You cannot control who can reach the HTTP/ngrok endpoint, or you need guarantees that updates won’t fail in edge cases (e.g., Anki UI open during updateNoteFields).
Use Cases
- • AI-assisted spaced repetition workflows (review, explanations, and adaptive practice)
- • Automating note creation/updates in Anki from conversational prompts
- • Searching and organizing Anki notes/decks using natural language mapped to AnkiConnect/MCP tools
- • Managing Anki media (upload/download/delete) as part of study content flows
- • Integration with MCP-capable desktop/editor clients (Claude Desktop, Cursor, Cline, Zed)
- • Read-only exploration of Anki data via MCP to reduce risk of accidental changes
Not For
- • Running without AnkiConnect installed (server relies on AnkiConnect)
- • Use as a general Anki automation API for non-MCP environments without suitable transport support
- • Scenarios requiring strong network-based access control (especially when using exposed ngrok tunnels)
Interface
Authentication
The MCP server itself appears to rely on local trust/transport. Authentication is primarily via AnkiConnect configuration (optional API key) and network exposure controls when using HTTP/ngrok.
Pricing
No package pricing details were provided in the supplied README/manifest beyond npm metadata.
Agent Metadata
Known Gotchas
- ⚠ updateNoteFields may silently fail if the note is currently being viewed in Anki’s browser window (upstream AnkiConnect limitation).
- ⚠ deleteNotes requires confirmDeletion: true; agents must supply explicit confirmation to avoid accidental deletions.
- ⚠ Media upload best practice recommends using file paths/URLs (base64 is discouraged due to speed/token inefficiency).
- ⚠ Project is labeled Beta and APIs/features may change.
Alternatives
Full Evaluation Report
Comprehensive deep-dive: security analysis, reliability audit, agent experience review, cost modeling, competitive positioning, and improvement roadmap for anki-mcp-server.
AI-powered analysis · PDF + markdown · Delivered within 30 minutes
Package Brief
Quick verdict, integration guide, cost projections, gotchas with workarounds, and alternatives comparison.
Delivered within 10 minutes
Score Monitoring
Get alerted when this package's AF, security, or reliability scores change significantly. Stay ahead of regressions.
Continuous monitoring
Scores are editorial opinions as of 2026-03-30.