Skip to main content
Glama
ctjmaxwell

Anki Flashcard MCP

by ctjmaxwell
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

No arguments

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
add_anki_noteC
    Adds a SINGLE Anki note. Use this for adding one card at a time.

    :param deck: The name of the deck to add the note to.
    :param front: The content for the front of the card.
    :param back: The content for the back of the card.
    :param tags: A list of tags to add to the note.
add_multiple_anki_notesB
    Adds a BATCH of multiple Anki notes in a single, efficient operation. Use this for adding more than one card at once.

    :param deck: The name of the deck to add the notes to.
    :param notes: A list of notes to add. Each note should be a dictionary with "Front" and "Back" keys.
    :param tags: A list of tags to add to every note in the batch.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

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.7/5.0

Scored across 2 tools

Disambiguation3/5

The two tools are clearly distinguished by single vs. batch operation, and the descriptions explicitly state when to use each. However, there is still some ambiguity since both serve the same fundamental purpose (adding notes to a deck), and an agent might reasonably pick either for a single-note add when the batch tool would also work.

Naming Consistency3/5

Both tools follow a verb_noun style with 'add' as the verb, which is consistent. However, the naming is somewhat redundant ('add_anki_note' vs 'add_multiple_anki_notes') rather than a clean noun-based pattern like 'create_note' and 'create_notes', and the repetition of 'anki' in both is verbose.

Tool Count1/5

Only two tools exist, and they cover only the 'add' operation. For a flashcard MCP server, this is extremely thin — there are no tools to retrieve, update, delete, search, or review notes or decks. A server this narrow is difficult to justify as useful for real workflows.

Completeness1/5

The surface only supports adding notes. There are no get/update/delete operations for notes, no deck management, no card review/study operations, and no search capability. This is a severely incomplete surface for managing Anki flashcards and will cause agents to hit dead ends immediately after adding content.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources