Skip to main content
Glama
deenesjakoruzh
nietus

Anki MCP Server

by nietus
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

anki-mcp

Schmiedeabzeichen

MCP-Server für Anki. Dieser Server ermöglicht die Interaktion mit Anki über das Model Context Protocol (MCP). Er ermöglicht es Benutzern, Karteikarten, Stapel und Überprüfungsprozesse programmgesteuert zu verwalten.

Voraussetzungen

  • Node.js und npm installiert.

  • AnkiConnect-Plugin installiert und in Anki ausgeführt.

Related MCP server: Anki MCP Server

Einrichtung und Ausführung

Es wird dringend empfohlen, lokal zu laufen, da Anki Connect nur lokal funktioniert

So führen Sie es lokal aus:

  1. Klonen Sie das Repository:

    git clone https://github.com/nietus/anki-mcp

  2. Installieren Sie Abhängigkeiten:

    npm install

  3. Erstellen Sie das Projekt: Das prepare in package.json sollte den Build nach der Installation automatisch ausführen. Wenn Sie manuell erstellen müssen:

    npm run build

    Dieser Befehl kompiliert den TypeScript-Code und macht das Client-Skript ausführbar.

  4. Integration mit Cursoreinstellungen für Windows

    "anki": {
      "command": "cmd",
      "args": [
        "/c",
        "node",
        "c:/Users/-/Downloads/anki-mcp/build/client.js"
      ]
    }

Verfügbare Tools

Um die Tools zu debuggen, verwenden Sie

npm run inspector

