LeetCode MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LEETCODE_SESSION | Yes | Your LeetCode session cookie | |
| LEETCODE_CSRFTOKEN | Yes | Your LeetCode csrftoken cookie |
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| fetch_problem_plain_textC | Fetches the plain text content of a LeetCode problem given its URL. |
| generate_templateB | Generates a language-specific code template for a given LeetCode problem slug. |
| run_codeC | Executes code against the example test cases for a LeetCode problem and returns the results. |
| submit_codeC | Submits the code for a LeetCode problem for evaluation against the full test suite. |
| get_daily_challengeA | Retrieves today's LeetCode Daily Challenge problem with complete details, including problem description, constraints, and examples. |
| get_problemC | Retrieves details about a specific LeetCode problem, including its description, examples, constraints, and related information. |
| search_problemsA | Searches for LeetCode problems based on multiple filter criteria including categories, tags, difficulty levels, and keywords, with pagination support. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 7 tools
Each tool has a clearly distinct purpose: fetching problem text, generating templates, running/submitting code, retrieving daily challenge, getting full problem details, and searching. No two tools overlap in functionality.
All tool names follow a consistent verb_noun pattern with underscores (e.g., fetch_problem_plain_text, run_code, submit_code). No mixing of styles.
Seven tools is well-scoped for a LeetCode problem-solving assistant, covering essential operations from retrieval to submission without unnecessary extras.
The tool set covers core workflows: fetch, template, run, submit, search, and daily challenge. Minor gaps like user account management or submission history are absent but not critical for the primary use case.