Skip to main content
Glama

Related Servers

Alternatives to LeetCode MCP Server

No user-submitted related servers found.

    Related Servers

    TDQS

    A4.1/5.0

    Scored across 12 tools

    Disambiguation4/5

    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.

    Naming Consistency5/5

    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.

    Tool Count5/5

    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.

    Completeness4/5

    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.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues