Deepwiki MCP Server for VS Code: Setup & Config

What you can do with Deepwiki in VS Code

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

• Inspect the intended aggregate versus per-page documentation outputs.
• Assess an existing installation before migrating to the official DeepWiki service.

Before you start: Deepwiki in VS Code

• 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 VS Code configuration

1. Choose VS Code configuration scope

   For Deepwiki MCP Server, open Workspace: .vscode/mcp.json. Merge into servers; preserve existing inputs.

2. Add Deepwiki MCP Server to VS Code

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

3. Check Deepwiki MCP Server in VS Code

   Deepwiki MCP Server: Start in VS Code’s MCP controls; inspect output and trust prompts.

{
  "servers": {
    "deepwiki-mcp": {
      "type": "stdio",
      "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 VS Code

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

deepwiki_fetch

Look for deepwiki_fetch among VS Code's agent-mode tools after starting Deepwiki through the MCP controls.

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

Deepwiki: full stored tool descriptions

Troubleshooting Deepwiki in VS Code

• Make npx mcp-deepwiki@latest (Node.js/npm) available in the workspace, container, or remote environment hosting Deepwiki MCP Server. Start through VS Code's MCP controls; inspect output and trust prompts.
• For Deepwiki MCP Server, keep DEEPWIKI_MAX_CONCURRENCY, DEEPWIKI_MAX_RETRIES, DEEPWIKI_REQUEST_TIMEOUT, DEEPWIKI_RETRY_DELAY out of version control; VS Code documents input variables and secret handling.
• Deepwiki MCP Server uses stdio here: VS Code 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 VS Code troubleshooting lives in the /clients/vscode guide.

Frequently asked questions