Provides tools for accessing LeetCode problems, user data, search capabilities, and submission tracking across both leetcode.com and leetcode.cn platforms. Enables retrieval of detailed problem descriptions, user profiles, submission history, and contest performance statistics.
The LeetCode MCP Server is a Model Context Protocol (MCP) server that provides seamless integration with LeetCode APIs, enabling advanced automation and intelligent interaction with LeetCode's programming problems, contests, solutions, and user data.
To install leetcode-mcp-server for Claude Desktop automatically via Smithery:
Alternatively, you can clone the repository and run it locally:
Add the following JSON configuration to your User Settings (JSON) file. Access this by pressing Ctrl/Cmd + Shift + P and searching for Preferences: Open User Settings (JSON).
For LeetCode China site, modify the --site parameter to cn.
Tip
The server supports the following environment variables:
LEETCODE_SITE: LeetCode API endpoint ('global' or 'cn')LEETCODE_SESSION: LeetCode session cookie for authenticated API accessPriority Note: Command-line arguments take precedence over environment variables when both are specified. For example:
LEETCODE_SITE=cn is set but you run leetcode-mcp-server --site global, the server will use global.LEETCODE_SESSION exists but you provide --session "new_cookie", the command-line session value will be used.| Tool | Global | CN | Auth Required | Description |
|---|---|---|---|---|
| get_daily_challenge | ✅ | ✅ | ❌ | Retrieves today's LeetCode Daily Challenge problem |
| get_problem | ✅ | ✅ | ❌ | Retrieves details for a specific LeetCode problem |
| search_problems | ✅ | ✅ | ❌ | Searches for LeetCode problems with multiple filter criteria |
| Tool | Global | CN | Auth Required | Description |
|---|---|---|---|---|
| get_user_profile | ✅ | ✅ | ❌ | Retrieves profile information for a LeetCode user |
| get_user_contest_ranking | ✅ | ✅ | ❌ | Obtains contest ranking statistics for a user |
| get_recent_ac_submissions | ✅ | ✅ | ❌ | Retrieves a user's recent accepted submissions |
| get_recent_submissions | ✅ | ❌ | ❌ | Retrieves a user's recent submissions history |
| get_user_status | ✅ | ✅ | ✅ | Retrieves current user's current status |
| get_problem_submission_report | ✅ | ✅ | ✅ | Provides detailed submission analysis for a specific problem |
| get_problem_progress | ✅ | ✅ | ✅ | Retrieves current user's problem-solving progress |
| get_all_submissions | ✅ | ✅ | ✅ | Retrieves current user's submission history |
| Tool | Global | CN | Auth Required | Description |
|---|---|---|---|---|
| search_notes | ❌ | ✅ | ✅ | Searches for user notes with filtering options |
| get_note | ❌ | ✅ | ✅ | Retrieves notes for a specific problem by question ID |
| create_note | ❌ | ✅ | ✅ | Creates a new note for a specific problem |
| update_note | ❌ | ✅ | ✅ | Updates an existing note with new content |
| Tool | Global | CN | Auth Required | Description |
|---|---|---|---|---|
| list_problem_solutions | ✅ | ✅ | ❌ | Retrieves a list of community solutions for a specific problem |
| get_problem_solution | ✅ | ✅ | ❌ | Retrieves the complete content of a specific solution |
titleSlug: The URL slug/identifier of the problem (string, required)category: Problem category filter (string, optional, default: "all-code-essentials")tags: List of topic tags to filter problems by (string[], optional)difficulty: Problem difficulty level filter (enum: "EASY", "MEDIUM", "HARD", optional)searchKeywords: Keywords to search in problem titles and descriptions (string, optional)limit: Maximum number of problems to return (number, optional, default: 10)offset: Number of problems to skip (number, optional)username: LeetCode username (string, required)username: LeetCode username (string, required)attended: Whether to include only the contests the user has participated in (boolean, optional, default: true)username: LeetCode username (string, required)limit: Maximum number of submissions to return (number, optional, default: 10)username: LeetCode username (string, required)limit: Maximum number of submissions to return (number, optional, default: 10)id: The numerical submission ID (number, required)offset: Number of questions to skip (number, optional, default: 0)limit: Maximum number of questions to return (number, optional, default: 100)questionStatus: Filter by question status (enum: "ATTEMPTED", "SOLVED", optional)difficulty: Filter by difficulty levels (string[], optional)limit: Maximum number of submissions to return (number, default: 20)offset: Number of submissions to skip (number, default: 0)questionSlug: Optional problem identifier (string, optional)lang: Programming language filter (string, optional, CN only)status: Submission status filter (enum: "AC", "WA", optional, CN only)lastKey: Pagination token for retrieving next page (string, optional, CN only)keyword: Search term to filter notes (string, optional)limit: Maximum number of notes to return (number, optional, default: 10)skip: Number of notes to skip (number, optional, default: 0)orderBy: Sort order for returned notes (enum: "ASCENDING", "DESCENDING", optional, default: "DESCENDING")questionId: The question ID of the LeetCode problem (string, required)limit: Maximum number of notes to return (number, optional, default: 10)skip: Number of notes to skip (number, optional, default: 0)questionId: The question ID of the LeetCode problem (string, required)content: The content of the note, supports markdown format (string, required)summary: An optional short summary or title for the note (string, optional)noteId: The ID of the note to update (string, required)content: The new content for the note, supports markdown format (string, required)summary: An optional new short summary or title for the note (string, optional)questionSlug: The URL slug/identifier of the problem (string, required)limit: Maximum number of solutions to return (number, optional, default: 10)skip: Number of solutions to skip (number, optional)userInput: Search term to filter solutions (string, optional)tagSlugs: Array of tag identifiers to filter solutions (string[], optional, default: [])orderBy: Sorting criteria for the returned solutionstopicId: Unique topic ID of the solution (string, required, Global only)slug: Unique slug/identifier of the solution (string, required, CN only)| Resource Name | Global | CN | Auth Required | Description |
|---|---|---|---|---|
| problem-categories | ✅ | ✅ | ❌ | A list of all problem classification categories |
| problem-tags | ✅ | ✅ | ❌ | A detailed collection of algorithmic and data structure tags |
| problem-langs | ✅ | ✅ | ❌ | A complete list of all supported programming languages |
| problem-detail | ✅ | ✅ | ❌ | Provides details about a specific problem |
| problem-solution | ✅ | ✅ | ❌ | Provides the complete content of a specific solution |
categories://problems/alltags://problems/alllangs://problems/allproblem://{titleSlug}titleSlug: Problem identifier as it appears in the LeetCode URLsolution://{topicId}topicId: Unique topic ID of the solutionsolution://{slug}slug: Unique slug/identifier of the solutionUser-specific data access requires LeetCode session authentication:
LEETCODE_SESSION cookie from browser developer tools--session flag or LEETCODE_SESSION environment variableAll tools return JSON-formatted responses with the following structure:
The JSON_DATA_STRING contains either the requested data or an error message for failed requests.
This project is licensed under the MIT License.
You must be authenticated.
remote-capable server
The server can be hosted and run remotely because it primarily relies on remote services or has no dependency on the local environment.
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.