de en es ja ko ru zh

Anki MCP

Name: Anki MCP
Author: arielbk

by arielbk

Overview Schema Source Related Servers Discussions Admin

TypeScript

Local

🧠 Анки МКП

Пакет NPM yanki-connect Лицензия: Массачусетский технологический институт

Трансформируйте свой опыт работы с карточками Anki с помощью ИИ! Этот сервер MCP (Model Context Protocol) связывает вашу коллекцию карточек Anki с помощниками ИИ, такими как Клод, позволяя вести естественные беседы о ваших учебных материалах.

🚀 Что вы можете сделать?

Представьте себе, что у вас есть наставник на основе искусственного интеллекта, который знает всю вашу коллекцию карточек и может:

📚 Интерактивное обучение

«Проверь меня на знание японской лексики, которую я не видел 3 дня»
«Проверьте меня на сложных картах из моей медицинской колоды»
«Покажите мне карты, с которыми у меня в последнее время возникли трудности»

✨ Создание интеллектуального контента

«Создание карточек по теме фотосинтеза с диаграммами»
«Превратите эту главу PDF в карточки для повторения с интервалами»
«Создать карточки удаления из моих лекционных записей»

🔍 Мощная аналитика

«С какими темами у меня больше всего проблем?»
«Покажи мне мои учебные планы за последний месяц»
«Каков мой процент удержания для разных типов карт?»

🎯 Массовые операции

«Пометьте все мои карточки по химии как «подготовка к экзамену»»
«Переместите карточки с низким уровнем запоминания в колоду для интенсивного обзора»
«Найти и исправить дубликаты карт в моих колодах»

Related MCP server: Anki MCP Server

🎯 Особенности

Полная интеграция с Anki : полный доступ к колодам, картам, заметкам и статистике через все 115 методов API AnkiConnect
Разговорный интерфейс : команды на естественном языке через вашего помощника на основе искусственного интеллекта
Массовые операции : эффективное управление тысячами карт одновременно
Статистика в реальном времени : получайте информацию о ходе вашего обучения
Поддержка мультимедиа : обработка изображений, аудио и других медиафайлов на ваших карточках.
Расширенные запросы : найдите карты, используя сложные критерии поиска
Безопасность типов : полностью типизированный API с комплексной обработкой ошибок

🛠 Технический стек

Node.js : среда выполнения (требуется 18+)
TypeScript : безопасность типов и опыт разработчика
MCP SDK : реализация протокола контекста модели
yanki-connect : 🙏 Полностью типизированный, изоморфный API-клиент AnkiConnect
tsup : Быстрый упаковщик TypeScript
PNPM : Эффективный менеджер пакетов

Особая благодарность библиотеке yanki-connect за предоставление надежного интерфейса AnkiConnect, обеспечивающего эту интеграцию!

📋 Предварительные условия

1. Установите Anki

Загрузите и установите Anki, если вы еще этого не сделали.

2. Установите плагин AnkiConnect

Открыть Анки
Перейдите в Инструменты → Дополнения.
Нажмите «Получить дополнения»...
Введите код: 2055492159
Перезапустить Анки

📋 Требования к версии: Для полной совместимости этому серверу требуется AnkiConnect версии 25.2.25.0 или более новой (выпущенной 2025-02-25). Большинство функций работают и со старыми версиями, но мы рекомендуем обновиться для лучшего опыта.

3. Настройте AnkiConnect (необязательно)

AnkiConnect работает «из коробки», но вы можете настроить параметры:

Перейдите в Инструменты → Дополнения.
Выберите AnkiConnect и нажмите «Конфигурация».
Настройки по умолчанию должны подойти большинству пользователей.

🚀 Быстрый старт

Вариант 1: использование с Claude Desktop (рекомендуется)

Установить пакет
```
npm install -g @arielbk/anki-mcp
```
Настроить рабочий стол Клода
Отредактируйте файл конфигурации Claude Desktop:
macOS : ~/Library/Application Support/Claude/claude_desktop_config.jsonWindows : %APPDATA%\Claude\claude_desktop_config.json
Добавьте эту конфигурацию:
```
{
  "mcpServers": {
    "anki": {
      "command": "anki-mcp",
      "args": []
    }
  }
}
```
Перезагрузить рабочий стол Клода
Начните использовать его!
- Убедитесь, что Anki запущена с включенным AnkiConnect.
- Спросите Клода: «Покажи мне мои колоды Anki» или «Проверь меня с помощью 5 карт»

