anki-web-mcp
Provides access to AnkiWeb's shared deck catalogue and your synced Anki decks. Enables searching and reading shared deck listings (descriptions, tags, sample notes, reviews), downloading shared decks as .apkg files, converting decks to Flashcard Markdown, listing decks synced to your account with due counts, and publishing one of your decks to the shared catalogue after a preview and explicit confirmation.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@anki-web-mcp search AnkiWeb for Japanese vocabulary decks"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
MCP server for AnkiWeb, gives an AI agents the shared-deck catalogue and the decks synced to your account, with no Anki desktop app running.
Search shared decks and read a listing: description, sample notes, reviews.
Download a shared deck's
.apkg, and convert it to Markdown the assistant can read.List the decks synced to your account, with due counts.
Share one of your decks publicly, only after you have seen a preview and said yes.
Reuse the AnkiWeb session already signed in to your browser.
It is not affiliated with AnkiWeb or Ankitects. AnkiWeb's terms do not allow third-party clients and say it can suspend access at its discretion; docs/ankiweb.md quotes the clause. AnkiWeb licenses shared decks for personal use only.
Why this project?
Most Anki MCP servers go through AnkiConnect, an add-on that exposes the collection of a running Anki desktop app. That is the right tool for editing your own cards. It cannot see the shared catalogue, which lives only on AnkiWeb.
AnkiConnect servers | anki-web-mcp | |
Needs Anki desktop running | yes | no |
Search and download shared decks | no | yes |
Share a deck publicly | no | yes |
List your synced decks | yes | yes |
Add, edit or review cards | yes | no |
Related MCP server: anki-mcp
Install
Add the server to your MCP client's configuration:
{
"mcpServers": {
"anki-web": {
"command": "npx",
"args": ["anki-web-mcp@latest"]
}
}
}The server answers its client in under half a second. With @latest, npx
first asks the npm registry for the newest version, every time the client
starts it, which can leave the server still connecting after the others have
loaded. To skip that, run npm install -g anki-web-mcp and use
"command": "anki-web-mcp" with no args, upgrading by hand.
Then download the Chromium build the server drives:
npx anki-web-mcp@latest --install-browserSearching and downloading shared decks work from here, with no account.
Sign in
Listing your decks and sharing one need an AnkiWeb session. The first call that needs one looks for it in a local browser where you are signed in to AnkiWeb:
On macOS that shows one keychain prompt per browser it tries. If no browser has a session, sign in once in a window the server opens:
npx anki-web-mcp@latest --loginYou type your password into AnkiWeb's own page, so it never passes through the server.
The session stays in ~/.local/state/anki-web-mcp/ on Linux and in ~/.anki-web-mcp/ elsewhere,
created 0700, and --logout deletes it.
docs/cli.md lists every flag.
Tools
tool | does |
| searches the shared catalogue, with sorting and paging |
| one listing: description, tags, sample notes, reviews |
| saves a shared deck's |
| turns a local |
| the decks synced to your account, with due counts |
| the decks you have shared, with downloads and ratings |
| publishes one of your decks to the shared catalogue |
| takes one of your listings off the shared catalogue |
| deletes one of your decks, and its subdecks and cards |
| version, data directory, and whether the session is valid |
| closes the headless browser until the next call needs it |
convert_deck_to_markdown writes Flashcard Markdown through @ankimd/core, and reports what did not convert.
Changes ask first
share_deck publishes under your account, so it takes two calls.
Without confirm: true it only returns a preview, and the assistant is told to show it to you and wait.
Removing a listing with unshare_deck and deleting a deck with delete_deck ask the same way.
Confirming also makes AnkiWeb's declaration that you own the material or have a license to share it.
Read-only
Start the server with --read-only, or ANKI_WEB_MCP_READ_ONLY=1, and it lists no tool that changes anything on AnkiWeb, so share_deck, unshare_deck and delete_deck are not offered at all (docs/cli.md):
{ "command": "npx", "args": ["anki-web-mcp@latest", "--read-only"] }Several accounts
One server can act as more than one AnkiWeb account. Sign each extra one in under a name of your choosing:
npx anki-web-mcp@latest --login --account workThen ask for it by name ("list the decks on my work account").
Calls that name no account use the one signed in with plain --login, or the one --account gives the server.
npx anki-web-mcp@latest --status checks them all.
How it works
AnkiWeb is a single-page app whose data comes from protobuf endpoints under /svc/.
The server calls those endpoints directly and renders no pages.
flowchart LR
A[MCP client] -- stdio --> S[anki-web-mcp]
S -- "fetch, no cookies" --> P["/svc/shared/*<br>search, listings, downloads"]
S -- "headless Chromium,<br>signed-in cookie jar" --> U["/svc/decks/*, your /svc/shared/*<br>your decks and listings:<br>list, share, remove, delete"]
B[Local browser profile] -. "session import" .-> SShared-deck reads go out without cookies, cached for as long as AnkiWeb allows: ten minutes.
After a few anonymous downloads AnkiWeb asks for a login, and the download is retried with your session, from its stored cookie when that is enough.
Calls on your account go through one headless browser, one at a time, closed after five idle minutes.
Requests are spaced at least a second apart, since AnkiWeb answers
429after about four searches a minute.
More
docs/cli.md: every command-line flag
docs/session.md: the data directory, signing in, browser import
docs/shared-decks.md: search, details, downloads and conversion to Markdown
docs/sharing.md: the share flow, removing a listing, and their confirmation
docs/deleting.md: deleting a deck, and its stricter confirmation
docs/errors.md: what a failing tool returns, and request pacing
docs/ankiweb.md: every AnkiWeb endpoint used, as observed
CONTRIBUTING.md: setup, gates, and what to update when AnkiWeb changes
NOTICE: the browser import is ported from linkedin-mcp-server
Available Tools
11 toolsclose_sessionClose the browserAIdempotent
Close the server's headless browser to free its memory, once any call in progress has finished: the one for account, or without it every one open. The AnkiWeb session stays stored, and the next call that needs the browser starts it again. A browser also closes by itself after five idle minutes.
Inputs: account. Returns: closed
convert_deck_to_markdownConvert a deck to MarkdownA
Convert a local .apkg, such as one download_shared_deck saved, to a Flashcard Markdown file the assistant can read. It goes in a new folder named after the package, with the images its cards use under .images/; nothing existing is replaced. Only basic front-and-back notes convert: cloze and other note types are counted in diagnostics, and review history is not kept.
Inputs: path (required), title, directory. Returns: cards, title, directory, mediaFiles, +3 more
delete_deckDelete a deckADestructiveIdempotent
Delete one of the signed-in user's decks, with its subdecks and every card in them, from their AnkiWeb collection. The deletion reaches every device on its next sync and cannot be undone.
Without confirm, nothing is deleted: the call finds the deck and returns a preview of what goes. Show that preview to the user and wait for their explicit go-ahead before calling again with confirm: true.
The confirmed call must name the deck by its numeric id, as the preview gives it, never by name.
With more than one AnkiWeb account stored, the preview names the one the deck belongs to, and the confirmed call must name it in account.
Needs an AnkiWeb session.
Inputs: deck (required), account, confirm. Returns: deck, status, account, listings, +1 more
list_my_decksList my decksARead-only
List the decks synced to the signed-in AnkiWeb account, parents before their subdecks, with due counts and card totals. Needs an AnkiWeb session.
Inputs: account. Returns: decks, currentDeckId, mediaSizeBytes, collectionSizeBytes
server_statusServer statusARead-only
Report the server version, where sessions and downloads are kept, and whether an AnkiWeb session is stored for each account. With validate, also ask AnkiWeb whether each session, or the one for account, is still signed in.
Inputs: account, validate. Returns: dataDir, version, accounts, readOnly, +1 more
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 11 tools
Each tool has a clear, distinct role: search/get/download shared decks are separate stages, list_my_decks and list_my_shared_decks are clearly differentiated, and share/unshare/delete are distinct account actions. Status, session cleanup, and local conversion do not overlap with the AnkiWeb catalogue tools.
Names use consistent snake_case and mostly follow verb_noun patterns such as search_shared_decks, download_shared_deck, and delete_deck. The main exception is server_status, which is a noun phrase rather than an action verb.
The set has 11 tools, which is well within a reasonable range and each tool corresponds to a meaningful AnkiWeb or deck-conversion operation. There is no obvious padding or missing category that would justify a different count.
The surface covers the shared-deck lifecycle well: search, inspect, download, share, unshare, and delete, plus account deck listings and local conversion. Minor gaps remain around account/session setup or deck update/import operations, but core workflows are covered.
Maintenance
Related MCP Connectors
Web search, data extraction and controlled browser automation for AI assistants via OAuth.
Turn text, files, URLs, or photos into Anki flashcard decks from your AI assistant.
A real browser for your agent: screenshots, page checks, Markdown and PDFs.
Web search, page reading, site crawling, data extraction and cited research. OAuth sign-in.
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceEnables LLMs to interact with Anki via AnkiConnect for creating, searching, and managing flashcards, decks, and note types.1MIT
- AlicenseNot gradedqualityDmaintenanceEnables LLMs to interact with Anki flashcard collections, including deck management, note search, viewing contents, and editing fields.16 npmMIT
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to create and manage Anki cards through AnkiConnect, including decks, card creation, search, updates, deletion, and mobile sync.MIT
- FlicenseBqualityCmaintenanceEnables AI assistants to directly manage Anki flashcards, decks, notetypes, tags, and media, with support for batch operations, searches, and deck exports via file-based input/output.23-