anki-mcp-server

An MCP server that lets LLMs interact with local Anki flashcards by calling AnkiConnect-style operations (decks, note types, CRUD for notes, search, and related metadata) via MCP tools and resources.

Evaluated Mar 30, 2026 (21d ago)
Repo ↗ Ai Ml mcp anki anki-connect flashcards automation agent-tools typescript
⚙ Agent Friendliness
62
/ 100
Can an agent use this?
🔒 Security
33
/ 100
Is it safe for agents?
⚡ Reliability
31
/ 100
Does it work consistently?

Score Breakdown

⚙ Agent Friendliness

MCP Quality
80
Documentation
75
Error Messages
0
Auth Simplicity
95
Rate Limits
10

🔒 Security

TLS Enforcement
30
Auth Strength
20
Scope Granularity
10
Dep. Hygiene
55
Secret Handling
60

Security posture is primarily local-tooling oriented: no auth/scopes are documented at the MCP layer, and TLS is not discussed (communication to AnkiConnect may be local/HTTP depending on AnkiConnect). This increases risk if AnkiConnect is exposed beyond localhost or if other local users can invoke the server. Ensure AnkiConnect is restricted to trusted local access, and treat note content as sensitive since tool calls can move data into/out of your Anki database.

⚡ Reliability

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

Best When

You run Anki + AnkiConnect locally and want an agent-driven workflow (via MCP/stdio) to create and manage flashcards.

Avoid When

You need authenticated multi-user remote access, webhooks, or a public API surface with strong governance and quota controls.

Use Cases

  • Generate and insert new flashcards into specific Anki decks
  • Batch creation of notes from structured content
  • Search and retrieve existing notes for review/update
  • Inspect and manage Anki note types and schemas
  • Automate deck and note-type setup from an agent

Not For

  • Hosted/remote Anki access over the internet (appears designed for local AnkiConnect)
  • Use cases requiring robust authorization or multi-tenant security boundaries
  • High-integrity workflows where silent failures or partial updates are unacceptable

Interface

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

Authentication

Methods: None documented (relies on local AnkiConnect/desktop environment)
OAuth: No Scopes: No

Authentication/authorization for the MCP server itself is not described; access is presumably limited by the local AnkiConnect setup and the user running the server.

Pricing

Free tier: No
Requires CC: No

No pricing information provided; as an MCP server wrapping local AnkiConnect, costs are likely incidental (hosting/compute and Anki installation).

Agent Metadata

Pagination
none
Idempotent
False
Retry Guidance
Not documented

Known Gotchas

  • Operations are destructive by nature (delete/update); agents should confirm targets before mutating.
  • Search/update accuracy depends on correct Anki query syntax and existing note field names.
  • AnkiConnect configuration/port must be reachable from the server process.

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