💡 Совет от профессионалов: вы можете проверить свою настройку, задавая Клоду простые вопросы, например : «Сколько у меня колод Anki?» или «Что в моей самой большой колоде?»

Вариант 2: Настройка разработки

Клонировать репозиторий

git clone https://github.com/arielbk/anki-mcp.git
cd anki-mcp

Установить зависимости
```
pnpm install
```
Построить проект
```
pnpm build
```

Протестируйте сервер

# Use the MCP inspector to test functionality
pnpm inspect

Вариант 3: использование с другими клиентами MCP

Этот сервер работает с любым MCP-совместимым клиентом. Вы также можете использовать его с:

MCP Inspector : интерактивный инструмент отладки
Cline : расширение VS Code для кодирования ИИ
Пользовательские клиенты MCP : создайте свои собственные клиенты с помощью MCP SDK

Для stdio-транспорта выполните:

node dist/index.js

🎮 Примеры использования

После настройки Claude Desktop вы сможете вести естественные беседы, например:

📖 Учебные сессии

You: "I have a Japanese exam tomorrow. Can you quiz me on Hiragana cards I haven't reviewed in a week?"

Claude: I'll find your Hiragana cards that need review and start a quiz session...

📝 Создание контента

You: "Create flashcards for the major battles of World War II with dates and significance"

Claude: I'll create comprehensive flashcards covering the key WWII battles...

📊 Аналитика исследования

You: "How am I doing with my medical terminology deck? Show me my weak areas."

Claude: Let me analyze your performance on the medical terminology deck...

🏷️ Организация

You: "Tag all cards about cardiovascular system with 'cardiology' and move them to my MCAT prep deck"

Claude: I'll help you organize those cards...

🔧 Доступные инструменты и ресурсы

Этот сервер MCP обеспечивает полный доступ к вашей коллекции Anki с помощью следующих возможностей:

📚 Управление палубой

Список всех колод со статистикой
Создавайте новые колоды
Переименовывать и удалять колоды
Получить конфигурацию колоды

🗂️ Операции с картами

Найти карты по критериям поиска
Карточки с ответами (имитация обзоров)
Получить информацию о карте и статистику
Приостановить/разблокировать карты
Массовые операции с картами

📝 Управление заметками

Добавляйте новые заметки с пользовательскими полями
Обновить существующие заметки
Удалить заметки
Найти заметки по поисковому запросу
Массовые операции с банкнотами

📊 Статистика и аналитика

Статистика колоды и показатели производительности
Данные об удобстве и интервалах карт
Обзор истории и закономерностей
Анализ прогресса обучения

🎨 Медиа и модели

Доступ к типам заметок и определениям полей
Управление медиафайлами
Поддержка настройки шаблона

🔍 Расширенные функции

Сложные поисковые запросы с использованием синтаксиса поиска Anki
Пакетные операции для эффективности
Синхронизация в реальном времени с Anki
Обработка ошибок и проверка
Организованные методы API, сгруппированные по функциональности (карты, колоды, заметки, модели, статистика, медиа и т. д.)
Прямой доступ ко всем 115 методам API AnkiConnect с полной безопасностью типов

🛠 Развитие

# Run in development mode with auto-reloading
pnpm dev

# Lint the code
pnpm lint

# Format the code
pnpm format

# Test with MCP inspector
pnpm inspect

🔧 Конфигурация

Настройки AnkiConnect

По умолчанию сервер подключается к AnkiConnect на localhost:8765 . Если вы настроили конфигурацию AnkiConnect, вам может потребоваться изменить настройки подключения.

Важно : убедитесь, что Anki запущена и AnkiConnect установлен перед использованием сервера MCP. Сервер не сможет подключиться, если AnkiConnect недоступен.

