# doggybee/mcp-server-leetcode [Health: Active]

**Category:** 🤖 Coding Agents  
**Repository:** https://github.com/doggybee/mcp-server-leetcode  
**GitHub Stars:** 43  
**npm Downloads (last month):** 84  
**Views:** 3  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/doggybee-mcp-server-leetcode

## Description
An MCP server that enables AI models to search, retrieve, and solve LeetCode problems. Supports metadata filtering, user profiles, submissions, and contest data access.

## Tools
Capabilities this server exposes over MCP:

- **get-daily-challenge** — Get the daily challenge
- **get-problem** — Get details for a specific problem
- **search-problems** — Search for problems based on criteria
- **get-user-profile** — Get user information
- **get-user-submissions** — Get user submission history
- **get-user-contest-ranking** — Get user contest rankings
- **get-contest-details** — Get contest details

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `npx` (confidence: high):

```json
"mcpServers": {
  "mcp-server-leetcode": {
    "command": "npx",
    "args": ["-y","@smithery/cli"]
  }
}
```

## Documentation

## What doggybee/mcp-server-leetcode MCP server does

The doggybee/mcp-server-leetcode MCP server connects an MCP-compatible AI assistant with LeetCode data. It covers three main areas: problems, user information, and contests. Agents can retrieve the daily challenge, request a problem by its title slug, or search problem metadata using optional tags, difficulty, pagination limit, and offset values.

User-focused operations accept a LeetCode username and can return profile information, submission history, or contest rankings. Contest lookup uses a contest slug to retrieve contest details. The available material describes access to LeetCode data; it does not list a tool for submitting solutions or executing code.

## How it works

The package runs as a command-line MCP server. After installation, an MCP client starts the `mcp-server-leetcode` executable and communicates with it through the client configuration. The repository also exposes a programmable `LeetCodeService` API for JavaScript applications, including methods for fetching the daily challenge and searching problems.

In addition to callable tools, the server defines URI resources. Problem resources include `leetcode://daily-challenge`, individual problem paths using a title slug, and a filterable problem-list URI. User resources provide profile, submissions, and contest-ranking paths keyed by username. These resources can be useful when a client supports MCP resource browsing as well as tool invocation.

## Setup and configuration

Install the npm package globally with `npm install -g @mcpfun/mcp-server-leetcode`, then start the server with `mcp-server-leetcode`. A local package installation is also documented, and the repository can be cloned and built for development with npm scripts.

For Claude Desktop, add an MCP server entry whose command is `mcp-server-leetcode`. The README also shows a development configuration that starts the compiled JavaScript file with Node. No environment variables, API keys, or other credentials are specified in the provided material.

The package is published as `@mcpfun/mcp-server-leetcode`. The repository is licensed under MIT. The documented client integration is Claude for Desktop, while the server itself follows the MCP tool and resource model.

## Tools and capabilities

The doggybee/mcp-server-leetcode MCP server exposes these tools:

- `get-daily-challenge` retrieves the daily challenge.
- `get-problem` fetches details for a problem identified by `titleSlug`.
- `search-problems` filters problems by optional tags and difficulty and supports `limit` and `skip` values.
- `get-user-profile` retrieves information for a supplied username.
- `get-user-submissions` returns submission history with an optional result limit.
- `get-user-contest-ranking` retrieves contest rankings for a username.
- `get-contest-details` fetches information for a contest identified by `contestSlug`.

The repository describes the server as providing fast access to the LeetCode API, but it does not specify API rate limits, response schemas, or a separate authentication configuration. Check those operational details before deploying it for high-volume use.

_Full upstream README: https://allmcps.com/mcp/doggybee-mcp-server-leetcode/readme_