Anki MCP

io.github.RyhusPublished by GitHub account Ryhusv0.1.1Updated Nov 7, 2026

Manage local Anki notes, cards, decks, note types, media, and deck packages via AnkiConnect.

VerifiedSTDIODesktop onlyProductivity & WorkflowFiles & Storage

Overview

AI-generated overview

Lets an assistant search, create and edit Anki notes and cards, manage decks, and handle media and .apkg packages through a local AnkiConnect add-on.

What you can do
  • Search, create and edit notes, with drafts shown before creation
  • Manage decks, cards and note types
  • Inspect card front/back HTML and CSS without changing it
  • Preview deck exports, including without review history
  • Import and export .apkg deck packages from allowlisted local folders
  • Add media from local folders, public HTTPS links or base64 sources
When to use it
Useful if you study with Anki Desktop and want an assistant to find notes by tag or text, draft new vocabulary cards for review, inspect card templates, or move decks in and out as packages.
Requirements
Runs locally via npx, so Node.js 24 or newer with npm must be on the client's PATH. Anki Desktop must be open with the AnkiConnect add-on installed. ANKI_URL is required and points at the local AnkiConnect base address without /api/v1. Optional settings: ANKI_API_MODE (v1 or legacy), ANKI_MEDIA_IMPORT_DIRS, ANKI_PACKAGE_IMPORT_DIR, ANKI_PACKAGE_EXPORT_DIR, ANKI_REQUEST_TIMEOUT_MS. The client must support launching stdio MCP servers.
Before you install
Tools can create, edit and delete notes, cards and decks; review previews before approving destructive changes, and note that not every tool offers a preview. The server makes no backups and does not retry writes, so check Anki after an error before repeating an action. Package and media import folders must be existing trusted absolute paths, since they grant file access. Using @latest fetches the current release at startup.

Installation

In SourceWeft

  1. Open Anki MCP in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

Anki MCP

Use Anki Desktop from your AI chat app. Search, create, and edit notes; manage decks and cards; preview card HTML/CSS; and work with media and .apkg deck packages.

Your MCP client is the app you chat with, not Anki Desktop. It needs to support launching local MCP servers (also called stdio servers). It starts Anki MCP so your assistant can use the Anki tools.

Quick start

  1. Install Node.js 24 or newer with npm.
  2. In Anki Desktop, install AnkiConnect via Tools → Add-ons → Get Add-ons with code 2055492159. Restart Anki and keep it open.
  3. Add the server configuration below in your MCP client's settings. No clone or global install is needed.
json
{  "mcpServers": {    "anki": {      "command": "npx",      "args": ["--yes", "--prefer-online", "--package=@ryhus/anki-mcp@latest", "anki-mcp"],      "env": {        "ANKI_URL": "http://127.0.0.1:8765",        "ANKI_API_MODE": "v1"      }    }  }}

If your client has a form, put only npx in Command, enter the four Arguments separately, and add the two Environment variables shown above. ANKI_URL is the AnkiConnect address, not a remote MCP URL.

Reload the client and ask: “List my Anki decks without changing anything.”

@latest checks for the current release when the server starts; it does not update a running server. To control updates yourself, replace @latest with an exact published version, for example @0.1.0.

Try it

  • “Find German notes tagged a1 that mention Haus.”
  • “Draft three vocabulary notes for my German deck. Show me the drafts before creating them.”
  • “Show me the front and back HTML of this card without changing it.”
  • “Preview an export of my German deck without review history.”

Settings

  • ANKI_API_MODE=v1 enables the full tool set with a compatible AnkiConnect build. For an older add-on, use legacy for the supported subset.
  • To enable local .apkg import or export, set ANKI_PACKAGE_IMPORT_DIR or ANKI_PACKAGE_EXPORT_DIR to an existing, trusted absolute folder. Each is enabled separately and requires local AnkiConnect v1.
  • To import media from disk, allowlist its source folder with ANKI_MEDIA_IMPORT_DIRS. Public HTTPS and base64 sources do not need this setting.

Review previews before approving destructive changes. Not every tool offers a preview. The server does not make backups or automatically retry writes; after an error, check Anki before repeating the action.

Troubleshooting

  • The client cannot find npx: make sure both Node and npm are on the client's PATH. On Windows, use npx.cmd if your client needs the shim.
  • Anki is unreachable: check that Anki is open and AnkiConnect is enabled. Use the base address in ANKI_URL without /api/v1.
  • The package is not found: check that the requested version has been published and that your client can reach the npm registry.

MIT License.

Source: README.md at commit d79093b

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.1.1LatestNov 7, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts