LeetCode Tracker MCP
Related Servers
Alternatives to LeetCode Tracker MCP
No user-submitted related servers found.
Related Servers
- AlicenseBqualityBmaintenanceEnables users to combine LeetCode and Codeforces practice history, get recommended next problems, journal recurring mistakes, and revise solved problems on a spaced-repetition schedule through MCP clients.16MIT
- AlicenseNot gradedqualityDmaintenanceEnables Claude to fetch and analyze your public LeetCode submission history, weak areas, and daily challenge via a remote MCP server.12 npmMIT
- AlicenseAqualityCmaintenanceEnables integration with LeetCode APIs to retrieve problems, contests, solutions, and user data, support daily challenges and advanced searches, and perform authenticated actions such as running or submitting code and managing notes.9MIT
- AlicenseNot gradedqualityAmaintenanceEnables automated access to LeetCode's problems, contests, solutions, and public or authenticated user data across leetcode.com and leetcode.cn, with search, daily challenge, submission, notes, and progress tools.MIT
- FlicenseNot gradedqualityCmaintenanceEnables analyzing Codeforces activity through local MCP tools, including weekly practice summaries, problem recommendations, user comparisons, weak-topic detection, contest tracking, and rating progress.-
- AlicenseNot gradedqualityAmaintenanceEnables automated access to LeetCode problems, solutions, contests, and public or authenticated user data across leetcode.com and leetcode.cn, supporting search, submissions, notes, and daily challenges.MIT
TDQS
Scored across 9 tools
Each tool has a distinct action-resource focus: listing tracked problems, listing due reviews, single-problem history, aggregate progress, topic analysis, syncing, logging, goal setting, and the daily challenge. The only mild overlap is between get_due_reviews and get_progress, which also reports due reviews, and between list_tracked_problems and get_problem_history, but the singular/plural and 'history' distinction makes boundaries clear enough.
Every tool follows a clean verb_noun snake_case pattern (list_*, get_*, log_*, sync_*, set_*, analyze_*). No camelCase or vague single-word verbs; the pattern is fully predictable.
Nine tools is well within the ideal 3-15 range and every tool maps to a real workflow: tracking, spaced repetition, syncing, stats, goals, and daily challenge. Nothing appears redundant or padded.
Core lifecycle is covered—sync submissions, log attempts, schedule reviews, view history, analyze topics, set goals, and fetch the daily challenge. Minor gaps exist: no way to edit or delete a logged attempt, and no explicit tool to selectively untrack or add a problem outside sync/log_attempt.