Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Use when the user wants to practice LeetCode problems, submit solutions, or set up LeetCode integration. Covers MCP server installation, learning-guided practice flow, solution submission, and authentication.
Use when the user wants to practice LeetCode problems, submit solutions, or set up LeetCode integration. Covers MCP server installation, learning-guided practice flow, solution submission, and authentication.
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete.
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run.
MCP server for LeetCode practice with learning-guided hints, solution submission, and AI-driven authentication.
Before anything else, check whether the get_started tool is available. If it is, the server is connected โ skip to the next section. If get_started is NOT available, the MCP server needs to be installed. Ask the user for confirmation before proceeding โ explain that this will download and run an npm package. The npm package is @sperekrestova/interactive-leetcode-mcp (source: GitHub). It runs over stdio transport. Requires Node.js >= 20. After the user confirms, add to the client's MCP configuration (the exact file varies by client): { "mcpServers": { "leetcode": { "command": "npx", "args": ["-y", "@sperekrestova/interactive-leetcode-mcp@3.1.1"] } } } For Claude Code specifically, you can also run: claude mcp add --transport stdio leetcode -- npx -y @sperekrestova/interactive-leetcode-mcp@3.1.1 Pin a specific version (shown above) rather than using @latest to avoid executing untested code. Users can check for newer versions at the npm page or GitHub releases and update the pinned version after reviewing the changelog. After adding the server, tell the user to restart their session so the MCP tools become available. Do not proceed with the session flow until get_started is accessible.
At the START of every LeetCode session, call the get_started tool. It returns the full usage guide: prompt invocation rules, session flow, learning mode rules, auth flow, and language map. Do not skip this โ it is a single fast call, not redundant with tool descriptions. The server has MCP prompts that must be explicitly invoked โ they are NOT auto-active. The get_started response tells you exactly when and how.
1. Call get_started <-- FIRST, every session 2. Invoke leetcode_learning_mode <-- BEFORE any problem discussion 3. User picks a problem 4. Invoke leetcode_problem_workflow(problemSlug, difficulty) 5. Invoke leetcode_workspace_setup(language, problemSlug, codeTemplate) 6. Guide user with progressive hints (4 levels) 7. submit_solution when ready Steps 2, 4, and 5 are MCP prompt invocations. Invoke them via the Skill tool or equivalent prompt mechanism. All three must happen BEFORE the user starts coding. Step 2 is non-negotiable. If you skip leetcode_learning_mode, you will bypass the progressive hint system and may show solutions prematurely. Invoke it before searching for or discussing any problem.
PromptWhenParamsleetcode_learning_modeSTART of session, before any problemnoneleetcode_problem_workflowAfter user selects a problemproblemSlug, difficultyleetcode_workspace_setupBefore user starts codinglanguage, problemSlug, codeTemplateleetcode_authentication_guideOn auth need, 401 errors, expired credsnone
Never show a full solution without working through hint levels 1 โ 2 โ 3 Level 1: Guiding questions ("What pattern do you see?") Level 2: General approaches ("Consider using a hash map...") Level 3: Specific hints ("Iterate once, tracking seen values...") Level 4: Pseudocode or partial implementation Only show complete solutions when explicitly requested AFTER earlier hints get_problem_solution returns full community solutions โ Level 4 or explicit request only
ToolPurposeAuth?get_daily_challengeToday's challengeNoget_problemProblem by slugNosearch_problemsFind by tags/difficulty/keywordsNolist_problem_solutionsSolution metadata (topicIds)Noget_problem_solutionFull solution โ Level 4 onlyNosubmit_solutionSubmit codeNo*get_user_profileAny user's statsNoget_recent_submissionsRecent submissionsNoget_recent_ac_submissionsAccepted submissionsNoget_user_contest_rankingContest rankingNostart_leetcode_authStart auth flowNosave_leetcode_credentialsValidate + save credsNocheck_auth_statusCheck credential stateNoget_user_statusCurrent user infoYesget_problem_submission_reportSubmission detailYesget_problem_progressProgress with filtersYesget_all_submissionsAll submissionsYes *submit_solution requires saved credentials to succeed.
Before auth-sensitive actions โ call check_auth_status If not authenticated or expired โ ask the user if they want to authenticate. Explain that this will store LeetCode session cookies locally at ~/.leetcode-mcp/credentials.json (owner-read/write only). Do not proceed without consent. After consent โ invoke leetcode_authentication_guide prompt Call start_leetcode_auth โ the prompt will guide the user through providing credentials โ call save_leetcode_credentials with the values the user provides On success โ retry original action On 401 from any tool โ repeat from step 1 Always delegate auth guidance to the leetcode_authentication_guide prompt. Do not improvise your own auth instructions โ the prompt handles browser-specific guidance, error recovery, and troubleshooting. Credential storage: The MCP server stores credentials locally at ~/.leetcode-mcp/credentials.json with file permissions 0o600 (owner-read/write only). Only csrftoken, LEETCODE_SESSION, and a createdAt timestamp are stored. Credentials are never transmitted to any third party โ they are used exclusively for direct LeetCode API calls. Typical credential lifetime is 7-14 days.
User saysPass to submit_solutionPython / Python 3python3Python 2pythonJavajavaC++cppJavaScriptjavascriptTypeScripttypescript Default: "Python" without version โ python3.
Resource URIWhat it providescategories://problems/allAll problem categoriestags://problems/allAll 60+ topic tagslangs://problems/allAll supported submission languagesproblem://{titleSlug}Problem detailsolution://{topicId}Solution detail (same learning-mode rules apply)
Jumping to problem search before invoking leetcode_learning_mode Showing full solutions without progressing through hint levels 1 โ 2 โ 3 Not invoking leetcode_workspace_setup โ code should live in a file, not only in chat Guiding auth manually instead of invoking leetcode_authentication_guide Passing "Python" to submit_solution instead of "python3" Not calling check_auth_status before auth-sensitive operations Skipping get_started and assuming tool descriptions are sufficient
Code helpers, APIs, CLIs, browser automation, testing, and developer operations.
Largest current source with strong distribution and engagement signals.