leetcode-problem-fetcher

leetcode-problem-fetcher

A specialized skill for fetching and parsing LeetCode problems with complete metadata, suitable for competitive programming practice, interview preparation, and algorithm learning workflows.

Purpose

Extract comprehensive problem data from LeetCode including:

• Problem statements and descriptions
• Input/output constraints and formats
• Test cases and hidden constraints
• Problem difficulty, tags, and acceptance rate
• Related problems and pattern tags
• Hints and solution approaches

Capabilities

Core Features

1. Problem Retrieval
2. Fetch problems by title slug (URL-friendly name)
3. Retrieve daily challenge problems
4. Search problems by category, tags, difficulty, or keywords
5. Access premium problem alternatives when available

1. Metadata Extraction
2. Difficulty level (Easy, Medium, Hard)
3. Acceptance rate and submission statistics
4. Problem tags and categories
5. Related problems and similar questions
6. Company tags (when available)

1. Content Parsing
2. Problem description in markdown format
3. Input/output examples with explanations
4. Constraints and edge cases
5. Follow-up questions and optimizations
6. Code templates for multiple languages

1. User Data Access
2. User profile and statistics
3. Contest ranking and history
4. Submission history and solutions
5. Progress tracking across problem sets

Integration Options

MCP Server (Recommended)

# Install LeetCode MCP Server by jinzcdev
claude mcp add-json "leetcode" '{"type":"stdio","command":"npx","args":["-y","@jinzcdev/leetcode-mcp-server","--site","global"]}'

Available MCP Tools:

• get_daily_challenge - Fetch daily LeetCode challenge
• get_problem - Retrieve problem by titleSlug
• search_problems - Filter by category, tags, difficulty, keywords
• get_user_profile - Access user data
• get_user_contest_ranking - Track contest performance

Direct API Integration

// GraphQL endpoint for LeetCode
const LEETCODE_GRAPHQL = 'https://leetcode.com/graphql';

// Query for problem details
const problemQuery = `
  query getProblem($titleSlug: String!) {
    question(titleSlug: $titleSlug) {
      questionId
      title
      titleSlug
      content
      difficulty
      topicTags { name slug }
      hints
      sampleTestCase
      codeSnippets { lang code }
      stats
    }
  }
`;

Browser Extension

Competitive Companion - Parses problems from LeetCode and 115+ other online judges:

• Chrome: competitive-companion
• Firefox: competitive-companion

Usage

Fetch a Problem

# Using MCP Server
leetcode get_problem --titleSlug "two-sum"

# Output includes:
# - Problem title and description
# - Difficulty and acceptance rate
# - Topic tags
# - Examples and constraints
# - Code templates

Search Problems

# Search by difficulty and tags
leetcode search_problems --difficulty MEDIUM --tags "dynamic-programming,array"

# Search by keyword
leetcode search_problems --keyword "substring"

Get Daily Challenge

# Fetch today's daily challenge
leetcode get_daily_challenge

Output Schema

{
  "problem": {
    "id": "string",
    "title": "string",
    "titleSlug": "string",
    "difficulty": "Easy|Medium|Hard",
    "acceptanceRate": "number",
    "description": "string (markdown)",
    "constraints": ["string"],
    "examples": [
      {
        "input": "string",
        "output": "string",
        "explanation": "string"
      }
    ],
    "hints": ["string"],
    "topicTags": ["string"],
    "similarQuestions": ["string"],
    "codeTemplates": {
      "python3": "string",
      "cpp": "string",
      "java": "string"
    }
  },
  "metadata": {
    "fetchedAt": "ISO8601 timestamp",
    "source": "leetcode.com|leetcode.cn"
  }
}

Integration with Processes

This skill enhances the following processes:

• leetcode-problem-solving - Core problem-solving workflow
• pattern-recognition - Identifying algorithmic patterns
• faang-interview-prep - FAANG interview preparation

References

• LeetCode MCP Server (jinzcdev)
• LeetCode MCP Server (doggybee)
• Competitive Companion
• Competitive Programming Helper (CPH)

Error Handling

| Error | Cause | Resolution | |-------|-------|------------| | PROBLEM_NOT_FOUND | Invalid titleSlug | Verify problem URL or slug | | RATE_LIMITED | Too many requests | Implement exponential backoff | | AUTH_REQUIRED | Premium problem | Use alternative or authenticate | | NETWORK_ERROR | Connection failed | Check network, retry with backoff |

Best Practices

1. Caching: Cache problem data to reduce API calls
2. Rate Limiting: Respect LeetCode's rate limits (use delays between requests)
3. Error Handling: Gracefully handle premium/locked problems
4. Offline Mode: Store fetched problems for offline practice
5. Data Freshness: Re-fetch periodically for updated statistics