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)
Codebase intelligence for AI coding agents — graph, git history, docs, decisions, code health.
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": {
"repowise": {
"command": "uvx",
"args": [
"repowise",
"mcp",
"--transport",
"stdio"
]
}
}
}Run this in your terminal
claude mcp add repowise -- uvx repowise mcp --transport stdioPaste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"repowise": {
"command": "uvx",
"args": [
"repowise",
"mcp",
"--transport",
"stdio"
]
}
}
}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": {
"repowise": {
"type": "stdio",
"command": "uvx",
"args": [
"repowise",
"mcp",
"--transport",
"stdio"
]
}
}
}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 against the domain repowise.dev (the registry checks domain ownership)
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.60.1) reached the registry 4 days ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Python (uv) 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.
English | 简体中文
Stop paying your agent to re-read your codebase.
Repowise indexes your code, git history, tests and decisions once, on your machine.
Your coding agent asks the index instead of grepping and opening files, so it does about half the work.
You get the same answers in a dashboard: what calls this, what breaks, what to fix first, and why.
Half the tool calls your agent opens 3 files where it opened 7 · 31.6% less output Up to 99% less noise from test runs, installs and git output · every error line kept 88% of the right files found in one call · next best tool: 61%
Graph, risk, health, tests and dead code make zero LLM calls · no API key to index · 28 languages · Claude Code, Codex, Cursor and any MCP host · free and open source
Quickstart · For your agent · What it does · Hosted · Benchmarks · Teams · Docs
Open Claude Code, Codex, Cursor or any MCP-capable agent in your repository and paste:
Read https://docs.repowise.dev/setup.md and set up Repowise in this repository.
The agent installs Repowise, indexes the repo with no API key, connects itself to the index, and asks you before anything costs money. To do it by hand:
uv tool install repowise # or: pipx install repowise / pip install repowise
cd /path/to/your/repo repowise init --yes --no-prose # graph, git, health, dead code, docs. No key, no spend.
repowise serve # dashboard + MCP server (needs Node 20+; first run downloads the UI)
serve opens the dashboard in your browser. After a first index it starts with a short guided tour, and Setup is where you connect agents, turn on sync and add coverage or a model.
Restart Claude Code or run /mcp, then ask *"What breaks if I change src/auth.py?"* or *"Use Repowise get_overview to summarize this repository."* init wires Claude Code for this repo and adds the global repowise MCP entry when there is none; it never moves one that serves another repo. Full setup for every agent →
Without an index, an agent rediscovers your codebase on every task: grep, open a file, open three more, grep again. Repowise answers those questions ahead of time, so the agent asks once and gets on with the work.
In a measured run on django/django, an agent with Repowise made 3.8 tool calls instead of 7.2, opened 3.0 files instead of 7.2 and wrote 31.6% less, with answers just as good. That is the largest saving of the five context tools we tested. On a small local model the output cut reaches 47.9%. How it was measured →
repowise distill trims test, install and git output before the agent reads it and keeps every error line. Distill →CLAUDE.md and AGENTS.md current from the index.repowise saved and the dashboard's Usage and savings page count the tokens your agent no longer has to read.One index of your code, its history and its decisions, used three ways: to understand the code, to change it safely, and to keep improving it.
See how it fits together A call graph across 28 languages, an architecture map you can explore, C4 views, and a generated wiki for every module and file.
The graph · Docs
Know what breaks Every caller of what you changed, the files that usually change with it but are missing from your diff, and the tests that reach it.
Change risk · Tests
Fix what matters A 1 to 10 health score for every file, validated against real bug history, a ranked fix-first queue, refactoring plans and dead code.
Code health · Refactoring
Follow it across repos Services and the HTTP, gRPC and event contracts between them, with a guard for breaking changes and the consumer files they affect.
Workspaces
Ask it anything Cited answers and charts from the dashboard, or the same answers through MCP for your agent.
Dashboard · MCP tools
Remember why Decisions mined from ADRs, comments, commits, PRs and agent sessions, each tied to the code it governs, plus docs checked against the code.
Decisions · Doc drift
Every question it answers
| You ask | Repowise gives you |
|---|---|
| *How does checkout work in this repo?* | A cited answer built from the call graph and the generated docs, in one call. Search and answers |
| *What calls this function, and what does it call?* | A call graph across 28 parsed languages, every edge stamped with how it was resolved and how far to trust it, plus traced execution flows from each entry point. The graph |
| *Can I get docs for this codebase?* | A wiki for every module and file, rendered from the code's structure with no key, or written by a model when you choose. It updates incrementally after each commit. Docs |
| *Which of our docs are wrong?* | Markdown checked against the tree: every reference to a file or symbol the code no longer has, with the line to edit. Doc drift |
| *Why is it built this way?* | Decisions mined from ADRs, # WHY: comments, commit and PR history and your agent sessions, each tied to the code it governs and flagged when it goes stale. Decisions |
| *Who knows this code?* | Owners, bus factor, fading ownership when the main author goes quiet, and suggested reviewers. Ownership |
| *Can I see the architecture?* | An explorable dependency map, C4 views, and a Structurizr export, no model involved. Dashboard |
| You ask | Repowise gives you |
|---|---|
| *What breaks if I change this?* | Symbol-level blast radius: the callers of what you changed, the files that historically change with it but are missing from your diff, and the tests that reach it. Change risk |
| *How risky is this PR?* | Where the change ranks against your repository's own recent commits, with the reasons, as a directive your agent can act on. Change risk |
| *Which tests should run?* | The tests a diff actually exercises, from a coverage report if you have one and from the call graph if you do not. Test intelligence |
| *Did this PR add untested lines?* | Patch coverage, branch coverage on changed lines and path-scoped gates in CI, on GitHub, GitLab or any runner. CI gates |
| *Will this API change break another r
Only the beginning is shown; read the rest in the repo