Repowise
A local codebase index with ten MCP tools: dependency graph, git history, code health and architectural decisions without re-grepping on every step
Medium risk
We rate an entry medium when the tool runs code, makes network calls or reads project files. Check what exactly it does before installing.
Why this level
- Reads the entire source code and git history of the repository to build the index
- By default can make one model call when capturing decisions from session transcripts
Install
In your terminal, with SkillFoxx CLI
npx skillfoxx add mcp/repowiseDetects the agents on your machine, checks the risk and pins the version.
Other ways to install
Run in a terminal
claude mcp add --transport stdio repowise -- uvx repowise==0.53.0 mcp --transport stdioOr add to the file .mcp.json, in the project
{
"mcpServers": {
"repowise": {
"command": "uvx",
"args": [
"repowise==0.53.0",
"mcp",
"--transport",
"stdio"
]
}
}
}If the file already exists, add the server inside the mcpServers key.
The button opens the agent and offers to add the server. If nothing happens, copy the config below.
Add to the file ~/.cursor/mcp.json, for all projects
{
"mcpServers": {
"repowise": {
"command": "uvx",
"args": [
"repowise==0.53.0",
"mcp",
"--transport",
"stdio"
]
}
}
}If the file already exists, add the server inside the mcpServers key. For a single project, put the same block into .cursor/mcp.json.
The button opens the agent and offers to add the server. If nothing happens, copy the config below.
Run in a terminal
code --add-mcp '{"name":"repowise","type":"stdio","command":"uvx","args":["repowise==0.53.0","mcp","--transport","stdio"]}'Or add to the file .vscode/mcp.json, in the project
{
"servers": {
"repowise": {
"type": "stdio",
"command": "uvx",
"args": [
"repowise==0.53.0",
"mcp",
"--transport",
"stdio"
]
}
}
}If the file already exists, add the server inside the servers key.
Run in a terminal
codex mcp add repowise -- uvx repowise==0.53.0 mcp --transport stdioOr add to the file ~/.codex/config.toml, for all projects
[mcp_servers.repowise]
command = "uvx"
args = ["repowise==0.53.0", "mcp", "--transport", "stdio"]If the file already exists, append the block to the end.
Add to the file ~/.gemini/settings.json, for all projects
{
"mcpServers": {
"repowise": {
"command": "uvx",
"args": [
"repowise==0.53.0",
"mcp",
"--transport",
"stdio"
]
}
}
}If the file already exists, add the server inside the mcpServers key.
Add to the file ~/.config/devin/mcp_config.json, for all projects
{
"mcpServers": {
"repowise": {
"command": "uvx",
"args": [
"repowise==0.53.0",
"mcp",
"--transport",
"stdio"
]
}
}
}If the file already exists, add the server inside the mcpServers key. Legacy Cascade keeps the MCP config in ~/.codeium/windsurf/mcp_config.json.
Formerly Windsurf.
Add to the file cline_mcp_settings.json, for all projects
{
"mcpServers": {
"repowise": {
"command": "uvx",
"args": [
"repowise==0.53.0",
"mcp",
"--transport",
"stdio"
]
}
}
}If the file already exists, add the server inside the mcpServers key. Open the settings file in Cline: MCP Servers tab, Configure MCP Servers.
Add to the file .roo/mcp.json, in the project
{
"mcpServers": {
"repowise": {
"command": "uvx",
"args": [
"repowise==0.53.0",
"mcp",
"--transport",
"stdio"
]
}
}
}If the file already exists, add the server inside the mcpServers key.
A fork of Roo Code, same .roo folders.
Add to the file opencode.json, in the project
{
"mcp": {
"repowise": {
"type": "local",
"command": [
"uvx",
"repowise==0.53.0",
"mcp",
"--transport",
"stdio"
]
}
}
}If the file already exists, add the server inside the mcp key.
Add to the file ~/.config/zed/settings.json, for all projects
{
"context_servers": {
"repowise": {
"command": "uvx",
"args": [
"repowise==0.53.0",
"mcp",
"--transport",
"stdio"
]
}
}
}If the file already exists, add the server inside the context_servers key.
Add to the file .codeassistant/mcp.json, in the project
{
"mcpServers": {
"repowise": {
"command": "uvx",
"args": [
"repowise==0.53.0",
"mcp",
"--transport",
"stdio"
]
}
}
}If the file already exists, add the server inside the mcpServers key.
Install and run Repowise in the project root: pip install repowise, then repowise init --no-prose -y and repowise serve. init wires up Claude Code automatically, other MCP hosts are covered in docs/start/QUICKSTART.md.
Other ways from the author
pip install repowise
cd /path/to/your/repo
repowise init --no-prose -y
repowise serveBuilds the index locally and starts the MCP server, init wires up Claude Code automatically.
This is third-party code. Review the repository files before installing.
What it does
Repowise builds a local repository index once: a file and symbol dependency graph across 26 languages, git history with hotspots and co-change data, a per-module wiki, architectural decisions mined from commit history, and 51 deterministic code-quality detectors. On top of that index it exposes ten MCP tools that hand the agent a ready answer instead of a chain of grep and read calls: who calls a function, what breaks if it changes, which tests to run for a given diff. The repowise distill command compresses the output of commands like pytest or git log, keeping the errors and cutting the noise, with a way to expand the original output back.
Who it is for. For developers who want the agent to already understand the repository's structure and history instead of rebuilding context on every task.
Good fit when
- The agent burns many calls figuring out who calls a function or what breaks when a file changes
- You need to quickly know which tests a given diff actually touches
- Command output like pytest or git log fills the context with noise
Not a fit when
- The repository is small enough that the agent already navigates it quickly
- You need a managed multi-tenant cloud service rather than a local self-hosted index
Example request
Use Repowise get_overview to summarize this repository, and show me what breaks if I change src/auth.pyLimitations
The core analysis needs no model key, but capturing decisions from session transcripts makes one batched model call by default, turned off with --no-llm. Multi-repository workspaces need extra setup. The project is AGPL-3.0, a separate license is needed for commercial use without disclosing source.
How to disable. Remove the package with pip uninstall repowise and stop the local server, the MCP connection comes out with claude mcp remove repowise.
MCP
- Transport
- stdio
- Authentication
- not required
Security check
- Reads the entire source code and git history of the repository to build the index
- By default can make one model call when capturing decisions from session transcripts
README in short
The README presents Repowise as an index of code, git history, tests, docs and decisions built once and then queried by agents and developers with cited sources. It cites measurements on django/django: fewer tool calls and fewer tokens for the same question compared to running without the index. It covers ten MCP tools, generating CLAUDE.md and AGENTS.md from the index, hooks that push context in at the right moment, and the distill command for compressing noisy command output. Install is via pip, self-hosted, AGPL-3.0 or commercial license.
FAQ
Do I need a model key to run it?
No, the graph, git analysis, code health, tests and dead-code detection run without calling a model, generated prose is optional.
Where do session transcripts go?
Nowhere off the machine, processing happens locally, and --no-llm removes the one model call in that process entirely.
Related
A skills library that gives coding agents a development process: brainstorming, planning, TDD, subagents and code review
Skills for real engineers by Matt Pocock
Skills For Real Engineers
Small composable skills for engineering with agents: plan grilling, TDD, bug diagnosis, code review and architecture
GitHub toolkit for spec-driven development: the specify CLI adds agent commands and skills to a project, from principles to implementation
Reference MCP servers
Model Context Protocol servers
Official reference MCP servers: Filesystem, Fetch, Git, Memory, Sequential Thinking, Time and Everything