DeepWiki MCP
OfficialCognition's official remote MCP: AI-grounded docs and Q&A for any public GitHub repo — free, no auth.
Add to your client
Copy the config for your MCP client and paste it into its config file.
npx -y mcp-remote https://mcp.deepwiki.com/mcpPaste into ~/Library/Application Support/Claude/claude_desktop_config.json
{
"mcpServers": {
"deepwiki-mcp": {
"command": "npx",
"args": [
"-y",
"mcp-remote",
"https://mcp.deepwiki.com/mcp"
]
}
}
}Claude Desktop connects to remote servers through the `mcp-remote` proxy (installed on first run via npx). Restart Claude Desktop after saving.
Step-by-step guides: Add to Claude Desktop · Add to Cursor · Add to Windsurf
Before you start
- An MCP client that supports remote servers (Cursor/Windsurf natively; Claude Desktop via the mcp-remote bridge)
- Nothing else — no account, no API key
About DeepWiki MCP
DeepWiki MCP is Cognition's hosted, official MCP endpoint for DeepWiki — the service that auto-generates architecture docs, diagrams and Q&A over public GitHub repositories (it indexes tens of thousands of popular repos). Add one URL and your agent can pull a repo's doc structure, read the generated pages, and ask grounded questions, which in practice kills a whole class of hallucinated-API answers.
It is free and unauthenticated: the endpoint is https://mcp.deepwiki.com/mcp over streamable HTTP (the legacy /sse path has been retired and now returns 410, so update older configs). Because it's remote, there is nothing to install or keep updated locally — but your queries do transit Cognition's service, and coverage is public-repo only.
History note for anyone who used the npm package mcp-deepwiki (regenrek/deepwiki-mcp): that community server scraped deepwiki.com and stopped working when DeepWiki blocked scraping. The repo itself now recommends the official endpoint above. If a tutorial tells you to npx mcp-deepwiki, substitute the hosted URL.
Where it fits vs alternatives: Context7 injects version-specific API docs, GitMCP turns a single repo into a doc server, and DeepWiki answers free-form questions across any public repo. They stack well — DeepWiki for understanding, Context7 for exact API signatures.
Tools & capabilities (3)
read_wiki_structureList the documentation topics DeepWiki generated for a GitHub repository.
read_wiki_contentsRead the generated documentation for a repository.
ask_questionAsk a free-form question about a repository and get an AI answer grounded in its docs and code.
When to use it
- Let a coding agent understand an unfamiliar dependency before using it
- Answer 'how does this library handle X?' with repo-grounded context instead of hallucination
- Explore a large codebase's architecture without cloning it
Quick setup
- 1Cursor / Windsurf: add the server with url https://mcp.deepwiki.com/mcp — no token needed
- 2Claude Desktop: use the mcp-remote bridge — command npx, args ['-y','mcp-remote','https://mcp.deepwiki.com/mcp']
- 3Restart the client and ask something like: 'Using DeepWiki, how does vercel/next.js implement ISR?'
Security notes
Hosted by Cognition; queries you send (repo names, questions) go to their service. It only covers public repositories, so there's no way to leak private code through it — but don't paste secrets into questions. No account or key means nothing to revoke or rotate.
DeepWiki MCP FAQ
Is the DeepWiki MCP server free?
Yes — the official endpoint (https://mcp.deepwiki.com/mcp) is free and needs no account or API key. You just add the URL to your client. It only works with public GitHub repositories.
Why did my mcp-deepwiki npx setup stop working?
The community package scraped deepwiki.com, and DeepWiki blocked scraping — the package is defunct and its own README says so. Switch to the official hosted endpoint: https://mcp.deepwiki.com/mcp (use mcp-remote to bridge it into Claude Desktop).
Does DeepWiki MCP work with private repos?
No. It covers the public repositories DeepWiki has indexed. For private-repo context you'd run a local server (filesystem/git) or Devin's own tooling instead.
Should I use the /sse or /mcp endpoint?
/mcp — it's the current streamable-HTTP endpoint. The old /sse path has been retired (returns HTTP 410), so configs written for it need updating.
Alternatives to DeepWiki MCP
Compare all alternatives →Microsoft's official browser-automation MCP using Playwright's accessibility tree (no vision model).
Up-to-date, version-specific library documentation injected into your coding agent.
Pack any local or remote repository into one AI-ready file your agent can grep and read incrementally.
Compare DeepWiki MCP with: