LeetCode MCP Server

The LeetCode MCP Server is a Model Context Protocol (MCP) server that provides seamless integration with LeetCode APIs, enabling advanced automation and intelligent interaction with LeetCode's programming problems, contests, solutions, and user data.

Features

• 🌐 Multi-site Support: Support​ both leetcode.com (Global) and leetcode.cn (China) platforms
• 🔌 Dual Transport Modes: Run as a stdio process (default) or as a Streamable HTTP server for web-based integrations
• 📊 Problem Data Retrieval: Obtain detailed problem descriptions, constraints, examples, official editorials, and ​user-submitted solutions
• 👤 User Data Access: Retrieve user profiles, submission history, and contest performance
• 🔒 ​Private Data Access: Create and query user notes, track problem-solving progress, and analyze submission details (AC/WA analysis)
• 🔍 Advanced Search Capabilities: Filter problems by tags, difficulty levels, categories, and keywords
• 📅 Daily Challenge Access: Easily access daily challenge problems

Prerequisites

1. Node.js (v20.x or above)

2. (Optional) LeetCode session cookie for authenticated API access

Installation

# Install from npm
npm install @jinzcdev/leetcode-mcp-server -g

# Run with Global site configuration (stdio transport, default)
npx -y @jinzcdev/leetcode-mcp-server --site global

# Run with authentication (for accessing private data)
npx -y @jinzcdev/leetcode-mcp-server --site global --session 

# Run as a Streamable HTTP server
npx -y @jinzcdev/leetcode-mcp-server --transport http --port 3000 --site global

Alternatively, you can clone the repository and run it locally:

# Clone the repository
git clone https://github.com/jinzcdev/leetcode-mcp-server.git

# Navigate to the project directory
cd leetcode-mcp-server

# Build the project
npm install && npm run build

# Run the server (stdio transport)
node build/index.js --site global

# Or run as a Streamable HTTP server
node build/index.js --transport http --port 3000 --site global

Usage

The server supports two transport modes:

Command-Line Options

MCP Client Configuration (stdio)

Add the following server entry to your MCP client configuration file:

Option 1: Using Environment Variables

{
  "mcpServers": {
    "leetcode": {
      "command": "npx",
      "args": ["-y", "@jinzcdev/leetcode-mcp-server"],
      "env": {
        "LEETCODE_SITE": "global",
        "LEETCODE_SESSION": ""
      }
    }
  }
}

Option 2: Using Command Line Arguments

{
  "mcpServers": {
    "leetcode": {
      "command": "npx",
      "args": [
        "-y",
        "@jinzcdev/leetcode-mcp-server",
        "--site",
        "global",
        "--session",
        ""
      ]
    }
  }
}

For LeetCode China site, modify the `--site` parameter to `cn`.

> [!NOTE]

>

> The exact configuration file location and JSON structure may vary by MCP client. Some clients use an `mcp.servers` wrapper or a `type` field — refer to your client's documentation and adapt the example accordingly.

MCP Client Configuration (Streamable HTTP)

First, start the server in HTTP mode:

npx -y @jinzcdev/leetcode-mcp-server --transport http --port 3000 --site global

Then connect your MCP client to the running server:

{
  "mcpServers": {
    "leetcode": {
      "type": "http",
      "url": "http://127.0.0.1:3000/mcp"
    }
  }
}

To use authenticated endpoints, pass the session cookie when starting the server:

npx -y @jinzcdev/leetcode-mcp-server --transport http --port 3000 --site global --session

> [!NOTE]

> Some MCP clients use `"type": "http"` or `"type": "streamableHttp"` alongside the `url` field. Refer to your client's documentation for the exact HTTP transport configuration format.

> [!TIP]

>

> The server supports the following optional environment variables:

>

> - `LEETCODE_SITE`: LeetCode API endpoint (`global` or `cn`, default: `global`)

> - `LEETCODE_SESSION`: LeetCode session cookie for authenticated API access (default: empty)

> - `LEETCODE_TRANSPORT`: Transport mode (`stdio` or `http`, default: `stdio`)

> - `LEETCODE_HTTP_PORT`: HTTP server port when using Streamable HTTP (default: `3000`)

> - `LEETCODE_HTTP_HOST`: HTTP server host when using Streamable HTTP (default: `127.0.0.1`)