Der Server bietet die folgenden Tools zur Interaktion mit Anki:

  • update_cards :

    • Beschreibung: Nachdem der Benutzer die Karten beantwortet hat, die Sie ihm zur Befragung vorgelegt haben, können Sie sie mit diesem Tool als beantwortet markieren und ihre Leichtigkeit aktualisieren.

    • Eingabe: Ein Array von Antworten, jede mit cardId (Nummer) und ease (Nummer, 1-4).

  • add_card :

    • Beschreibung: Erstellen Sie eine neue Karteikarte in Anki. Beachten Sie, dass der Inhalt HTML verwendet.

      • Zeilenumbrüche: <br>

      • Code: <pre style="background-color: transparent; padding: 10px; border-radius: 5px;">

      • Listen: <ol> und <li>

      • Fett: <strong>

      • Kursiv: <em>

    • Eingang:

      • fields : (Objekt) Ein Objekt, bei dem die Schlüssel Feldnamen (z. B. „Hanzi“, „Pinyin“) und die Werte deren HTML-Inhalt sind.

      • modelName : (Zeichenfolge) Der Name des zu verwendenden Anki-Notiztyps (Modells).

      • deckName : (optionale Zeichenfolge) Der Name des Decks, zu dem die Karte hinzugefügt werden soll. Standardmäßig wird das aktuelle Deck oder „Default“ verwendet.

      • tags : (optionales Array von Zeichenfolgen) Eine Liste von Tags, die der Notiz hinzugefügt werden sollen.

  • get_due_cards :

    • Beschreibung: Gibt eine bestimmte Anzahl von Karten zurück, die zur Überprüfung fällig sind.

    • Eingabe: num (Zahl).

  • get_new_cards :

    • Beschreibung: Gibt eine bestimmte Anzahl neuer und ungesehener Karten zurück.

    • Eingabe: num (Zahl).

  • get-deck-names :

    • Beschreibung: Holen Sie sich eine Liste aller Anki-Decknamen.

    • Eingabe: Keine.

  • find-cards :

    • Beschreibung: Finden Sie Karten mithilfe einer einfachen Anki-Suchabfrage. Gibt detaillierte Karteninformationen einschließlich Feldern zurück.

    • Eingabe: query (Zeichenfolge, z. B. 'deck:Default -tag:test' oder '"deck:My Deck" tag:important' ). Um nach leeren Feldern zu filtern, verwenden Sie '-FieldName:_*' (z. B. '-Hanzi:_*' ).

  • update-note-fields :

    • Beschreibung: Aktualisieren Sie bestimmte Felder einer bestimmten Anki-Notiz.

    • Eingabe: noteId (Zahl), fields (Objekt, zB {"Front": "New Q", "Back": "New A"} ).

  • create_deck :

    • Beschreibung: Erstellen Sie ein neues Anki-Deck.

    • Eingabe: deckName (Zeichenfolge).

  • bulk_update_notes :

    • Beschreibung: Aktualisieren Sie bestimmte Felder für mehrere Anki-Notizen.

    • Eingabe: Ein Array von notes , wobei jede Notiz noteId (Nummer) und fields (Objekt) hat.

  • get_model_names :

    • Beschreibung: Listet alle verfügbaren Anki-Notiztypen/Modellnamen auf.

    • Eingabe: Keine.

  • get_model_details :

    • Beschreibung: Ruft die Felder, Kartenvorlagen und CSS-Stile für einen angegebenen Notiztyp ab.

    • Eingabe: modelName (Zeichenfolge).

  • get_deck_model_info :

    • Beschreibung: Ruft Informationen zu den in einem bestimmten Stapel verwendeten Notentypen (Modellen) ab. Hilft festzustellen, ob ein einzelnes Modell oder mehrere Modelle verwendet werden oder ob der Stapel leer oder nicht vorhanden ist.

    • Eingabe: deckName (Zeichenfolge).

    • Ausgabe: Ein Objekt mit deckName , status (z. B. „single_model_found“, „multiple_models_found“, „no_notes_found“, „deck_not_found“) und bedingt modelName (Zeichenfolge) oder modelNames (Array von Zeichenfolgen).

  • add_note_type_field :

    • Beschreibung: Fügt einem Notiztyp ein neues Feld hinzu.

    • Eingabe: modelName (Zeichenfolge), fieldName (Zeichenfolge).

  • remove_note_type_field :

    • Beschreibung: Entfernt ein vorhandenes Feld aus einem Notiztyp.

    • Eingabe: modelName (Zeichenfolge), fieldName (Zeichenfolge).

  • rename_note_type_field :

    • Beschreibung: Benennt ein Feld in einem Notiztyp um.

    • Eingabe: modelName (Zeichenfolge), oldFieldName (Zeichenfolge), newFieldName (Zeichenfolge).

  • reposition_note_type_field :

    • Beschreibung: Ändert die Reihenfolge (Index) eines Feldes in einem Notiztyp.

    • Eingabe: modelName (Zeichenfolge), fieldName (Zeichenfolge), index (Zahl).

  • update_note_type_templates :

    • Beschreibung: Aktualisiert die HTML-Vorlagen (z. B. Vorder- und Rückseite) für die Karten eines Notiztyps.

    • Eingabe: modelName (Zeichenfolge), templates (Objekt, z. B. {"Card 1": {"Front": "html", "Back": "html"}} ).

  • update_note_type_styling :

    • Beschreibung: Aktualisiert das CSS-Styling für einen Notiztyp.

    • Eingabe: modelName (Zeichenfolge), css (Zeichenfolge).

  • create_model :

    • Beschreibung: Erstellt einen neuen Anki-Notiztyp (Modell).

    • Eingabe: modelName (Zeichenfolge), fieldNames (Array von Zeichenfolgen), cardTemplates (Array von Objekten, jedes mit den HTML-Zeichenfolgen Name , Front und Back “), css (optionale Zeichenfolge), isCloze (optionaler Boolescher Wert, standardmäßig „false“), modelType (optionale Zeichenfolge, standardmäßig „Standard“).

  • add_bulk :

    • Beschreibung: Fügt mehrere Karteikarten in einem einzigen Vorgang zu Anki hinzu. Der Notizinhalt verwendet HTML. Mit diesem Tool können Sie mehrere Notizen (Karten) gleichzeitig hinzufügen.

    • Eingabe: Ein Array von notes , wobei jedes Notizobjekt Folgendes hat:

      • fields : (Objekt) Ein Objekt, bei dem die Schlüssel Feldnamen und die Werte deren HTML-Inhalt sind.

      • modelName : (Zeichenfolge) Der Name des Anki-Notiztyps (Modells), der für diese Notiz verwendet werden soll.

      • deckName : (optionale Zeichenfolge) Der Name des Decks für diese Notiz. Der Standardwert ist „Default“.

      • tags : (optionales Array von Zeichenfolgen) Eine Liste von Tags für diese Notiz.

Weitere Informationen finden Sie hier: Anki Integration | Smithery

Available Tools

3 tools
anki_add_noteC

Add a flashcard to an Anki deck

ParametersJSON Schema
NameRequiredDescriptionDefault
backYesBack of the flashcard
deckNameYesThe target deck name
frontYesFront of the flashcard

TDQS

C2.9/5.0
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description carries full burden for behavioral disclosure. It states the action ('Add') which implies a write/mutation operation, but doesn't disclose any behavioral traits like whether it requires specific permissions, what happens if the deck doesn't exist, error conditions, or how the system responds to successful addition. The description is minimal and lacks operational context.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is extremely concise with a single, clear sentence that communicates the core purpose without any wasted words. It's appropriately sized for a straightforward tool and gets directly to the point with no unnecessary elaboration.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a mutation tool with no annotations and no output schema, the description is insufficiently complete. It doesn't explain what happens after adding the flashcard, potential error conditions, or how to verify success. Given the tool's complexity as a write operation and the lack of structured behavioral information, more context about the operation's behavior and outcomes would be valuable.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The description adds no parameter information beyond what's already in the schema, which has 100% coverage with clear descriptions for all three parameters. The baseline score of 3 reflects adequate schema documentation, but the description doesn't provide additional context about parameter relationships, constraints, or usage patterns.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action ('Add') and resource ('flashcard to an Anki deck'), making the purpose immediately understandable. It distinguishes from sibling 'anki_add_notes' by specifying singular 'flashcard' vs. plural 'notes', but doesn't explicitly differentiate from 'anki_create_deck' which creates decks rather than flashcards.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention when to choose this over 'anki_add_notes' (for single vs. multiple cards) or 'anki_create_deck' (for creating decks before adding cards). No prerequisites or contextual usage information is provided.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

