Leetcode MCP Server

What jinzcdev/leetcode-mcp-server MCP server does

The jinzcdev/leetcode-mcp-server MCP server connects MCP clients to LeetCode's global and China platforms. It provides tools for discovering problems, reading problem statements, checking the daily challenge, inspecting public user data, and retrieving community solution articles.

Problem tools cover three common workflows. search_problems filters problems by keywords, tags, category, and difficulty, with pagination through limit and offset values. get_problem returns a known problem's description, examples, constraints, and metadata using its title slug. get_daily_challenge returns the current day's featured problem.

User-facing read-only tools retrieve public profiles, contest rankings, recent submissions, and recent accepted submissions. Recent submission history is available only on the global site, while accepted-submission lookup works on both supported sites. Community solution access uses a two-step flow: first list articles for a problem to obtain a topic ID, then request the article content with that ID.

How it works

The server communicates with an MCP client using either standard input/output or Streamable HTTP. Stdio is the default and is intended for local client configurations. HTTP mode starts a server that listens on a configured host and port and exposes the MCP endpoint, which defaults to /mcp.

Select the LeetCode deployment with --site global or --site cn; global is the default. Command-line options override matching environment variables. The available configuration covers the site, transport, HTTP port, HTTP host, and endpoint path.

The jinzcdev/leetcode-mcp-server MCP server does not require authentication for the listed problem, public-profile, ranking, recent-submission, or solution-article lookups. Pass a LeetCode session cookie when authenticated access to private or current-user data is needed. The cookie can be supplied with --session or through the LEETCODE_SESSION environment variable.

Setup and configuration

The repository requires Node.js 20 or newer. The documented npm execution path runs the published package with npx:

npx -y @jinzcdev/leetcode-mcp-server --site global

For LeetCode China, replace global with cn. To use HTTP transport, add --transport http and optionally set --port, --host, or --endpoint. The project also documents cloning the repository, installing dependencies, building it, and starting node build/index.js locally.

MCP client configuration can pass settings as command-line arguments or environment variables. Supported environment variables include LEETCODE_SITE, LEETCODE_SESSION, LEETCODE_TRANSPORT, LEETCODE_HTTP_PORT, LEETCODE_HTTP_HOST, and LEETCODE_HTTP_ENDPOINT. Session cookies should be treated as sensitive credentials.

Tools and capabilities

The jinzcdev/leetcode-mcp-server MCP server exposes tools for:

• Finding problems by filters and pagination.
• Reading complete problem details and the daily challenge.
• Looking up public profiles and contest performance.
• Reading recent submissions, including accepted-only history where supported.
• Listing solution article metadata and retrieving article content.

Results are returned as JSON for the problem, profile, ranking, submission, and solution operations described in the listing. Use a title slug for direct problem retrieval and a topic ID for full solution retrieval.

Limitations and notes

Recent non-accepted submission history is limited to LeetCode Global. Solution listing returns article metadata and topic IDs rather than the article body, so a second tool call is required for full content. Authenticated features depend on a valid LeetCode session cookie and are intended for private or current-user data. The server accesses LeetCode's public and authenticated APIs, so site availability and API behavior may affect results.