Skip to main content
Glama
nietus

Anki MCP Server

by nietus
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to Anki MCP Server

No user-submitted related servers found.

    Related Servers

    • anki-mcp

      icem0
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables LLM agents to manage Anki cards headlessly via Model Context Protocol, including deck listing, card creation, editing, deletion, search, and media import. It runs 24/7 without Anki Desktop.
      Apache 2.0

    • Anki MCP Server

      ethangillani
      A
      license
      Not graded
      quality
      D
      maintenance
      A Model Context Protocol server that allows LLMs to interact with Anki flashcard software, enabling functions like creating decks, adding notes, searching cards, and managing flashcard content through natural language.
      76 npm
      1
      MIT

    • Anki MCP Server

      stefanwille
      A
      license
      B
      quality
      C
      maintenance
      A Model Context Protocol server for managing Anki flashcards via AnkiConnect, enabling AI assistants to create, read, and update cards.
      8
      13 npm
      MIT
    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

    ActivitySlowing
    ResponsivenessUnresponsive

    Resources