Skip to main content
Glama

Related Servers

Alternatives to anki-agent

No user-submitted related servers found.

    Related Servers

    • A
      license
      B
      quality
      C
      maintenance
      Enables AI assistants to manage Anki flashcards, decks, note types, tags, and media via AnkiConnect. Supports operations like adding, editing, finding, and syncing cards through a local MCP server.
      100
      MIT
    • F
      license
      Not graded
      quality
      A
      maintenance
      Exposes Anki flashcard collections to AI assistants via MCP, enabling AI-powered study sessions, card creation, deck management, and review workflows. Supports comprehensive collection operations including search, media management, and note type customization.
      98
      -
    • A
      license
      A
      quality
      A
      maintenance
      Lets Claude and other MCP clients manage an Anki collection through AnkiConnect: create decks, add notes, import TSV/CSV files, search, edit, move, rename and delete cards, generate text-to-speech pronunciation audio into note fields, and sync with AnkiWeb. Changes are guarded by preview-and-confirm tokens, automatic backups, dry runs, and read-only or delete-disabled modes.
      17
      1
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      Enables reading and writing to your local Anki collection through AnkiConnect, allowing creation, update, and search of notes and decks from MCP clients like Claude Desktop.
      11
      MIT
    • F
      license
      Not graded
      quality
      D
      maintenance
      Provides programmatic access to Anki flashcard operations through the AnkiConnect API, allowing users to list and create decks and cards. It enables seamless management of flashcards directly from MCP-compatible clients like Claude Desktop.
      -

    TDQS

    A3.8/5.0

    Scored across 15 tools

    Disambiguation5/5

    Each tool targets a distinct resource+action, and the preview/apply pairs (preview_notes/create_notes, preview_delete_cards/delete_cards, preview_delete_deck/delete_deck) are explicitly framed as dry-run versus commit steps, so an agent can tell them apart without guesswork. Card-level versus deck-level deletion is also clearly separated by scope.

    Naming Consistency4/5

    Nearly every tool follows a snake_case verb_noun pattern (list_decks, create_deck, rename_deck, move_cards, search_notes, delete_deck), including the compound preview_* prefix. The lone outlier is connection_status, a noun-only status check, which is a minor but visible deviation.

    Tool Count5/5

    At 15 tools the surface is dense but every tool maps to a real operation (connection check, deck CRUD, note lifecycle, card moves/deletes, backup), with no redundant wrappers. Nothing feels padded or missing from the count perspective.

    Completeness4/5

    Core lifecycle is well covered: decks (list/create/rename/delete), notes (search/preview/create/update), cards (move/preview-delete/delete), plus backup. Gaps remain around tags (no tag add/remove/list), card scheduling controls (suspend/bury/reset), and direct single-note deletion, which agents must work around via card deletion.

    Maintenance

    ActivityNo data
    ResponsivenessSyncing