LeetCode MCP Server
Related Servers
Alternatives to LeetCode MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityAmaintenanceEnables automated access to LeetCode problems, solutions, contests, and user data, with optional authentication for private features. Supports both leetcode.com and leetcode.cn via stdio or Streamable HTTP transports.MIT
- FlicenseNot gradedqualityAmaintenanceEnables automated access to LeetCode problems, contest data, solutions, user profiles, submissions, notes, and progress, with optional authentication for private user-specific features. Supports both leetcode.com (Global) and leetcode.cn (China) sites with stdio and Streamable HTTP transports.-
- AlicenseNot gradedqualityAmaintenanceEnables automated access to LeetCode problems, solutions, contests, and public data across leetcode.com and leetcode.cn, with optional authentication for user-specific features like submissions, notes, and progress.MIT
- AlicenseNot gradedqualityAmaintenanceEnables automated access to LeetCode problems, solutions, contests, and user data, with optional authentication for private features across leetcode.com and leetcode.cn.MIT
- AlicenseNot gradedqualityAmaintenanceEnables automated access to LeetCode problems, solutions, contests, and user data, with optional authentication for private features and support for both leetcode.com and leetcode.cn.MIT
- AlicenseNot gradedqualityAmaintenanceEnables automated access to LeetCode problems, solutions, contests, and user data across leetcode.com and leetcode.cn, with optional authentication for private features such as notes, problem lists, progress tracking, and submission analysis.MIT
TDQS
Scored across 12 tools
Most tools target a distinct resource+mode (problem fetch, search, random, daily challenge, solutions list vs. read, contest schedule vs. ranking, profile, submissions), and descriptions actively cross-reference siblings to steer selection. The only soft overlaps are get_recent_submissions vs. get_recent_ac_submissions and get_problem vs. get_random_problem/get_daily_challenge, but the descriptions spell out the boundaries. Minor deduction because descriptions reference tools not present in the set (get_user_status, get_all_submissions), which can muddy an agent's mental model.
All 12 names are snake_case with a predictable verb_noun pattern using a small verb vocabulary (get_, list_, search_). Variants are distinguished by clear, consistent suffixes (get_recent_submissions vs. get_recent_ac_submissions). No mixed conventions anywhere.
Twelve tools sit squarely in the well-scoped range, and each covers a discrete capability (problem retrieval, discovery, solutions, code snippets, contests, user stats, submissions). Nothing appears redundant enough to remove, and the surface is not bloated.
The read-only surface covers the core LeetCode workflows well: problem discovery/retrieval, solutions, starter code, contests, profiles, and submission history. Gaps are mostly ones the descriptions themselves advertise but do not deliver (get_user_status, paginated get_all_submissions with filters), plus no official editorial or CN-specific variants. These are workable but leave dead references in the descriptions.