Skip to main content
Glama
lkastar

LeetCode CN MCP

by lkastar
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to LeetCode CN MCP

No user-submitted related servers found.

    Related Servers

    • LeetCode MCP Server

      shubhamgupta2702
      A
      license
      A
      quality
      C
      maintenance
      Enables 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.
      9
      129 npm
      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.
      30 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.
      6 npm
      MIT

    • LeetCode MCP Server

      jinzcdev
      A
      license
      A
      quality
      B
      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
      129 npm
      152
      MIT
    Deploy Server
    Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

    TDQS

    A3.9/5.0

    Scored across 5 tools

    Disambiguation5/5

    Each tool has a clear, non-overlapping responsibility: authentication lifecycle (login, logout, auth_status), problem lookup (get_problem), and submission history retrieval (get_submissions_by_date). There is no realistic ambiguity between tool purposes.

    Naming Consistency4/5

    Most tools follow a readable snake_case pattern with clear verbs and nouns, such as get_problem and get_submissions_by_date. login/logout and auth_status are minor deviations but remain conventional and predictable.

    Tool Count5/5

    Five tools is well-scoped for a focused LeetCode CN server handling authentication, problem data, and submission history. Each tool earns its place with no redundancy or bloat.

    Completeness4/5

    Authentication status/login/logout form a complete lifecycle, and problem fetching plus daily submission retrieval cover the core read-only workflows. Minor gaps such as broader problem search or submission detail endpoints are workable but not critical.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources