Anki MCP Server

What anki-mcp-server does

anki-mcp-server gives language-model clients an MCP interface to Anki through AnkiConnect. It covers common collection-management tasks, including creating decks and notes, importing notes in batches, searching with Anki query syntax, inspecting note details, modifying fields or tags, and deleting notes.

The server also exposes operations for note types. Agents can list available models, inspect a model’s structure, and create new note types. Tag management includes listing collection tags and adding or removing tags across one or more notes. A sync tool can request an AnkiWeb synchronization after explicit confirmation.

MCP resources complement the action tools with collection metadata: all decks and IDs, all tags, all note types, schemas for every note type, and the schema for one named note type.

How it works

The MCP process communicates with AnkiConnect, which must be installed and reachable from the same environment or configured endpoint. Agents call namespaced tools such as anki_create_note, anki_search_notes, and anki_update_note. Older unprefixed names remain available for existing clients, but new integrations should use the anki_* names.

anki_check_connection can verify that AnkiConnect is reachable before other operations begin. The server accepts a custom AnkiConnect port through the --port command-line option. The default client configuration launches the package with npx --yes anki-mcp-server over standard input and output.

Synchronization is intentionally gated by a confirm: true argument because a full sync can merge or overwrite local and remote collections. A successful tool response means Anki accepted the request; a blocking dialog in Anki can leave the operation queued without delivering data to AnkiWeb.

Setup and configuration

Install Anki and the AnkiConnect add-on, then ensure Node.js 20.11 or newer is installed. For Claude Desktop, add the server to claude_desktop_config.json:

{
  "mcpServers": {
    "anki": {
      "command": "npx",
      "args": ["--yes", "anki-mcp-server"]
    }
  }
}

For a non-default AnkiConnect port, append "--port", "8080" to the argument list. Cline uses the same command structure in its cline_mcp_settings.json configuration. Claude Desktop users can also build and install the packaged .mcpb extension with npm run mcpb; the package is intended for Desktop Extensions.

Claude Code can install the associated Anki skill with npx skills add nailuoGG/anki-mcp-server@anki. For direct development, install dependencies with npm install, build with npm run build, and run tests with npm test.

Do not use the .mcpb package as the stdio process: its Electron metadata on standard output interferes with MCP communication. Use npx -y anki-mcp-server for that mode.

Tools and capabilities

Available namespaced tools include:

• Check AnkiConnect reachability and trigger AnkiWeb synchronization.
• List or create decks, optionally returning deck IDs.
• List collection tags, then add or remove tags on multiple notes.
• Create one note or batch-create several notes.
• Search notes with Anki query syntax and retrieve detailed note information.
• Update note fields or tags and delete one or more notes.
• List note types, create a type, and inspect its detailed structure.

Resources include anki://decks/all, anki://tags/all, anki://note-types/all, anki://note-types/all-with-schemas, and anki://note-types/{modelName}. The repository also includes an MCP Inspector command, npm run inspector, for viewing messages, invoking tools, and examining logs during development.

Limitations and notes

Anki and the AnkiConnect add-on are required dependencies. The sync operation can affect both local and remote collections, so it requires explicit confirmation. The server’s packaged Desktop Extension and its direct stdio invocation are separate usage paths; the latter is the appropriate choice when launching it as a normal MCP process.