> - `LEETCODE_HTTP_ENDPOINT`: HTTP endpoint path when using Streamable HTTP (default: `/mcp`)

>

> Priority Note:

> Command-line arguments take precedence over environment variables when both are specified. For example:

>

> - If `LEETCODE_SITE=cn` is set but you run `leetcode-mcp-server --site global`, the server will use `global`.

> - If `LEETCODE_SESSION` exists but you provide `--session "new_cookie"`, the command-line session value will be used.

Available Tools

Problems

Users

Submissions

Notes

Solutions

Tool Parameters

Problems

• get_daily_challenge - Retrieves today's LeetCode Daily Challenge problem with complete details

• get_problem - Retrieves details about a specific LeetCode problem

• search_problems - Searches for LeetCode problems based on multiple filter criteria
  • `category`: Problem category filter (string, optional, default: "all-code-essentials")
  • `tags`: List of topic tags to filter problems by (string[], optional)
  • `difficulty`: Problem difficulty level filter (enum: "EASY", "MEDIUM", "HARD", optional)
  • `searchKeywords`: Keywords to search in problem titles and descriptions (string, optional)
  • `limit`: Maximum number of problems to return (number, optional, default: 10)
  • `offset`: Number of problems to skip (number, optional)

Users

• get_user_profile - Retrieves profile information about a LeetCode user

• get_user_contest_ranking - Retrieves a user's contest ranking information

• get_recent_submissions - Retrieves a user's recent submissions on LeetCode Global

• get_recent_ac_submissions - Retrieves a user's recent accepted submissions

• get_user_status - Retrieves the current user's status

• get_problem_submission_report - Retrieves detailed information about a specific submission

• get_problem_progress - Retrieves the current user's problem-solving progress

• get_all_submissions - Retrieves paginated list of user's submissions
  • `limit`: Maximum number of submissions to return (number, default: 20)
  • `offset`: Number of submissions to skip (number, default: 0)
  • `questionSlug`: Optional problem identifier (string, optional)
  • `lang`: Programming language filter (string, optional, CN only)
  • `status`: Submission status filter (enum: "AC", "WA", optional, CN only)
  • `lastKey`: Pagination token for retrieving next page (string, optional, CN only)

Submissions

• run_code - Runs code for a specific problem and waits until finished (requires authentication)

• submit_solution - Submits code for a specific problem and waits until finished (requires authentication)

Notes

• search_notes - Searches for user notes on LeetCode China

• get_note - Retrieves user notes for a specific LeetCode problem
  • `questionId`: The question ID of the LeetCode problem (string, required)
  • `limit`: Maximum number of notes to return (number, optional, default: 10)
  • `skip`: Number of notes to skip (number, optional, default: 0)
• create_note - Creates a new note for a specific LeetCode problem

• update_note - Updates an existing note with new content or summary
  • `noteId`: The ID of the note to update (string, required)
  • `content`: The new content for the note, supports markdown format (string, required)
  • `summary`: An optional new short summary or title for the note (string, optional)

Solutions

• list_problem_solutions - Retrieves a list of community solutions for a specific problem

• get_problem_solution - Retrieves the complete content of a specific solution
  • `topicId`: Unique topic ID of the solution (string, required, Global only)
  • `slug`: Unique slug/identifier of the solution (string, required, CN only)

Available Resources

Resource URIs

• problem-categories - A list of all problem classification categories

• problem-tags - A detailed collection of algorithmic and data structure tags

• problem-langs - A complete list of all programming languages supported by LeetCode

• problem-detail - Provides details about a specific LeetCode problem

• problem-solution - Provides the complete content of a specific solution
  • Global URI: `solution://{topicId}`
    • Parameters:
      • `topicId`: Unique topic ID of the solution
  • CN URI: `solution://{slug}`
    • Parameters:
      • `slug`: Unique slug/identifier of the solution

Authentication

User-specific data access requires LeetCode session authentication:

1. Log in to LeetCode (Global or China site)

2. Extract `LEETCODE_SESSION` cookie from browser developer tools

3. Configure server with `--session` flag or `LEETCODE_SESSION` environment variable

Response Format

All tools return JSON-formatted responses with the following structure:

{
  "content": [
    {
      "type": "text",
      "text": "JSON_DATA_STRING"
    }
  ]
}

The `JSON_DATA_STRING` contains either the requested data or an error message for failed requests.

License

This project is licensed under the MIT License.