anki_add_notesC

Add multiple flashcards to an Anki deck

ParametersJSON Schema
NameRequiredDescriptionDefault
cardsYes
deckNameYesThe target deck name

TDQS

C2.9/5.0
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the action ('Add multiple flashcards') but doesn't cover critical aspects like whether this is a write operation (implied but not confirmed), error handling (e.g., if the deck doesn't exist), or response format. This leaves significant gaps for an agent to understand the tool's behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, clear sentence that efficiently conveys the core purpose without unnecessary words. It's front-loaded and appropriately sized for the tool's complexity, with no wasted information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the lack of annotations, no output schema, and incomplete parameter documentation (50% coverage), the description is insufficient. It doesn't address key contextual elements like mutation effects, error scenarios, or return values, making it inadequate for safe and effective tool invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The description mentions 'multiple flashcards' and 'Anki deck', which loosely maps to the 'cards' array and 'deckName' parameters. However, with 50% schema description coverage (only 'deckName' has a description), the description doesn't add meaningful details about parameter formats, constraints, or the structure of card objects (front/back fields). It partially compensates but not fully.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action ('Add multiple flashcards') and resource ('to an Anki deck'), making the purpose immediately understandable. However, it doesn't explicitly differentiate from the sibling tool 'anki_add_note' (singular vs. plural), which could cause confusion about when to use each.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus alternatives like 'anki_add_note' (for single cards) or 'anki_create_deck' (for deck creation). There's no mention of prerequisites, such as whether the deck must already exist, or any contextual limitations.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

anki_create_deckC

Create a new Anki deck

ParametersJSON Schema
NameRequiredDescriptionDefault
deckNameYesThe name of the deck to create

TDQS

C2.9/5.0
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description carries full burden but only states the basic action. It doesn't disclose behavioral traits such as error handling (e.g., what happens if the deck already exists), permission requirements, side effects, or response format, which are critical for a creation tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, direct sentence with no wasted words, making it highly concise and front-loaded. It efficiently communicates the core purpose without unnecessary elaboration.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a creation tool with no annotations and no output schema, the description is insufficient. It lacks details on behavior, error cases, and output, leaving gaps that could hinder an agent's ability to use the tool effectively in complex scenarios.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, with the parameter 'deckName' clearly documented in the schema. The description doesn't add any meaning beyond the schema, such as naming conventions or constraints, but the schema provides adequate baseline information.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action ('Create') and resource ('new Anki deck'), making the purpose immediately understandable. However, it doesn't differentiate from sibling tools like 'anki_add_note' or 'anki_add_notes', which are about adding content rather than creating deck structure.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance is provided on when to use this tool versus alternatives. The description doesn't mention prerequisites (e.g., whether the deck must not already exist), constraints, or relationships to sibling tools, leaving the agent to infer usage context.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

  1. 3 tool updatesv1.0.0
    • First observedanki_add_note
    • First observedanki_add_notes
    • First observedanki_create_deck
Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

C2.9/5.0

Scored across 3 tools

Disambiguation3/5

The tools have overlapping purposes, as 'anki_add_note' and 'anki_add_notes' both handle adding flashcards, which could cause confusion for an agent deciding between single vs. batch operations. However, the descriptions clarify the distinction (single vs. multiple), mitigating some ambiguity. The 'anki_create_deck' tool is clearly distinct, focusing on deck management rather than note addition.

Naming Consistency5/5

All tool names follow a consistent 'anki_' prefix and snake_case pattern (e.g., anki_add_note, anki_add_notes, anki_create_deck), with clear verb_noun structures. This predictability makes it easy for agents to understand and navigate the tool set without confusion from mixed conventions.

Tool Count2/5

With only 3 tools, the server feels thin for managing Anki flashcards, a domain that typically involves operations like updating, deleting, reviewing, or searching notes and decks. The count is too low for the apparent scope, lacking essential CRUD lifecycle coverage beyond basic creation, which may limit agent functionality.

Completeness2/5

The tool set is severely incomplete for Anki management, covering only note addition and deck creation. Obvious gaps include updating or deleting notes/decks, listing or searching existing content, and handling reviews or scheduling—core aspects of flashcard workflows. This will likely cause agent failures when trying to perform common tasks beyond initial setup.

Maintenance

ActivityMaintained
ResponsivenessNo issues

Resources

Related MCP Connectors

Related MCP Servers

Appeared in Searches