Daily Tutor MCP
Related Servers
Alternatives to Daily Tutor MCP
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceImplements cognitive science-backed interleaved learning techniques to create study plans, generate mixed-topic quizzes, manage flashcard decks, and track learning progress for optimal knowledge retention.1MIT
- AlicenseBqualityBmaintenanceEnables AI agents to act as a state-driven tutoring engine over MCP, with server-side mastery estimation, prerequisite checks, evidence-based assessment, and FSRS spaced review scheduling.581MIT

atomicrepsofficial
AlicenseCqualityBmaintenanceEnables coding agents to deliver short retrieval-practice questions about what was just built, with tools for answering, viewing progress, and managing pacing, topics, mutes, and difficulty.463 npmMIT- FlicenseNot gradedqualityCmaintenanceEnables users to generate quizzes in various formats, flashcards from topics or personal notes, structured study courses, explanatory diagrams, and short study-break games through any MCP client. It turns spare moments into active learning by letting clients quiz, drill, and organize study material on virtually any subject.-
- AlicenseNot gradedqualityCmaintenanceEnables users to create, review, and manage flashcards using the SM-2 spaced repetition algorithm for optimized learning. It supports organizing cards into projects and automatically handles review scheduling based on user performance.2MIT
- AlicenseBqualityDmaintenanceAn MCP server for tracking student learning via a knowledge graph, with spaced repetition scheduling and intelligent queries to identify gaps, misconceptions, and optimal next steps.721 PyPI2MIT
TDQS
Scored across 26 tools
Most tools map to a clearly distinct step in a well-signposted workflow (SETUP, ASK step 1/2, EVALUATE step 1/2), and descriptions explicitly say when to use which. The main friction points are the config cluster (set_preferences vs. set_topic vs. set_settings) and the analytics cluster (get_progress vs. get_coverage vs. weekly_recap), where boundaries are clear only after reading the detailed descriptions.
Predominantly a consistent snake_case verb_noun pattern (set_topic, get_session, save_question, check_answer, remove_material). A few deviations exist, notably use_hint and weekly_recap which lack a clarifying verb, and the very long get_next_question_brief, but nothing is ambiguous or chaotically mixed.
26 tools is on the heavy side; while the domain (setup, materials, sessions, question authoring, grading, spaced repetition, analytics) legitimately spans many stages, several tools are fine-grained splits that could be consolidated. The check_answer/record_result and get_next_question_brief/save_question pairs in particular feel like protocol steps rather than standalone capabilities.
The lifecycle is well covered: onboarding, topic/track management, material ingestion, session flow, question generation, grading, spaced repetition, mistakes review, and analytics. Minor gaps exist, such as no way to abandon/reset a session or edit a previously saved question, but agents can work around these.