Problem
The official DeepWiki MCP tools accept a repository name but no branch, tag, or commit. This makes version-specific documentation questions unreliable because the model can only use the currently indexed repository state.
Current tool inputs:
read_wiki_structure(repoName)read_wiki_contents(repoName)ask_question(repoName, question)
Asking for a historical version in natural language does not solve this. In testing, ask_question mixed current Next.js APIs into an answer explicitly scoped to Next.js 13.5.11.
Proposed solution
Add an optional revision parameter to all repository tools, for example:
{
"repoName": "vercel/next.js",
"revision": "v13.5.11",
"question": "When are GET Route Handlers cached?"
}The revision could accept a branch, tag, or commit SHA. Responses should report the resolved commit so clients can verify which source was used.
If a revision is not indexed or cannot be retrieved, the tool should return an explicit unsupported-revision error rather than silently answering from the default branch.
Why this matters
Library APIs and defaults change across releases. A current-branch answer presented as historical guidance can produce incorrect migrations and application behavior. Exact revision selection would make DeepWiki useful for maintenance work, migrations, and reproducible technical research.
Problem
The official DeepWiki MCP tools accept a repository name but no branch, tag, or commit. This makes version-specific documentation questions unreliable because the model can only use the currently indexed repository state.
Current tool inputs:
read_wiki_structure(repoName)read_wiki_contents(repoName)ask_question(repoName, question)Asking for a historical version in natural language does not solve this. In testing,
ask_questionmixed current Next.js APIs into an answer explicitly scoped to Next.js 13.5.11.Proposed solution
Add an optional revision parameter to all repository tools, for example:
{ "repoName": "vercel/next.js", "revision": "v13.5.11", "question": "When are GET Route Handlers cached?" }The revision could accept a branch, tag, or commit SHA. Responses should report the resolved commit so clients can verify which source was used.
If a revision is not indexed or cannot be retrieved, the tool should return an explicit unsupported-revision error rather than silently answering from the default branch.
Why this matters
Library APIs and defaults change across releases. A current-branch answer presented as historical guidance can produce incorrect migrations and application behavior. Exact revision selection would make DeepWiki useful for maintenance work, migrations, and reproducible technical research.