anki-mcp-server

An MCP (Model Context Protocol) server that connects a client (e.g., Claude Desktop) to Anki via the AnkiConnect plugin, exposing Anki decks and note models as MCP resources and providing tools to list/create notes.

Evaluated Mar 30, 2026 (21d ago)
Repo ↗ Ai Ml anki mcp anki-connect memorization knowledge-management developer-tools
⚙ Agent Friendliness
52
/ 100
Can an agent use this?
🔒 Security
25
/ 100
Is it safe for agents?
⚡ Reliability
26
/ 100
Does it work consistently?

Score Breakdown

⚙ Agent Friendliness

MCP Quality
70
Documentation
55
Error Messages
0
Auth Simplicity
95
Rate Limits
0

🔒 Security

TLS Enforcement
10
Auth Strength
20
Scope Granularity
0
Dep. Hygiene
40
Secret Handling
60

MCP over stdio implies no TLS concerns at the MCP transport layer, but this also means there is no documented auth/authorization model in the README. Tooling can create content in the user’s Anki database; inputs should be treated as sensitive and validated by the MCP client. No information is provided on dependency vulnerability posture, secret handling, logging, or operational safeguards.

⚡ Reliability

Uptime/SLA
0
Version Stability
35
Breaking Changes
40
Error Recovery
30
AF Security Reliability

Best When

You control the Anki/AnkiConnect environment locally and want an MCP bridge for LLM-driven note creation and deck/model discovery.

Avoid When

You need guaranteed idempotency, robust retry semantics, or documented limits/error codes beyond what AnkiConnect provides.

Use Cases

  • Generate and insert Anki notes from an LLM workflow
  • Programmatically create study content in specific decks/models
  • Retrieve metadata about decks and note models to drive automation

Not For

  • Production-grade, multi-tenant deployments needing strong auth, tenancy boundaries, and rate limiting at the service layer
  • Use without Anki running and AnkiConnect installed/enabled

Interface

REST API
No
GraphQL
No
gRPC
No
MCP Server
Yes
SDK
No
Webhooks
No

Authentication

OAuth: No Scopes: No

No auth mechanism is described for the MCP server itself; access appears local/stdio-based as configured in the Claude Desktop config. AnkiConnect typically governs permissions, but this README does not describe auth.

Pricing

Free tier: No
Requires CC: No

No pricing information provided; repository appears as open-source tooling.

Agent Metadata

Pagination
none
Idempotent
False
Retry Guidance
Not documented

Known Gotchas

  • Requires AnkiConnect and Anki to be running/reachable from the MCP server environment (behavior not documented here).
  • Debugging over stdio can be challenging; relies on MCP Inspector for troubleshooting.
  • No documented mapping/constraints for tool inputs (e.g., required field formats, tag semantics) beyond a high-level description.

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

$99

Package Brief

Quick verdict, integration guide, cost projections, gotchas with workarounds, and alternatives comparison.

Delivered within 10 minutes

$3

Score Monitoring

Get alerted when this package's AF, security, or reliability scores change significantly. Stay ahead of regressions.

Continuous monitoring

$3/mo

Scores are editorial opinions as of 2026-03-30.

8642
Packages Evaluated
17761
Need Evaluation
586
Need Re-evaluation
Community Powered