GitHub
GitHub’s official server lets AI read and manage code, issues and pull requests in your account. Use GitHub’s hosted version or run it locally with Docker.
Description from the maker (original English)
Read DeepWiki repository wikis and ask questions about public GitHub repos.
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
You need
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json
{
"mcpServers": {
"repowiki": {
"command": "npx",
"args": [
"-y",
"@reneturcios/repowiki",
"mcp"
]
}
}
}Run this in your terminal
claude mcp add repowiki -- npx -y @reneturcios/repowiki mcpPaste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"repowiki": {
"command": "npx",
"args": [
"-y",
"@reneturcios/repowiki",
"mcp"
]
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Paste into .vscode/mcp.json in your project
{
"servers": {
"repowiki": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@reneturcios/repowiki",
"mcp"
]
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.
Your choice stays on this device in a cookie; no account needed.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
Runs on your computer; the tool list appears in your AI app after you install it.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 6, 2026
The registry name was verified with the GitHub account CloudCorpRecords, which owns the repo
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Runs on your computer; we can only read tool lists from internet endpoints
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
The registry does not list a required key, though some servers ask you to sign in on first use.
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
The GitHub repo last changed –, and the latest version (0.1.0) reached the registry 6 days ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js, Docker on your computer.
In the same category: GitHub, Desktop Commander, Cloudflare MCP
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
GitHub’s official server lets AI read and manage code, issues and pull requests in your account. Use GitHub’s hosted version or run it locally with Docker.
MCP server for terminal commands, file operations, and process management
Cloudflare MCP servers
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
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.
npx @reneturcios/repowiki structure facebook/react
Or run the container image:
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.
# List the documentation topics for a repository
repowiki structure facebook/react
repowiki contents facebook/react
repowiki 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.
One bin serves both faces. The mcp subcommand starts a stdio MCP server:
npx -y @reneturcios/repowiki mcp
MCP client configuration:
{
"mcpServers": { "repowiki": { "command": "npx", "args": ["-y", "@reneturcios/repowiki", "mcp"] } } }
| Tool | Input | What it returns |
|---|---|---|
read_wiki_structure | repoName (string, required, owner/repo) | The list of documentation topics DeepWiki has for the repository. |
read_wiki_contents | repoName (string, required, owner/repo) | The full documentation text for the repository. |
ask_question | repoName (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.
npm install
npm 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
MIT — see LICENSE.