Repowiki

io.github.CloudCorpRecordsPublished by GitHub account CloudCorpRecordsv0.1.0Updated Nov 3, 2026

Read DeepWiki repository wikis and ask questions about public GitHub repos.

VerifiedSTDIODesktop onlyKnowledge & MemoryDeveloper Tools

Overview

AI-generated overview

Local stdio MCP server that reads DeepWiki documentation wikis for public GitHub repositories and answers questions about their code.

What you can do
  • List the documentation topics DeepWiki has written for a repository
  • Read the full documentation text for a repository
  • Ask a plain-language question about a repository and get an answer grounded in DeepWiki's index of its code and docs
When to use it
Useful when you want an assistant to explain or onboard onto a public GitHub project without cloning it: browsing its generated wiki, pulling the full docs, or asking targeted questions about how the codebase works.
Requirements
Runs locally over stdio via npx (npm package) or the published container image. Needs network access to DeepWiki's hosted service. No account, API key, or environment variables are required. Repository names must be given as owner/repo.
Before you install
Each call is forwarded to DeepWiki's hosted service, so the repository name and your question leave your machine. Only public repositories are supported; private ones are out of scope. Answers are generated by DeepWiki's own models and may be inaccurate.

Installation

In SourceWeft

  1. Open Repowiki in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

repowiki

repowiki gives a command line and a local MCP server for DeepWiki, the service that writes documentation wikis for public GitHub repositories. Point it at a repository in owner/repo form and it can list the topics DeepWiki has written for that project, hand back the full documentation text, or answer a plain-language question about the codebase using DeepWiki's own index and models.

The answers come from DeepWiki's public hosted service, which is free and needs no account or API key. repowiki is the local half: it speaks the documented protocol to that service and presents the same three tools over stdio, so any MCP client can use them without a remote transport setup.

Install

bash
npx @reneturcios/repowiki structure facebook/react

Or run the container image:

bash
docker run -i ghcr.io/cloudcorprecords/repowiki

The container defaults to the MCP server (see below). Pass CLI arguments to use it as a CLI instead.

CLI

bash
# List the documentation topics for a repositoryrepowiki structure facebook/react
# Print the full documentation textrepowiki contents facebook/react
# Ask a question about the repositoryrepowiki ask facebook/react "How is state managed?"
repowiki --version

Exit codes: 0 on success, 1 when the upstream service reports an error or cannot be reached, 2 for usage errors. Repository names must be in owner/repo form; anything else is rejected before a request is made.

MCP server

One bin serves both faces. The mcp subcommand starts a stdio MCP server:

bash
npx -y @reneturcios/repowiki mcp

MCP client configuration:

json
{  "mcpServers": {    "repowiki": {      "command": "npx",      "args": ["-y", "@reneturcios/repowiki", "mcp"]    }  }}

Tools

ToolInputWhat it returns
read_wiki_structurerepoName (string, required, owner/repo)The list of documentation topics DeepWiki has for the repository.
read_wiki_contentsrepoName (string, required, owner/repo)The full documentation text for the repository.
ask_questionrepoName (string, required), question (string, required)An answer about the repository, grounded in DeepWiki's index of its code and documentation.

Behind the scenes each call is forwarded to DeepWiki's hosted MCP endpoint (https://mcp.deepwiki.com/mcp) as a JSON-RPC tools/call request; responses arrive as plain JSON or as a Server-Sent Events stream and are reduced to their result text. No credentials are sent: the public service requires none. Private repositories are out of scope, matching the upstream's public-only access.

Development

bash
npm installnpm run build   # tsc -> dist/npm test        # node test runner over test/*.test.ts, no network (fake fetch fixtures)npm run dev     # run the CLI from source via tsx

License

MIT — see LICENSE.

Source: README.md at commit cc7e74c

Tools

3

read_wiki_structure

Get a list of documentation topics for a GitHub repository.

ParametersrepoNamerequired

read_wiki_contents

View documentation about a GitHub repository.

ParametersrepoNamerequired

ask_question

Ask any question about a GitHub repository and get an AI-powered, context-grounded response.

ParametersquestionrequiredrepoNamerequired

Version history

1
  1. v0.1.0LatestOct 31, 2026

Score

90% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts
  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts