Data as of

Deepwiki MCP Server for Cursor: Setup & Config

Cursor: This unofficial server was designed to turn DeepWiki documentation into Markdown for MCP assistants.

What you can do with Deepwiki in Cursor

Evaluate its Markdown crawler design, but use the official alternative while scraping remains blocked.

  • Evaluate the documented design for turning repository documentation into Markdown.
  • Assess an existing installation before migrating to the official DeepWiki service.

Before you start: Deepwiki in Cursor

  • Node.js and npx
  • An MCP-compatible client

This is the README's Cursor launch configuration, not a remedy for blocked scraping. The README recommends the official DeepWiki MCP service because this implementation is currently nonfunctional.

Deepwiki Cursor configuration

  1. Choose Cursor configuration scope

    For Deepwiki MCP Server, open Project: .cursor/mcp.json User: ~/.cursor/mcp.json. Merge into mcpServers at project or user scope.

  2. Add Deepwiki MCP Server to Cursor

    Use the deepwiki-mcp entry below in mcpServers. Keep Deepwiki MCP Server's documented stdio connection fields and your other Cursor entries.

  3. Check Deepwiki MCP Server in Cursor

    Deepwiki MCP Server: Enable in Cursor’s MCP settings; inspect tools.

Config file · Project: .cursor/mcp.json

User: ~/.cursor/mcp.json

JSON
{
  "mcpServers": {
    "deepwiki-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-deepwiki@latest"
      ],
      "env": {
        "DEEPWIKI_MAX_CONCURRENCY": "<optional simultaneous request limit>",
        "DEEPWIKI_REQUEST_TIMEOUT": "<optional request timeout in milliseconds>",
        "DEEPWIKI_MAX_RETRIES": "<optional retry count>",
        "DEEPWIKI_RETRY_DELAY": "<optional retry-backoff base in milliseconds>"
      }
    }
  }
}

Deepwiki tools available to Cursor

Deepwiki's stored tool list documents 1 tool; compare it with Cursor's connected tool list, because the stored list is not a live check.

deepwiki_fetch

Find deepwiki_fetch under Deepwiki in Cursor's MCP settings; inspect its arguments when the agent requests a call.

Designed to crawl DeepWiki documentation and return combined Markdown or per-page records.

Deepwiki: full stored tool descriptions

Troubleshooting Deepwiki in Cursor

  • Cursor must find npx mcp-deepwiki@latest (Node.js/npm) for Deepwiki MCP Server. Enable the project/user entry in MCP settings and inspect its tools.
  • Review DEEPWIKI_MAX_CONCURRENCY, DEEPWIKI_MAX_RETRIES, DEEPWIKI_REQUEST_TIMEOUT, DEEPWIKI_RETRY_DELAY for Deepwiki MCP Server before sharing project .cursor/mcp.json; project scope travels with the repository.
  • Deepwiki MCP Server uses stdio here: Cursor must keep the configured process running; protocol output belongs on stdout and diagnostics on stderr.
  • Known limitation: The README reports the server currently does not work because scraping is blocked.
  • Known limitation: It is an unofficial integration.
  • Known limitation: Docker deployment is documented as untested.
  • General Cursor troubleshooting lives in the /clients/cursor guide.

Deepwiki MCP Server — details. Cursor guide

Frequently asked questions

Cursor's Deepwiki MCP Server entry belongs under mcpServers in .cursor/mcp.json (project) or ~/.cursor/mcp.json (user). Confirm the active scope in MCP settings.

Cursor's deepwiki-mcp example uses stdio.

Deepwiki MCP Server's Cursor configuration invokes npx mcp-deepwiki@latest (Node.js/npm).

Cursor's Deepwiki MCP Server example references DEEPWIKI_MAX_CONCURRENCY, DEEPWIKI_MAX_RETRIES, DEEPWIKI_REQUEST_TIMEOUT, DEEPWIKI_RETRY_DELAY. Check these names if startup or authentication fails; the example alone does not distinguish required from optional values.

Deepwiki MCP Server's stored list contains 1 tool, including deepwiki_fetch. Compare those names with Cursor's connected tool list; the stored list is not a live check.

Aggregate mode returns one Markdown document, while pages mode returns structured page entries.

The documented domain check permits only deepwiki.com URLs.