Skip to main content
Glama
shubhamgupta2702

LeetCode MCP Server

by shubhamgupta2702
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to LeetCode MCP Server

No user-submitted related servers found.

    Related Servers

    • LeetCode CN MCP

      lkastar
      A
      license
      A
      quality
      C
      maintenance
      Enables secure, read-only access to LeetCode CN for fetching problem details by title, slug, number, or URL, and retrieving user submission records for a given date with optional filtering.
      5
      MIT

    • LeetCode MCP

      pipeworx-io
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to look up LeetCode public profiles, solved-problem counts by difficulty, recent accepted submissions, the daily coding challenge, and individual problem details by title slug through LeetCode's keyless GraphQL endpoint. Runs either as a local stdio server or via a hosted gateway URL, with no account required for initial calls.
      188 npm
      MIT

    • PersonalLeetcodeMCP

      RishiSarraff
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables Claude to fetch and analyze your public LeetCode submission history, weak areas, and daily challenge via a remote MCP server.
      9 npm
      MIT

    • LeetCode MCP Server

      jinzcdev
      A
      license
      A
      quality
      A
      maintenance
      A Model Context Protocol server that provides integration with LeetCode APIs, enabling automated interaction with programming problems, contests, solutions, and user data across both leetcode.com and leetcode.cn platforms.
      9
      196 npm
      151
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A4.4/5.0

    Scored across 9 tools

    Disambiguation4/5

    Most tools have clearly distinct purposes (e.g., get_problem vs search_problems vs get_daily_challenge). Slight overlap exists between get_recent_submissions and get_recent_ac_submissions, and between get_user_profile and get_user_contest_ranking, but descriptions help differentiate them.

    Naming Consistency5/5

    All tools follow a consistent snake_case verb_noun pattern (get_daily_challenge, get_problem, search_problems, etc.). Minor variation between get_ and list_ verbs is natural and still predictable.

    Tool Count5/5

    9 tools is well-scoped for a read-only LeetCode data access server. Each tool covers a distinct aspect (problems, users, submissions, solutions) without redundancy.

    Completeness3/5

    The set covers core read-only operations, but several tools referenced in descriptions are absent (get_user_status, get_all_submissions), leaving gaps for authenticated full submission history and session verification. These missing operations could cause agent failures when those capabilities are expected.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources