LeetCode MCP Server

1# LeetCode MCP Server
2 
3[![NPM Version](https://img.shields.io/npm/v/@jinzcdev/leetcode-mcp-server.svg)](https://www.npmjs.com/package/@jinzcdev/leetcode-mcp-server)
4[![GitHub License](https://img.shields.io/github/license/jinzcdev/leetcode-mcp-server.svg)](https://img.shields.io/github/license/jinzcdev/leetcode-mcp-server.svg)
5[![smithery badge](https://smithery.ai/badge/@jinzcdev/leetcode-mcp-server)](https://smithery.ai/server/@jinzcdev/leetcode-mcp-server)
6[![Chinese Doc](https://img.shields.io/badge/简体中文-点击查看-orange)](README_zh-CN.md)
7[![Stars](https://img.shields.io/github/stars/jinzcdev/leetcode-mcp-server)](https://github.com/jinzcdev/leetcode-mcp-server)
8 
9The LeetCode MCP Server is a [Model Context Protocol (MCP)](https://modelcontextprotocol.io/introduction) server that provides seamless integration with LeetCode APIs, enabling advanced automation and intelligent interaction with LeetCode's programming problems, contests, solutions, and user data.
10 
11<a href="https://glama.ai/mcp/servers/@jinzcdev/leetcode-mcp-server">
12  <img width="380" height="200" src="https://glama.ai/mcp/servers/@jinzcdev/leetcode-mcp-server/badge" alt="LeetCode Server MCP server" />
13</a>
14 
15## Features
16 
17- 🌐 **Multi-site Support**: Support​ both leetcode.com (Global) and leetcode.cn (China) platforms
18- 📊 **Problem Data Retrieval**: Obtain detailed problem descriptions, constraints, examples, official editorials, and ​user-submitted solutions
19- 👤 **User Data Access**: Retrieve user profiles, submission history, and contest performance
20- 🔒 **​Private Data Access**: Create and query user notes, track problem-solving progress, and analyze submission details (AC/WA analysis)
21- 🔍 **Advanced Search Capabilities**: Filter problems by tags, difficulty levels, categories, and keywords
22- 📅 **Daily Challenge Access**: Easily access daily challenge problems
23 
24## Prerequisites
25 
261. Node.js (v20.x or above)
272. (Optional) LeetCode session cookie for authenticated API access
28 
29## Installation
30 
31### Installing via Smithery
32 
33To install leetcode-mcp-server for Claude Desktop automatically via [Smithery](https://smithery.ai/server/@jinzcdev/leetcode-mcp-server):
34 
35```bash
36npx -y @smithery/cli install @jinzcdev/leetcode-mcp-server --client claude
37```
38 
39### Manual Installation
40 
41```bash
42# Install from npm
43npm install @jinzcdev/leetcode-mcp-server -g
44 
45# Or run with Global site configuration
46npx -y @jinzcdev/leetcode-mcp-server --site global
47 
48# Run with authentication (for accessing private data)
49npx -y @jinzcdev/leetcode-mcp-server --site global --session <YOUR_LEETCODE_SESSION_COOKIE>
50```
51 
52Alternatively, you can clone the repository and run it locally:
53 
54```bash
55# Clone the repository
56git clone https://github.com/jinzcdev/leetcode-mcp-server.git
57 
58# Navigate to the project directory
59cd leetcode-mcp-server
60 
61# Build the project
62npm install && npm run build
63 
64# Run the server
65node build/index.js --site global
66```
67 
68## Usage
69 
70### Visual Studio Code Integration
71 
72Add 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)`.
73 
74#### Option 1: Using Environment Variables
75 
76```json
77{
78  "mcp": {
79    "servers": {
80      "leetcode": {
81        "type": "stdio",
82        "command": "npx",
83        "args": ["-y", "@jinzcdev/leetcode-mcp-server"],
84        "env": {
85          "LEETCODE_SITE": "global",
86          "LEETCODE_SESSION": "<YOUR_LEETCODE_SESSION_COOKIE>"
87        }
88      }
89    }
90  }
91}
92```
93 
94#### Option 2: Using Command Line Arguments
95 
96```json
97{
98  "mcp": {
99    "servers": {
100      "leetcode": {
101        "type": "stdio",
102        "command": "npx",
103        "args": [
104          "-y",
105          "@jinzcdev/leetcode-mcp-server",
106          "--site",
107          "global",
108          "--session",
109          "<YOUR_LEETCODE_SESSION_COOKIE>"
110        ]
111      }
112    }
113  }
114}
115```
116 
117For LeetCode China site, modify the `--site` parameter to `cn`.
118 
119> [!TIP]
120>
121> The server supports the following optional environment variables:
122>
123> - `LEETCODE_SITE`: LeetCode API endpoint ('global' or 'cn', default: 'global')
124> - `LEETCODE_SESSION`: LeetCode session cookie for authenticated API access (default: empty)
125>
126> **Priority Note**:
127> Command-line arguments take precedence over environment variables when both are specified. For example:
128>
129> - If `LEETCODE_SITE=cn` is set but you run `leetcode-mcp-server --site global`, the server will use `global`.
130> - If `LEETCODE_SESSION` exists but you provide `--session "new_cookie"`, the command-line session value will be used.
131 
132## Available Tools
133 
134### Problems
135 
136| Tool                    | Global | CN  | Auth Required | Description                                                  |
137| ----------------------- | :----: | :-: | :-----------: | ------------------------------------------------------------ |
138| **get_daily_challenge** |   ✅   | ✅  |      ❌       | Retrieves today's LeetCode Daily Challenge problem           |
139| **get_problem**         |   ✅   | ✅  |      ❌       | Retrieves details for a specific LeetCode problem            |
140| **search_problems**     |   ✅   | ✅  |      ❌       | Searches for LeetCode problems with multiple filter criteria |
141 
142### Users
143 
144| Tool                              | Global | CN  | Auth Required | Description                                                  |
145| --------------------------------- | :----: | :-: | :-----------: | ------------------------------------------------------------ |
146| **get_user_profile**              |   ✅   | ✅  |      ❌       | Retrieves profile information for a LeetCode user            |
147| **get_user_contest_ranking**      |   ✅   | ✅  |      ❌       | Obtains contest ranking statistics for a user                |
148| **get_recent_ac_submissions**     |   ✅   | ✅  |      ❌       | Retrieves a user's recent accepted submissions               |
149| **get_recent_submissions**        |   ✅   | ❌  |      ❌       | Retrieves a user's recent submissions history                |
150| **get_user_status**               |   ✅   | ✅  |      ✅       | Retrieves current user's current status                      |
151| **get_problem_submission_report** |   ✅   | ✅  |      ✅       | Provides detailed submission analysis for a specific problem |
152| **get_problem_progress**          |   ✅   | ✅  |      ✅       | Retrieves current user's problem-solving progress            |
153| **get_all_submissions**           |   ✅   | ✅  |      ✅       | Retrieves current user's submission history                  |
154 
155### Notes
156 
157| Tool             | Global | CN  | Auth Required | Description                                           |
158| ---------------- | :----: | :-: | :-----------: | ----------------------------------------------------- |
159| **search_notes** |   ❌   | ✅  |      ✅       | Searches for user notes with filtering options        |
160| **get_note**     |   ❌   | ✅  |      ✅       | Retrieves notes for a specific problem by question ID |
161| **create_note**  |   ❌   | ✅  |      ✅       | Creates a new note for a specific problem             |
162| **update_note**  |   ❌   | ✅  |      ✅       | Updates an existing note with new content             |
163 
164### Solutions
165 
166| Tool                       | Global | CN  | Auth Required | Description                                                    |
167| -------------------------- | :----: | :-: | :-----------: | -------------------------------------------------------------- |
168| **list_problem_solutions** |   ✅   | ✅  |      ❌       | Retrieves a list of community solutions for a specific problem |
169| **get_problem_solution**   |   ✅   | ✅  |      ❌       | Retrieves the complete content of a specific solution          |
170 
171## Tool Parameters
172 
173### Problems
174 
175- **get_daily_challenge** - Retrieves today's LeetCode Daily Challenge problem with complete details
176 
177  - No parameters required
178 
179- **get_problem** - Retrieves details about a specific LeetCode problem
180 
181  - `titleSlug`: The URL slug/identifier of the problem (string, required)
182 
183- **search_problems** - Searches for LeetCode problems based on multiple filter criteria
184  - `category`: Problem category filter (string, optional, default: "all-code-essentials")
185  - `tags`: List of topic tags to filter problems by (string[], optional)
186  - `difficulty`: Problem difficulty level filter (enum: "EASY", "MEDIUM", "HARD", optional)
187  - `searchKeywords`: Keywords to search in problem titles and descriptions (string, optional)
188  - `limit`: Maximum number of problems to return (number, optional, default: 10)
189  - `offset`: Number of problems to skip (number, optional)
190 
191### Users
192 
193- **get_user_profile** - Retrieves profile information about a LeetCode user
194 
195  - `username`: LeetCode username (string, required)
196 
197- **get_user_contest_ranking** - Retrieves a user's contest ranking information
198 
199  - `username`: LeetCode username (string, required)
200  - `attended`: Whether to include only the contests the user has participated in (boolean, optional, default: true)
201 
202- **get_recent_submissions** - Retrieves a user's recent submissions on LeetCode Global
203 
204  - `username`: LeetCode username (string, required)
205  - `limit`: Maximum number of submissions to return (number, optional, default: 10)
206 
207- **get_recent_ac_submissions** - Retrieves a user's recent accepted submissions
208 
209  - `username`: LeetCode username (string, required)
210  - `limit`: Maximum number of submissions to return (number, optional, default: 10)
211 
212- **get_user_status** - Retrieves the current user's status
213 
214  - No parameters required
215 
216- **get_problem_submission_report** - Retrieves detailed information about a specific submission
217 
218  - `id`: The numerical submission ID (number, required)
219 
220- **get_problem_progress** - Retrieves the current user's problem-solving progress
221 
222  - `offset`: Number of questions to skip (number, optional, default: 0)
223  - `limit`: Maximum number of questions to return (number, optional, default: 100)
224  - `questionStatus`: Filter by question status (enum: "ATTEMPTED", "SOLVED", optional)
225  - `difficulty`: Filter by difficulty levels (string[], optional)
226 
227- **get_all_submissions** - Retrieves paginated list of user's submissions
228  - `limit`: Maximum number of submissions to return (number, default: 20)
229  - `offset`: Number of submissions to skip (number, default: 0)
230  - `questionSlug`: Optional problem identifier (string, optional)
231  - `lang`: Programming language filter (string, optional, CN only)
232  - `status`: Submission status filter (enum: "AC", "WA", optional, CN only)
233  - `lastKey`: Pagination token for retrieving next page (string, optional, CN only)
234 
235### Notes
236 
237- **search_notes** - Searches for user notes on LeetCode China
238 
239  - `keyword`: Search term to filter notes (string, optional)
240  - `limit`: Maximum number of notes to return (number, optional, default: 10)
241  - `skip`: Number of notes to skip (number, optional, default: 0)
242  - `orderBy`: Sort order for returned notes (enum: "ASCENDING", "DESCENDING", optional, default: "DESCENDING")
243 
244- **get_note** - Retrieves user notes for a specific LeetCode problem
245  - `questionId`: The question ID of the LeetCode problem (string, required)
246  - `limit`: Maximum number of notes to return (number, optional, default: 10)
247  - `skip`: Number of notes to skip (number, optional, default: 0)
248- **create_note** - Creates a new note for a specific LeetCode problem
249 
250  - `questionId`: The question ID of the LeetCode problem (string, required)
251  - `content`: The content of the note, supports markdown format (string, required)
252  - `summary`: An optional short summary or title for the note (string, optional)
253 
254- **update_note** - Updates an existing note with new content or summary
255  - `noteId`: The ID of the note to update (string, required)
256  - `content`: The new content for the note, supports markdown format (string, required)
257  - `summary`: An optional new short summary or title for the note (string, optional)
258 
259### Solutions
260 
261- **list_problem_solutions** - Retrieves a list of community solutions for a specific problem
262 
263  - `questionSlug`: The URL slug/identifier of the problem (string, required)
264  - `limit`: Maximum number of solutions to return (number, optional, default: 10)
265  - `skip`: Number of solutions to skip (number, optional)
266  - `userInput`: Search term to filter solutions (string, optional)
267  - `tagSlugs`: Array of tag identifiers to filter solutions (string[], optional, default: [])
268  - `orderBy`: Sorting criteria for the returned solutions
269    - Global: enum: "HOT", "MOST_RECENT", "MOST_VOTES", optional, default: "HOT"
270    - CN: enum: "DEFAULT", "MOST_UPVOTE", "HOT", "NEWEST_TO_OLDEST", "OLDEST_TO_NEWEST", optional, default: "DEFAULT"
271 
272- **get_problem_solution** - Retrieves the complete content of a specific solution
273  - `topicId`: Unique topic ID of the solution (string, required, Global only)
274  - `slug`: Unique slug/identifier of the solution (string, required, CN only)
275 
276## Available Resources
277 
278| Resource Name          | Global | CN  | Auth Required | Description                                                  |
279| ---------------------- | :----: | :-: | :-----------: | ------------------------------------------------------------ |
280| **problem-categories** |   ✅   | ✅  |      ❌       | A list of all problem classification categories              |
281| **problem-tags**       |   ✅   | ✅  |      ❌       | A detailed collection of algorithmic and data structure tags |
282| **problem-langs**      |   ✅   | ✅  |      ❌       | A complete list of all supported programming languages       |
283| **problem-detail**     |   ✅   | ✅  |      ❌       | Provides details about a specific problem                    |
284| **problem-solution**   |   ✅   | ✅  |      ❌       | Provides the complete content of a specific solution         |
285 
286## Resource URIs
287 
288- **problem-categories** - A list of all problem classification categories
289 
290  - URI: `categories://problems/all`
291 
292- **problem-tags** - A detailed collection of algorithmic and data structure tags
293 
294  - URI: `tags://problems/all`
295 
296- **problem-langs** - A complete list of all programming languages supported by LeetCode
297 
298  - URI: `langs://problems/all`
299 
300- **problem-detail** - Provides details about a specific LeetCode problem
301 
302  - URI: `problem://{titleSlug}`
303  - Parameters:
304    - `titleSlug`: Problem identifier as it appears in the LeetCode URL
305 
306- **problem-solution** - Provides the complete content of a specific solution
307  - Global URI: `solution://{topicId}`
308    - Parameters:
309      - `topicId`: Unique topic ID of the solution
310  - CN URI: `solution://{slug}`
311    - Parameters:
312      - `slug`: Unique slug/identifier of the solution
313 
314## Authentication
315 
316User-specific data access requires LeetCode session authentication:
317 
3181. Log in to LeetCode ([Global](https://leetcode.com) or [China](https://leetcode.cn) site)
3192. Extract `LEETCODE_SESSION` cookie from browser developer tools
3203. Configure server with `--session` flag or `LEETCODE_SESSION` environment variable
321 
322## Response Format
323 
324All tools return JSON-formatted responses with the following structure:
325 
326```json
327{
328  "content": [
329    {
330      "type": "text",
331      "text": "JSON_DATA_STRING"
332    }
333  ]
334}
335```
336 
337The `JSON_DATA_STRING` contains either the requested data or an error message for failed requests.
338 
339## License
340 
341This project is licensed under the MIT License.
342