MCP Server Learning
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ZOTERO_API_KEY | No | Your Zotero Web API key (get from zotero.org/settings/keys) | |
| ZOTERO_LIBRARY_ID | No | Your Zotero library ID (user ID for personal library or group ID for group library) | |
| OBSIDIAN_VAULT_PATH | No | Full path to your Obsidian vault directory (the folder containing your .md files and .obsidian folder) | |
| ZOTERO_LIBRARY_TYPE | No | Either 'user' for personal library or 'group' for group library |
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
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| create_flashcardsA | Convert text into flashcards with LaTeX math rendering for Claude Desktop Args: content: Text content to convert to flashcards. Use Q: A: format or separate lines. card_type: Type of flashcard - "front-back" or "cloze" Examples: Basic card: Q: What is the sigmoid function? A: $\sigma(x) = \frac{1}{1 + e^{-x}}$ |
| upload_to_ankiA | Upload generated flashcards directly to Anki with proper MathJax conversion Args: content: Text content to convert and upload to Anki (LaTeX will be converted to MathJax format) deck_name: Name of the Anki deck to upload to card_type: Type of flashcard - "front-back" or "cloze" tags: Tags to add to the cards anki_api_key: Optional AnkiConnect API key |
| check_anki_connectionC | Check connection to Anki and get available decks/models Args: anki_api_key: Optional AnkiConnect API key |
| preview_cardsB | Generate text preview of flashcards with LaTeX rendering for Claude Desktop Args: content: Text content to convert to flashcards and preview card_type: Type of flashcard - "front-back" or "cloze" title: Title for the preview document tags: Tags to display on the cards (currently not shown in text format) |
| search_anki_notesC | Search for notes in Anki collection Args: query: Search query (e.g., 'deck:Math', 'tag:chemistry', 'Python programming') limit: Maximum number of notes to return anki_api_key: Optional AnkiConnect API key |
| update_anki_noteB | Update an existing Anki note Args: note_id: ID of the note to update fields: Fields to update (field_name: new_value) tags: New tags for the note (optional) anki_api_key: Optional AnkiConnect API key |
| delete_anki_notesC | Delete notes from Anki collection Args: note_ids: List of note IDs to delete anki_api_key: Optional AnkiConnect API key |
| sync_ankiC | Synchronize Anki collection with AnkiWeb Args: anki_api_key: Optional AnkiConnect API key |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 8 tools
Each tool has a clearly distinct purpose with no ambiguity. Tools like check_anki_connection, create_flashcards, delete_anki_notes, search_anki_notes, sync_anki, update_anki_note, upload_to_anki, and preview_cards all target specific, non-overlapping operations in the Anki flashcard management workflow.
All tools follow a consistent verb_noun pattern with snake_case naming. Examples include check_anki_connection, create_flashcards, delete_anki_notes, search_anki_notes, sync_anki, update_anki_note, upload_to_anki, and preview_cards, showing perfect consistency throughout.
With 8 tools, this server is well-scoped for managing Anki flashcards. Each tool serves a clear purpose in the workflow, from connection checking and flashcard creation to search, update, deletion, syncing, and previewing, making the count appropriate and efficient.
The tool set provides complete CRUD/lifecycle coverage for Anki flashcard management. It includes creation (create_flashcards, upload_to_anki), reading/searching (search_anki_notes, preview_cards), updating (update_anki_note), deletion (delete_anki_notes), and auxiliary operations (check_anki_connection, sync_anki), with no obvious gaps.