anki-mcp-server-addon

Provides an Anki add-on that runs a local Model Context Protocol (MCP) server inside Anki (via HTTP transport) so AI assistants can query and manage a user's Anki collection (e.g., decks, notes, cards, tags, media) and guide review sessions.

Evaluated Mar 30, 2026 (0d ago)
Homepage ↗ Repo ↗ DevTools anki mcp ai spaced-repetition local-server python
⚙ Agent Friendliness
56
/ 100
Can an agent use this?
🔒 Security
35
/ 100
Is it safe for agents?
⚡ Reliability
38
/ 100
Does it work consistently?

Score Breakdown

⚙ Agent Friendliness

MCP Quality
78
Documentation
80
Error Messages
0
Auth Simplicity
25
Rate Limits
20

🔒 Security

TLS Enforcement
35
Auth Strength
15
Scope Granularity
20
Dep. Hygiene
55
Secret Handling
60

Likely primarily local access (127.0.0.1) but can be tunnel-exposed. README does not describe authentication/authorization, so security depends on network restrictions and CORS. Custom http_path and CORS origins can reduce accidental exposure, but there is no mention of protecting against direct requests to the MCP endpoint or enforcing per-client authorization.

⚡ Reliability

Uptime/SLA
20
Version Stability
45
Breaking Changes
35
Error Recovery
50
AF Security Reliability

Best When

You want a local, MCP-compatible bridge between an AI assistant and a single user's Anki instance running on the same machine (or safely via a tunnel with restricted exposure).

Avoid When

You need fine-grained security/audit controls for remote access or you cannot restrict who can reach the local HTTP endpoint.

Use Cases

  • AI-assisted study/review workflows using an MCP client
  • AI-driven deck/note/card creation and management in Anki
  • Searching notes using Anki's query syntax
  • Automating common spaced-repetition operations (rate cards, reschedule, tag management)
  • Tunneling/inspecting the local MCP endpoint via tools like ngrok/Cloudflare (with optional custom path)

Not For

  • Use cases requiring strong remote multi-tenant access controls (this is primarily local/tunnel exposure)
  • Scenarios where users cannot trust a local service that can manipulate their Anki collection
  • Environments needing a public, internet-facing API with robust authentication built in

Interface

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

Authentication

OAuth: No Scopes: No

README describes a local HTTP MCP server with host/port/path and CORS settings but does not mention authentication (API keys, OAuth, etc.). Access control is therefore likely determined by network exposure (localhost vs tunnel) and CORS.

Pricing

Free tier: No
Requires CC: No

No pricing information provided; Anki add-ons are typically installed locally.

Agent Metadata

Pagination
none
Idempotent
False
Retry Guidance
Not documented

Known Gotchas

  • Operations can mutate or delete collection data; agents should be cautious with destructive tools (delete_notes, delete_media_file, forget/suspend/sync).
  • Disabled tools are removed from the MCP schema; typos in tool/action names produce console warnings (agents should validate tool names).
  • First run downloads pydantic_core (~2MB); agents/workflows that rely on cold-start should allow for this delay.

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-addon.

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.

6533
Packages Evaluated
19870
Need Evaluation
586
Need Re-evaluation
Community Powered