💡 Примечание: Базовая библиотека yanki-connect поддерживает автоматический запуск Anki на macOS, но эта функция в настоящее время не представлена в конфигурации сервера MCP. Вам нужно будет запустить Anki вручную.

Расширенная конфигурация рабочего стола Claude

Для опытных пользователей можно передать дополнительные параметры:

{
  "mcpServers": {
    "anki": {
      "command": "anki-mcp",
      "args": ["--verbose"],
      "env": {
        "ANKI_CONNECT_HOST": "localhost",
        "ANKI_CONNECT_PORT": "8765"
      }
    }
  }
}

Поиск неисправностей

Распространенные проблемы:

«Не удалось подключиться к AnkiConnect» : убедитесь, что Anki запущен и установлен плагин AnkiConnect.
«Колоды не найдены» : убедитесь, что у вас есть хотя бы одна колода в Anki
Клод не отвечает : перезапустите Claude Desktop после изменения конфигурации.
Ошибки разрешений : проверьте, что глобальная установка npm работает правильно с помощью npm list -g @arielbk/anki-mcp

🤝 Вклад

Мы приветствуем ваши вклады! Пожалуйста:

Форк репозитория
Создать ветку функций
Внесите изменения
Добавьте тесты, если применимо
Отправить запрос на извлечение

📜 Лицензия

MIT — подробности см. в файле LICENSE .

🙏 Благодарности

yanki-connect — превосходный клиент TypeScript для AnkiConnect
AnkiConnect — плагин, делающий возможной автоматизацию Anki
Протокол контекста модели — обеспечение бесшовной интеграции ИИ

Измените свой опыт работы с карточками с помощью бесед на основе искусственного интеллекта! 🚀

Available Tools

7 tools

anki_operationsD

ParametersJSON Schema

Name	Required	Description
`operation`	Yes	Anki utility operation
`deckName`	No	Deck name to export
`filePath`	No	File path for export/import
`includeSched`	No	Include scheduling in export
`filename`	No	Media filename
`mediaData`	No	Base64 encoded media data
`mediaUrl`	No	URL to download media from
`pattern`	No	Pattern to match media files

TDQS

D1/5.0

Behavior1/5

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

Tool has no description.

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

Conciseness1/5

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

Tool has no description.

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

Completeness1/5

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

Tool has no description.

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

Parameters1/5

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

Tool has no description.

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

Purpose1/5

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

Tool has no description.

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

Usage Guidelines1/5

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

Tool has no description.

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

get_analyticsD

ParametersJSON Schema

Name	Required	Description
`scope`	Yes	Analytics scope
`deckName`	No	Deck name for deck-specific stats
`cardIds`	No	Card IDs for detailed analysis
`startTimestamp`	No	Start timestamp for review history
`wholeCollection`	No	Get whole collection stats vs current deck

TDQS

D1/5.0

Behavior1/5

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

Tool has no description.

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

Conciseness1/5

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

Tool has no description.

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

Completeness1/5

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

Tool has no description.

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

Parameters1/5

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

Tool has no description.

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

Purpose1/5

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

Tool has no description.

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

Usage Guidelines1/5

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

Tool has no description.

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

get_media_fileD

ParametersJSON Schema

Name	Required	Description	Default
`filename`	Yes	Media filename referenced in Anki cards (e.g., "image.png")

TDQS

D1/5.0

Behavior1/5

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

Tool has no description.

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

Conciseness1/5

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

Tool has no description.

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

Completeness1/5

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

Tool has no description.

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

Parameters1/5

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

Tool has no description.

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

Purpose1/5

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

Tool has no description.

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

Usage Guidelines1/5

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

Tool has no description.

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

manage_decksD

ParametersJSON Schema

Name	Required	Description
`operation`	Yes	Deck management operation
`deckName`	No	Deck name
`deckNames`	No	Deck names (for batch operations)
`deleteCards`	No	Delete cards when deleting deck
`cardIds`	No	Card IDs to move
`targetDeck`	No	Target deck for moving cards
`configId`	No	Config ID to apply

TDQS

D1/5.0

Behavior1/5

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

Tool has no description.

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

Conciseness1/5

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

Tool has no description.

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

Completeness1/5

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

Tool has no description.

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

