Anki MCP Server

An MCP server for Anki. Exposed over MCP by the anki mcp server, that capability becomes something an assistant can invoke while it works, not something you go and do afterwards.

What it actually does

An MCP server implementation that connects to a locally running Anki, providing card review and creation.

Its toolset

Everything the assistant can do here goes through one of these:

• update_cards — Marks cards with given card IDs as answered and gives them an ease score between 1 (Again) and 4 (Easy)
• Inputs — - answers (array): Array of objects with cardId (number) and ease (number) fields
• add_card — Creates a new card in the Default Anki deck
• get_due_cards — Returns n number of cards currently due for review
• get_new_cards — Returns n number of cards from new
• Debugging — Since MCP servers communicate over stdio, debugging can be challenging. We recommend using the [MCP

Adding it to your client

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client.

When to reach for it

Plenty of developer tooling servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Anki's toolset — update_cards, Inputs, add_card and 3 more — is a fair guide to whether it matches your workflow. It is maintained by scorzeth; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.

Caveats

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the anki mcp server does with a few real requests.