LabscoMCP early access ↗
sergey-mamulchenkoMCP SERVER

Anki Connect

Manage your Anki notes from an assistant through the AnkiConnect plugin — with a raw RPC escape hatch.

by sergey-mamulchenko ↗Education, Tutoring & Study ToolsCommunity

LABSCO SUMMARY

Named tools for the common path, raw RPC for the rest.

AnkiConnect's API is large and mostly things you will never ask for, so wrapping only the note operations keeps the tool list short — and leaving the raw request exposed means the long tail is still reachable without waiting for someone to wrap it. The catch is structural: Anki has to be open, because the plugin is the only way in.

What it is

A Node server that talks to the AnkiConnect plugin on your Anki desktop app. It defines concrete tools for the common note operations, and keeps the base RPC request available so anything AnkiConnect can do is still reachable even when there is no purpose-built tool for it.

What you get

  • Named tools for the key requests that manipulate notes
  • The underlying RPC request kept as a tool, so arbitrary AnkiConnect calls stay available
  • Everything goes to 127.0.0.1:8765 on your own machine — the plugin's local endpoint, nothing remote

Requirements

The Anki desktop app with the AnkiConnect plugin installed, and Anki running whenever you want to use the server — the tools reach it over 127.0.0.1:8765. Clone the repository and build it: corepack enable then yarn install and yarn build, or the npm equivalent. Point your client at node with the path to the built index.js. No account and no key.

Setup effort

Build from source — clone the repository and build it, then point your client at the built dist/index.js

See installation options