Parameters1/5

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

Tool has no description.

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

Purpose1/5

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

Tool has no description.

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

Usage Guidelines1/5

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

Tool has no description.

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

manage_flashcardsD

ParametersJSON Schema

Name	Required	Description
`operation`	Yes	The flashcard operation to perform
`deckName`	No	Deck name (for create operations)
`modelName`	No	Note type/model name (for create operations)
`fields`	No	Field name-value pairs (for create/update)
`tags`	No	Tags to add/remove or set
`notes`	No	Array of notes to create (for create_batch)
`noteId`	No	Note ID (for update/delete single note)
`noteIds`	No	Note IDs (for delete multiple)
`query`	No	Anki search query (for find operation)
`includeDetails`	No	Include detailed note info (for find)
`limit`	No	Max results to return (default: 50, recommended to prevent context overflow)
`offset`	No	Number of results to skip for pagination (default: 0)
`cardIds`	No	Card IDs to get info for

TDQS

D1/5.0

Behavior1/5

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

Tool has no description.

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

Conciseness1/5

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

Tool has no description.

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

Completeness1/5

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

Tool has no description.

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

Parameters1/5

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

Tool has no description.

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

Purpose1/5

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

Tool has no description.

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

Usage Guidelines1/5

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

Tool has no description.

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

manage_modelsD

ParametersJSON Schema

Name	Required	Description
`operation`	Yes	Model management operation
`modelName`	No	Model/note type name
`fields`	No	Field names in order (for create)
`templates`	No	Card templates (for create)
`css`	No	CSS styling
`isCloze`	No	Is cloze deletion type
`fieldName`	No	Field name
`newFieldName`	No	New field name (for rename)
`fieldIndex`	No	Field index position
`templateName`	No	Template name
`template`	No	Template content

TDQS

D1/5.0

Behavior1/5

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

Tool has no description.

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

Conciseness1/5

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

Tool has no description.

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

Completeness1/5

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

Tool has no description.

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

Parameters1/5

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

Tool has no description.

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

Purpose1/5

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

Tool has no description.

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

Usage Guidelines1/5

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

Tool has no description.

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

study_sessionD

ParametersJSON Schema

Name	Required	Description
`operation`	Yes	Study session operation
`query`	No	Search query to find cards (for find_due)
`cardIds`	No	Card IDs to operate on
`answers`	No	Card answers (for answer operation)
`days`	No	Days from today for due date (for reschedule)

TDQS

D1/5.0

Behavior1/5

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

Tool has no description.

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

Conciseness1/5

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

Tool has no description.

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

Completeness1/5

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

Tool has no description.

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

Parameters1/5

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

Tool has no description.

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

Purpose1/5

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

Tool has no description.

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

Usage Guidelines1/5

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

Tool has no description.

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.

