{"id":"ankimcp-anki-mcp-server","name":"anki-mcp-server","af_score":60.2,"security_score":44.5,"reliability_score":35.0,"what_it_does":"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.","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).","last_evaluated":"2026-03-30T13:38:13.099631+00:00","has_mcp":true,"has_api":true,"auth_methods":["MCP transport to local/remote server (STDIO or HTTP)","Optional AnkiConnect API key via environment variable ANKI_CONNECT_API_KEY (if configured in AnkiConnect)"],"has_free_tier":false,"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."],"error_quality":0.0}