It is a read path only: nothing here submits a solution, runs code or edits a profile, which makes it a source for building study sets and reviewing history rather than a way to practise inside the client. The two halves pair well — search-problems narrows by tag and difficulty, get-user-submissions shows what has already been attempted — and contest results are reachable from both a contest and a user.
A read-only server over LeetCode's public data, 7 tools spanning problems, the daily challenge, contests, and user profiles, submissions and rankings.
- get-problem returns a problem by its titleSlug, and get-daily-challenge returns the current day's without needing to know which one it is
- search-problems filters by tags and difficulty, with skip and limit for paging through the result set
- get-user-profile and get-user-submissions cover a public profile and its recent activity, the second with a limit
- get-contest-details by contestSlug and get-user-contest-ranking for where a user placed in one
A titleSlug, contestSlug or username to address anything — the tools take slugs and usernames rather than numeric IDs, so a job that starts from a problem title goes through search-problems first. No key or account appears in the tool set. MIT licensed.
One command — npx -y @mcpfun/mcp-server-leetcode