LeetCode Crawler MCP Server

Connect LeetCode Crawler to Claude, Cursor or any other MCP client and it stops being a tab you switch to. mcp server for craw the interview questions in discussion. The leetcode crawler mcp server is what makes that connection.

What the server does

Crawl LeetCode interview discussion forums, extract structured intelligence with Claude AI, and expose the data as an MCP (Model Context Protocol) server for Claude Desktop and Claude Code.

• Crawls LeetCode discussion forums filtered by company tag (google, meta, amazon, etc.)
• Classifies posts by type (leetcode, discuss_link, discussion)
• Groups and deduplicates discussions by post title + company across pages
• Optionally enriches posts with AI-extracted fields: problem_name, leetcode_url,
• Saves to CSV (per-company cache or monthly output)
• Exposes 4 tools over stdio MCP transport for use with Claude Desktop / Claude Code

Installation

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client.

Credentials and setup notes

Configuration is passed through the environment: ANTHROPIC_API_KEY. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.

• Python 3.12+ - ANTHROPIC_API_KEY env var (only for --enrich)

Worth knowing first

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.

Where it fits

Among the search and retrieval options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. It is maintained by louisfghbvc; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.