vocabit-mcp
Related Servers
Alternatives to vocabit-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceConnects AI assistants like Claude to MindDory to automatically capture new vocabulary and grammar mistakes into spaced-repetition flashcards during language practice conversations.MIT
- FlicenseNot gradedqualityBmaintenanceEnables AI assistants to search the Inoh dictionary and create, update, or delete vocabulary flashcards in the user's Inoh account through natural language.-

EduBase MCP Serverofficial
AlicenseCqualityAmaintenanceEnables AI assistants to interact with the EduBase educational platform to create quizzes, upload questions, schedule exams, manage educational content, and analyze user results through natural language.200322 npm28MIT- FlicenseNot gradedqualityDmaintenanceA bridge that provides AI assistants with access to WaniKani user data and functionality, enabling them to retrieve learning progress, identify difficult items, and offer personalized Japanese language learning assistance.2-
- AlicenseNot gradedqualityBmaintenanceBridge between AI assistants and Anki Desktop, enabling automated flashcard management and study document processing.86 npmMIT

Unfold It MCP Serverofficial
AlicenseAqualityDmaintenanceConnect AI assistants to Unfold It -- create goals with AI-generated plans, agent-assisted clarification, plan import with enrichment, individual progress tracking, cohort analytics, and skill assessments.1326 npm2MIT
TDQS
Scored across 8 tools
Each tool has a clearly distinct purpose: health check, CRUD for study sets, results feedback, and learner notification. Even get_study_set and get_set_results are unambiguously separated—one retrieves content, the other study metrics. No two tools appear to do the same thing.
Most tools follow a verb_noun pattern (create_study_set, list_study_sets, update_study_set, delete_study_set, get_study_set, get_set_results). However, vocabit_health deviates from the verb-first style and notify_learner uses a non-set object, so the pattern is not perfectly uniform but remains predictable.
8 tools is well within the ideal 3-15 range and each earns its place in the set lifecycle. The count matches the server's scope—managing study sets with health check and notification—without redundancy or unnecessary bulk.
The tool surface covers the full lifecycle: create, read, update, delete, list, plus results feedback and learner notification. The feedback loop is closed by get_set_results informing update_study_set. Health check aids debugging. No obvious gaps that would cause agent failures.