LeetCode MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LEETCODE_SITE | No | LeetCode API endpoint (global or cn, default: global) | global |
| LEETCODE_SESSION | No | LeetCode session cookie for authenticated API access (default: empty) | |
| LEETCODE_HTTP_HOST | No | HTTP server host when using Streamable HTTP (default: 127.0.0.1) | 127.0.0.1 |
| LEETCODE_HTTP_PORT | No | HTTP server port when using Streamable HTTP (default: 3000) | 3000 |
| LEETCODE_TRANSPORT | No | Transport mode (stdio or http, default: stdio) | stdio |
| LEETCODE_HTTP_ENDPOINT | No | HTTP endpoint path when using Streamable HTTP (default: /mcp) | /mcp |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_daily_challengeA | Retrieves today's Daily Challenge problem with full description (read-only, no auth). Returns problem details for the current date as JSON. Use get_problem when you know a specific titleSlug; use search_problems to discover problems by filters. |
| get_problemA | Retrieves a single LeetCode problem by titleSlug (read-only, no auth). Returns description, examples, constraints, and metadata as JSON. Use search_problems to find problems by keyword/tag/difficulty; use get_daily_challenge for today's featured problem. |
| search_problemsA | Searches LeetCode problems by category, tags, difficulty, and keywords (read-only, no auth). Supports pagination via limit/offset. Returns matching problem list as JSON. Use get_problem when you already know the titleSlug; use this to browse or discover problems. |
| get_user_profileA | Retrieves any user's public profile by username (read-only, no auth). Returns ranking, avatar, bio, submission stats, and platform-specific progress. Use this to look up other users or public stats. Use get_user_status (requires auth) instead to verify the current session user's login state—not for looking up arbitrary users. |
| get_recent_submissionsA | Retrieves a user's recent submission history on LeetCode Global (read-only, no auth). Includes both accepted and failed submissions. Global only—not available on CN. Use get_recent_ac_submissions for accepted-only results, or get_all_submissions (auth, current user) for paginated full history with filters. |
| get_recent_ac_submissionsA | Retrieves a user's recent accepted (AC) submissions (read-only, no auth). Available on both Global and CN. Use get_recent_submissions (Global only) to include failed attempts, or get_all_submissions (auth, current user) for full paginated history. |
| get_user_contest_rankingA | Retrieves a user's contest ranking and participation history (read-only, no auth). Returns overall rating, ranking, and per-contest performance as JSON. Use get_user_profile for general stats and ranking; use this specifically for contest performance data. |
| list_problem_solutionsA | Lists community solution articles for a problem (read-only, no auth). Returns metadata only (topicId)—not full content. Use get_problem_solution with the returned topicId to read the full article. Do not call this when you already have a topicId and need the solution text. |
| get_problem_solutionA | Retrieves full content of a community solution article (read-only, no auth). Requires topicId from list_problem_solutions. Returns article text, author, and metadata as JSON. Use list_problem_solutions first to discover solutions and obtain topicId. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| problem-categories | A list of all problem classification categories in LeetCode platform, including difficulty levels (Easy, Medium, Hard) and algorithmic domains. These categories help organize and filter coding problems for users based on their complexity and topic area. Returns an array of all available problem categories. |
| problem-tags | A detailed collection of algorithmic and data structure tags used by LeetCode to categorize problems. These tags represent specific algorithms (like 'dynamic-programming', 'binary-search') or data structures (such as 'array', 'queue', 'tree') that are relevant to solving each problem. Returns an array of all available problem tags for filtering and searching problems. |
| problem-langs | A complete list of all programming languages officially supported by LeetCode for code submission and problem solving. Returns an array of all available programming languages on the platform. |
TDQS
Scored across 9 tools
Most tools have clearly distinct purposes (e.g., get_problem vs search_problems vs get_daily_challenge). Slight overlap exists between get_recent_submissions and get_recent_ac_submissions, and between get_user_profile and get_user_contest_ranking, but descriptions help differentiate them.
All tools follow a consistent snake_case verb_noun pattern (get_daily_challenge, get_problem, search_problems, etc.). Minor variation between get_ and list_ verbs is natural and still predictable.
9 tools is well-scoped for a read-only LeetCode data access server. Each tool covers a distinct aspect (problems, users, submissions, solutions) without redundancy.
The set covers core read-only operations, but several tools referenced in descriptions are absent (get_user_status, get_all_submissions), leaving gaps for authenticated full submission history and session verification. These missing operations could cause agent failures when those capabilities are expected.