check_auth_status
Checks if LeetCode credentials exist and are still valid. Returns authentication status, username if authenticated, and credential age information.
LABSCO SUMMARY
It makes the assistant tutor you instead of handing over the answer.
start_problem opens a session per problem and request_hint walks it up one level at a time; list_problem_solutions and get_problem_solution reject with HINT_LEVEL_TOO_LOW until that session has reached the maximum, so the community write-ups are not reachable on the first turn. run_local_tests keeps the inner loop off LeetCode entirely, and with LEETCODE_MCP_STRICT_MODE=1 set, submit_solution refuses until a local run has passed for that problem. The 24 tools only work as designed if the client actually calls get_started first — the flow is carried by convention, not enforced at every step.
What it is
An MCP server in front of LeetCode that adds a tutoring session on top of it: per-problem hint levels, a local test runner, and a gate on community solutions.
What you get
- Problem access — the daily challenge, a problem by slug, and search across categories, tags, difficulty and keywords with pagination.
- A tutoring session per problem that survives a client restart: open or resume it, read its state, or reset it back to hint level 0.
- A hint ladder that advances one step at a time — clarification, approach, implementation sketch, then the solution unlock at level 4.
- Community solutions behind that ladder — metadata first, then the full text of a chosen solution.
- A local runner that executes your code in an isolated subprocess and reports stdout, stderr and exit code, plus a doctor call that says which language runtimes and OS sandboxes this host has.
- Submission to LeetCode itself, returning acceptance status, runtime and memory stats, or the failing test case.
- Account history — profile, contest ranking, recent and accepted submissions, per-problem progress, and the source of any past submission by ID.
Requirements
A LeetCode account for anything marked as needing authentication: start_leetcode_auth opens the login and walks the agent through pulling the session and csrftoken values out of browser DevTools, and save_leetcode_credentials validates and stores them. run_local_tests needs a language runtime on the host — runner_doctor reports whether python3, go, java and the sandboxes bwrap, firejail or sandbox-exec were found.
Setup effort
One command plus credentials — npx -y @sperekrestova/interactive-leetcode-mcp@latest, then supply credentials
USE CASES
01
Practising a problem without being handed the answer
Open a session for the problem and pull hints one level at a time, so the assistant escalates only when you are stuck.
02
Testing a solution without burning a LeetCode submission
Run the code locally in the inner loop and only submit once it passes; the code you pass in has to carry its own test invocations, and runner_doctor says whether the host has the runtime for it.
03
Reading a community solution once you have earned it
Drive the hints to the top of the ladder, then take the metadata list and open the write-up you want in full.
04
Starting the day on the daily challenge
Pull today's problem with its constraints and examples and open a session on it in the same turn.
05
Seeing where your solving actually stands
Read the account's own history rather than guessing — what has been solved, what was attempted, and how contests went.
24 tools
Counted once with only startup setup. Other versions, modes or optional credentials may expose a different list.
get_all_submissions
Retrieves a paginated list of the current user's submissions for a specific problem or all problems on LeetCode Global, with detailed submission metadata (requires authentication)
get_daily_challenge
Retrieves today's LeetCode Daily Challenge problem with complete details, including problem description, constraints, and examples. After fetching, invoke the leetcode_learning_mode and leetcode_problem_workflow prompts before helping the user work on it.
get_problem
Retrieves details about a specific LeetCode problem, including its description, examples, constraints, and related information. After fetching, invoke the leetcode_learning_mode and leetcode_problem_workflow prompts before helping the user work on it.
get_problem_progress
Retrieves the current user's problem-solving status with filtering options, including detailed solution history for attempted or solved questions (requires authentication)
get_problem_solution
Retrieves the full content of a specific community solution. GATED: rejects with HINT_LEVEL_TOO_LOW unless the session for titleSlug has reached the maximum hint level. Pass the topicId returned by list_problem_solutions.
get_problem_submission_report
Retrieves detailed information about a specific LeetCode submission by its ID, including source code, runtime stats, and test results (requires authentication)
get_recent_ac_submissions
Retrieves a user's recent accepted (AC) submissions on LeetCode Global, focusing only on successfully completed problems
get_recent_submissions
Retrieves a user's recent submissions on LeetCode Global, including both accepted and failed submissions with detailed metadata
get_session_state
Returns the persisted session for a problem, or null if the user has not called start_problem for it. Useful for restoring context after a restart.
get_started
Returns the usage guide for this MCP server: which prompts to invoke and when, session flow, auth flow, and submission language map. Call this at the start of any LeetCode practice session.
get_user_contest_ranking
Retrieves a user's contest ranking information on LeetCode, including overall ranking, participation history, and performance metrics across contests
get_user_profile
Retrieves profile information about a LeetCode user, including user stats, solved problems, and profile details
get_user_status
Retrieves the current user's status on LeetCode, including login status, premium membership details, and user information (requires authentication)
list_problem_solutions
Retrieves community solution metadata (topicIds) for a problem. GATED: rejects with HINT_LEVEL_TOO_LOW unless the active session for the slug has reached the maximum hint level. Drive the user through request_hint until that level is reached.
request_hint
Advances the hint level for an active session and returns the next hint. Levels: 1 clarification → 2 approach → 3 implementation sketch → 4 solution unlock. The community-solutions tools become callable only after this has been driven to level 4.
reset_session
Resets the tutoring session for a problem back to hint level 0. Use when the user wants to re-attempt the problem from scratch.
run_local_tests
Runs the user's code locally in an isolated subprocess, captures stdout / stderr / exit code, and updates the session's lastLocalRunPassed flag. Use this in the inner loop instead of submit_solution — it costs no LeetCode submission and turns around in seconds. The agent is responsible for including test invocations (e.g. print(Solution().twoSum([2,7,11,15], 9))) in the code passed in. Currently runnable: python3, go, and java.
runner_doctor
Reports which language runtimes (python3, go, java) and OS sandbox tools (bwrap, firejail, sandbox-exec) are detected on this host. Useful for diagnosing 'LANGUAGE_RUNTIME_NOT_FOUND' errors and confirming whether run_local_tests will be sandboxed.
save_leetcode_credentials
Validates and saves LeetCode credentials provided by the user. Validates credentials by making a test API call to LeetCode, then securely stores them for future authenticated requests.
search_problems
Searches for LeetCode problems based on multiple filter criteria including categories, tags, difficulty levels, and keywords, with pagination support
start_leetcode_auth
Initiates LeetCode authentication flow. Opens browser to LeetCode login (if possible) and provides instructions for the AI agent to guide the user through manual credential extraction from browser DevTools.
start_problem
Opens (or resumes) a tutoring session for a LeetCode problem. Must be called before request_hint, list_problem_solutions, or get_problem_solution. Idempotent: re-running on a slug the user is already mid-way through preserves their hint progress.
submit_solution
Submit a solution to a LeetCode problem and get results. Returns acceptance status, runtime/memory stats, or failed test case details. When LEETCODE_MCP_STRICT_MODE=1 is set, requires run_local_tests to have last passed for the problem first — saves real LeetCode submissions for solutions that pass examples locally.
BEFORE YOU INSTALL
What to know first
Tools you get
24 tools when we connected. start_problem must run before the hint and solution tools, list_problem_solutions and get_problem_solution unlock only at the solution hint level, and account tools need saved LeetCode cookies.
Requires
Node.js v20.x or above
Where it runs
The documented client runs the server on your machine.
CONTEXT COST
Moderate Standing cost
Rated by the size of the 24 tool definitions that ride along on every turn, not by how many there are
INSTALLATION
Connect your client
Server setup
Setup
TERMINAL
git clone https://github.com/SPerekrestova/interactive-leetcode-mcp.git
cd interactive-leetcode-mcp
npm install && npm run build
npm linknpx
TERMINAL
npx -y @sperekrestova/interactive-leetcode-mcp@latestMCP Clients
Claude Code
CLAUDE CODE · JSON
{
"mcpServers": {
"leetcode": {
"command": "npx",
"args": [
"-y",
"@sperekrestova/interactive-leetcode-mcp@latest"
]
}
}
}
