Leetcode MCP Server vs Cursor Usage
A side-by-side look at the Leetcode MCP Server and Cursor Usage MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Leetcode MCP Server for coding agents work as a local process; choose Cursor Usage for coding agents as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Leetcode MCP Server when
- You need dedicated capabilities in the Coding Agents domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: other.
- You want tools like
get_daily_challenge, get_problem, search_problems.
Choose Cursor Usage when
- You need dedicated capabilities in the Coding Agents domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: API key required.
- You have the keys it needs:
CURSOR_API_KEY. - You want tools like
get_team_members, get_spending, get_daily_usage.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Coding Agents | Coding Agents |
| Quality signal | 65/100 · Great | 59/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | other | API key required |
| Pricing | Free | BYOK (pay the provider) |
| Required env vars | None listed | CURSOR_API_KEY |
| Verified owner | Community listing | Community listing |
| GitHub stars | 154 | 8 |
| Directory activity | 6 views 0 installs 0 upvotes | 1 views 0 installs 0 upvotes |
| Tools | 9 | 17 |
| Full listing | View Leetcode MCP Server | View Cursor Usage |
Tools & capabilities
Leetcode MCP Server tools 9
get_daily_challengeRetrieves today's Daily Challenge problem with full description (read-only, no auth). Returns problem details for the current date as JSON. Use get_problem when you know a specific titleSlug; use search_problems to discover problems by filters.get_problemRetrieves a single LeetCode problem by titleSlug (read-only, no auth). Returns description, examples, constraints, and metadata as JSON. Use search_problems to find problems by keyword/tag/difficulty; use get_daily_challenge for today's featured problem.search_problemsSearches LeetCode problems by category, tags, difficulty, and keywords (read-only, no auth). Supports pagination via limit/offset. Returns matching problem list as JSON. Use get_problem when you already know the titleSlug; use this to browse or discover problems.get_user_profileRetrieves any user's public profile by username (read-only, no auth). Returns ranking, avatar, bio, submission stats, and platform-specific progress. Use this to look up other users or public stats. Use get_user_status (requires auth) instead to verify the current session user's login state—not for looking up arbitrary users.get_recent_submissionsRetrieves a user's recent submission history on LeetCode Global (read-only, no auth). Includes both accepted and failed submissions. Global only—not available on CN. Use get_recent_ac_submissions for accepted-only results, or get_all_submissions (auth, current user) for paginated full history with filters.get_recent_ac_submissionsRetrieves a user's recent accepted (AC) submissions (read-only, no auth). Available on both Global and CN. Use get_recent_submissions (Global only) to include failed attempts, or get_all_submissions (auth, current user) for full paginated history.get_user_contest_rankingRetrieves a user's contest ranking and participation history (read-only, no auth). Returns overall rating, ranking, and per-contest performance as JSON. Use get_user_profile for general stats and ranking; use this specifically for contest performance data.list_problem_solutionsLists community solution articles for a problem (read-only, no auth). Returns metadata only (topicId)—not full content. Use get_problem_solution with the returned topicId to read the full article. Do not call this when you already have a topicId and need the solution text.get_problem_solutionRetrieves full content of a community solution article (read-only, no auth). Requires topicId from list_problem_solutions. Returns article text, author, and metadata as JSON. Use list_problem_solutions first to discover solutions and obtain topicId.
Cursor Usage tools 17
get_team_membersList all team members with their roles and status. Returns name, email, role, and whether they've been removed.get_spendingGet current billing cycle spending for all team members. Shows spend in dollars, included vs overage, fast premium requests, and spend limits.get_daily_usageGet daily usage data per user: lines added/deleted, applies, accepts, rejects, tabs, requests by mode (composer/chat/agent), models used, and client versions.get_billing_groupsGet billing groups with member lists, group-level spend, and daily spend breakdown. Also returns billing cycle dates.get_usage_eventsGet granular per-request usage events with model, token counts, costs, and whether the request was chargeable. Supports filtering by user email and date range.set_spend_limitSet a hard spending limit (in dollars) for a specific team member. Use with caution — this will block the user from making requests once the limit is reached.get_dauGet daily active users over time, including breakdowns for CLI, cloud agent, and Bugbot usage.get_model_usageGet model usage breakdown per day: which models are being used, how many messages, and by how many users. Essential for understanding model adoption and cost drivers.get_agent_editsGet agent edit metrics: suggested vs accepted vs rejected diffs and lines. Shows how effectively the team is using AI-generated code.get_tabsGet tab autocomplete usage: suggestions shown vs accepted vs rejected, with line-level detail.get_mcp_usageGet MCP (Model Context Protocol) tool usage: which MCP servers and tools are being used, and how often.get_file_extensionsGet top file extensions being edited with AI: which file types get the most AI suggestions, accepts, and rejects.- +5 more on the listing page
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Leetcode MCP Server
{
"mcpServers": {
"jinzcdev-leetcode-mcp-server": {
"command": "npx",
"args": [
"-y",
"@jinzcdev/leetcode-mcp-server"
]
}
}
}
Cursor Usage
{
"mcpServers": {
"ofershap-cursor-usage": {
"command": "npx",
"args": [
"-y",
"cursor-usage-mcp"
],
"env": {
"CURSOR_API_KEY": "YOUR_CURSOR_API_KEY_HERE"
}
}
}
}
Frequently asked questions
Leetcode MCP Server is categorized under Coding Agents and uses a local stdio subprocess. Cursor Usage belongs to Coding Agents and uses a local stdio subprocess. Pick Leetcode MCP Server for coding agents work and Cursor Usage for coding agents.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Leetcode MCP Server is listed as free. Auth: other. Cursor Usage is bring-your-own-key: usage is billed by the API provider you supply a key for. Auth: api key required. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add jinzcdev-leetcode-mcp-server and ofershap-cursor-usage as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Leetcode MCP Server has a quality signal of 65/100 (Great) with 6 views, 0 installs and 154 GitHub stars. Cursor Usage has 59/100 (Good) with 1 views, 0 installs and 8 GitHub stars.