98 tool updatesv1.0.0Jan 3, 2026
- Removedadd_note
- Removedadd_notes
- Removedadd_tags_to_notes
- Addedanki_operations
- Removedanswer_cards
- Removedapi_reflect
- Removedcan_add_notes
- Removedcard_reviews
- Removedcards_to_notes
- Removedchange_deck
- Removedcheck_card_suspended
- Removedcheck_cards_due
- Removedcheck_cards_suspended
- Removedclear_unused_tags
- Removedclone_deck_config
- Removedcreate_deck
- Removedcreate_model
- Removeddelete_decks
- Removeddelete_media_file
- Removeddelete_notes
- Removedexport_package
- Removedfind_and_replace_in_models
- Removedfind_cards
- Removedfind_notes
- Removedforget_cards
- Removedget_active_profile
- Addedget_analytics
- Removedget_cards_ease_factors
- Removedget_cards_info
- Removedget_cards_intervals
- Removedget_cards_mod_time
- Removedget_collection_stats_html
- Removedget_latest_review_id
- Removedget_media_dir_path
- Addedget_media_file
- Removedget_media_files_names
- Removedget_num_cards_reviewed_by_day
- Removedget_num_cards_reviewed_today
- Removedget_profiles
- Removedget_reviews_of_cards
- Removedget_version
- Removedgui_add_cards
- Removedgui_answer_card
- Removedgui_browse
- Removedgui_check_database
- Removedgui_current_card
- Removedgui_deck_browser
- Removedgui_deck_overview
- Removedgui_deck_review
- Removedgui_edit_note
- Removedgui_exit_anki
- Removedgui_import_file
- Removedgui_select_card
- Removedgui_select_note
- Removedgui_selected_notes
- Removedgui_show_answer
- Removedgui_show_question
- Removedgui_start_card_timer
- Removedgui_undo
- Removedimport_package
- Removedinsert_reviews
- Removedload_profile
- Addedmanage_decks
- Addedmanage_flashcards
- Addedmanage_models
- Removedmodel_field_add
- Removedmodel_field_remove
- Removedmodel_field_rename
- Removedmodel_field_reposition
- Removedmodel_field_set_description
- Removedmodel_field_set_font
- Removedmodel_field_set_font_size
- Removedmodel_template_add
- Removedmodel_template_remove
- Removedmodel_template_rename
- Removedmodel_template_reposition
- Removedmulti
- Removedrelearn_cards
- Removedreload_collection
- Removedremove_deck_config
- Removedremove_empty_notes
- Removedremove_tags_from_notes
- Removedreplace_tags_in_notes
- Removedrequest_permission
- Removedretrieve_media_file
- Removedsave_deck_config
- Removedset_card_specific_values
- Removedset_cards_due_date
- Removedset_cards_ease_factors
- Removedset_deck_config
- Removedstore_media_file
- Addedstudy_session
- Removedsuspend_cards
- Removedsync
- Removedunsuspend_cards
- Removedupdate_model_styling
- Removedupdate_model_templates
- Removedupdate_note
91 tool updatesAug 15, 2025
- First observedadd_note
- First observedadd_notes
- First observedadd_tags_to_notes
- First observedanswer_cards
- First observedapi_reflect
- First observedcan_add_notes
- First observedcard_reviews
- First observedcards_to_notes
- First observedchange_deck
- First observedcheck_card_suspended
- First observedcheck_cards_due
- First observedcheck_cards_suspended
- First observedclear_unused_tags
- First observedclone_deck_config
- First observedcreate_deck
- First observedcreate_model
- First observeddelete_decks
- First observeddelete_media_file
- First observeddelete_notes
- First observedexport_package
- First observedfind_and_replace_in_models
- First observedfind_cards
- First observedfind_notes
- First observedforget_cards
- First observedget_active_profile
- First observedget_cards_ease_factors
- First observedget_cards_info
- First observedget_cards_intervals
- First observedget_cards_mod_time
- First observedget_collection_stats_html
- First observedget_latest_review_id
- First observedget_media_dir_path
- First observedget_media_files_names
- First observedget_num_cards_reviewed_by_day
- First observedget_num_cards_reviewed_today
- First observedget_profiles
- First observedget_reviews_of_cards
- First observedget_version
- First observedgui_add_cards
- First observedgui_answer_card
- First observedgui_browse
- First observedgui_check_database
- First observedgui_current_card
- First observedgui_deck_browser
- First observedgui_deck_overview
- First observedgui_deck_review
- First observedgui_edit_note
- First observedgui_exit_anki
- First observedgui_import_file
- First observedgui_select_card
- First observedgui_select_note
- First observedgui_selected_notes
- First observedgui_show_answer
- First observedgui_show_question
- First observedgui_start_card_timer
- First observedgui_undo
- First observedimport_package
- First observedinsert_reviews
- First observedload_profile
- First observedmodel_field_add
- First observedmodel_field_remove
- First observedmodel_field_rename
- First observedmodel_field_reposition
- First observedmodel_field_set_description
- First observedmodel_field_set_font
- First observedmodel_field_set_font_size
- First observedmodel_template_add
- First observedmodel_template_remove
- First observedmodel_template_rename
- First observedmodel_template_reposition
- First observedmulti
- First observedrelearn_cards
- First observedreload_collection
- First observedremove_deck_config
- First observedremove_empty_notes
- First observedremove_tags_from_notes
- First observedreplace_tags_in_notes
- First observedrequest_permission
- First observedretrieve_media_file
- First observedsave_deck_config
- First observedset_card_specific_values
- First observedset_cards_due_date
- First observedset_cards_ease_factors
- First observedset_deck_config
- First observedstore_media_file
- First observedsuspend_cards
- First observedsync
- First observedunsuspend_cards
- First observedupdate_model_styling
- First observedupdate_model_templates
- First observedupdate_note

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

