DeepWiki MCP: ask any public GitHub repo a question

What DeepWiki and its MCP server actually are

DeepWiki, from Cognition, the company behind Devin, indexes public GitHub repositories and generates structured wiki-style documentation for them: an architecture overview, per-subsystem pages, diagrams, and a question-answering layer over the whole thing. The web version has a well-known shortcut, which is to take any GitHub URL and swap the domain.

https://github.com/openai/codex
https://deepwiki.com/openai/codex

The MCP server, announced by Cognition on 22 May 2025, is that same index exposed to an agent. Instead of you reading a generated wiki, your coding agent queries it mid-task: what does this library call its plugin interface, where does authentication live in this codebase, does this framework support the thing I am about to assume it supports.

The three tools it exposes

The right mental model for ask_question is a knowledgeable contributor rather than a search index. Asking "how do I configure retries" gets you an explanation with references. Asking "show me line 400 of client.go" is a question for the repository, not for DeepWiki, and you should clone it instead.

Use deepwiki to explain how tokio schedules tasks across worker threads.

Ask deepwiki whether pydantic v2 still supports the __get_validators__ hook,
and what replaced it if not.

Before you write the adapter: read the deepwiki structure for
openai/codex and tell me where MCP servers are registered.

Setting it up in Claude Code

claude mcp add -s user -t http deepwiki https://mcp.deepwiki.com/mcp

# confirm it connected
claude mcp list

Use --scope user, spelled -s user above, so it follows you between repositories. This is a personal research tool rather than a team dependency, and there is no credential to share, so committing it to .mcp.json buys nothing.

{
  "mcpServers": {
    "deepwiki": {
      "type": "http",
      "url": "https://mcp.deepwiki.com/mcp"
    }
  }
}

Setting it up in Cursor and Codex

Cursor

{
  "mcpServers": {
    "deepwiki": {
      "url": "https://mcp.deepwiki.com/mcp",
      "type": "http"
    }
  }
}

Codex

codex mcp add deepwiki --url https://mcp.deepwiki.com/mcp

codex mcp list

[mcp_servers.deepwiki]
url = "https://mcp.deepwiki.com/mcp"

Free, paid, and private repositories

The free public tier is unusually generous for a hosted service and there is no key to rotate, which is most of why this server is easy to recommend. Private repository support is the commercial hook: it needs a Devin account with GitHub connected, and at that point you are evaluating Devin rather than evaluating an MCP server.

Rough edges worth knowing before you rely on it

Nothing here is a dealbreaker, and all of it is easier to recognise than to debug from scratch.

The vendor publishes no rate limits for the free endpoint, which is a statement about the documentation rather than a promise. Treat it the way you would treat any free unauthenticated public service: fine for interactive research, not something to put in the hot path of a build. A repository that matters to you every day is also a repository worth cloning, where the source is authoritative and the read costs nothing.

When DeepWiki is the right tool, and when it is not

The honest limitation is structural rather than a bug. DeepWiki answers from a generated wiki built at index time, not from the repository at HEAD. For architecture, intent, and how subsystems relate, that is fine and often better than the source, because someone has already done the summarising. For "what is the current signature of this function", it is exactly the wrong shape of answer, delivered confidently.

Questions people ask

Keep reading

Continue through MCP for Claude Code with MCP gateway: one endpoint in front of every MCP server.