D1.8/5.0

Scored 2026-04-18 10:00 across 7 tools

Disambiguation4/5

The tools have distinct purposes targeting different aspects of Anki functionality: operations, analytics, media, decks, flashcards, models, and study sessions. There is some potential overlap between 'anki_operations' and the more specific 'manage_' tools, but the separation is generally clear enough for an agent to distinguish them based on their names.

Naming Consistency3/5

The naming is mixed: 'anki_operations', 'get_analytics', and 'get_media_file' follow a verb_noun pattern, while 'manage_decks', 'manage_flashcards', and 'manage_models' use a verb_noun pattern with a consistent 'manage_' prefix, and 'study_session' is a noun_noun pattern. This inconsistency in conventions reduces predictability but remains readable.

Tool Count5/5

With 7 tools, the count is well-scoped for an Anki server, covering core areas like decks, flashcards, models, study sessions, analytics, media, and general operations. Each tool appears to earn its place without being excessive or insufficient for the domain.

Completeness3/5

The tool set covers key areas of Anki (decks, flashcards, models, study, analytics, media, operations), but without descriptions, it's unclear if there are gaps in CRUD/lifecycle coverage. For example, 'manage_flashcards' might imply create/update/delete, but specific tools for individual operations are missing, potentially leading to agent workarounds.

Maintenance

ActivityInactive

ResponsivenessNo issues

Resources

Need Help?

Related Servers

Related MCP Connectors

Flash AOAuth
com.flashmemorize
Spaced-repetition flashcards your AI writes, quizzes you on by voice, and schedules with FSRS.
Education & Learning Tools Speech Processing
2412
Flashcards Open Source AppOAuth
com.flashcards-open-source-app
Read, write, and conversationally review open-source flashcards through split read/write MCP tools.
Education & Learning Tools Note Taking
229
Acornonaut MCP ServerOAuth
io.github.zerolve-io
AI-powered YouTube to flashcards with spaced repetition and Anki export
Education & Learning Tools AI & Machine Learning
2
Quizlar — voice-powered AI flashcards with spaced repetitionOAuth
io.github.quizlar
Voice-led, FSRS-scheduled flashcards from YouTube, PDFs, web, or text. Auto-graded quizzes.
Education & Learning Tools Speech Processing Knowledge & Memory
2

Related MCP Servers

Clanki
Education & Learning Tools App Automation
jasperket
A
license
A
quality
B
maintenance
An MCP server that enables AI assistants like Claude to interact with Anki flashcard decks, allowing users to create, manage, and update flashcards through natural language conversations.
Updated 20 days ago (2026-09-17 01:38 UTC)
9
44
MIT
Anki MCP Server
Education & Learning Tools Note Taking
ankimcp
A
license
Not graded
quality
A
maintenance
An MCP server that enables AI assistants to interact with the Anki flashcard application for studying, deck management, and note creation. It supports natural language interaction for reviewing cards, searching content, and managing media files across local and remote environments.
Updated 19 days ago (2026-09-18 15:17 UTC)
1,773 npm
502
MIT
TalkToAnki
Education & Learning Tools Note Taking App Automation
muxuuu
A
license
Not graded
quality
D
maintenance
An MCP server that enables AI assistants to seamlessly manage Anki flashcards, decks, and templates through the AnkiConnect API. It supports intelligent querying, batch note creation, and detailed study progress analysis using natural language.
Updated a year ago (2025-06-22 09:57 UTC)
4
MIT
Anki MCP Server
Education & Learning Tools Knowledge & Memory
matteo1222
A
license
B
quality
D
maintenance
A Model Context Protocol (MCP) server that integrates with Anki flashcard application, allowing LLM applications like Claude to interact with your Anki decks and cards.
Updated a year ago (2025-08-01 03:17 UTC)
11
334 npm
1
MIT