Log inSubmit server
Repowise logo

Repowise

by repowise-dev

Indexes code, history, tests, and decisions locally, then exposes repository intelligence through MCP tools.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install Repowise

Pick your client, then add it in one click or paste the config.

STDIOPython
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "repowise-dev-repowise": {
      "command": "uvx",
      "args": [
        "repowise"
      ]
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Install not yet sandbox-tested— we haven't run this command through our automated sandbox yet. Not a red flag; we're working through the catalog.

Overview

repowise-dev/repowise indexes a repository's code, Git history, tests, and architectural decisions into a local codebase intelligence index. Its MCP tools answer questions about dependencies, callers, change risk, code health, tests, dead code, documentation, and cross-repository service relationships. Run it locally without an API key, or use the hosted option when appropriate. Reach for it when an AI coding agent needs repository context without repeatedly searching and reopening files.

Use cases

  • Trace callers and tests before changing a shared file
  • Prioritize refactoring using code-health and defect history
  • Explore repository architecture through dependency and C4 views
  • Identify dead code and files affected by service-contract changes
  • Reduce test and Git output before sending it to an agent

Key features

  • Local repository index with no API key
  • MCP tools for codebase intelligence
  • Dependency, caller, and test-impact analysis
  • Code-health scores based on defect history
  • Generated documentation and architecture views
  • Cross-repository service and contract mapping

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked Today

Recent health check succeeded.

30/31 checks healthy over the last 78d

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 9d ago via OSV.dev · repowise (PyPI)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars7.9kStargazers on the source repository.
Last commitTodayMost recent push to the default branch.
Directory activity6 viewsConfig copies, upvotes, and views on AllMCPs.

How Repowise works

What repowise-dev/repowise does

repowise-dev/repowise builds an index of a repository and makes that index available to coding agents through MCP. The indexed material includes source code, Git history, tests, and architectural decisions. It supports codebase analysis across 28 languages and can also produce a generated wiki covering modules and files.

The resulting context is designed for questions that require relationships between files rather than the contents of one file. An agent can investigate what calls a changed symbol, which tests reach it, which related files may be missing from a change, and which areas have the highest defect or maintenance risk. The dashboard presents the same indexed information with architecture maps, C4 views, health scores, charts, and cited answers.

How it works

The normal flow is to install the Python package, initialize the repository, and start the service. Initialization creates the graph and analysis data locally without an API key. It can include Git information, code health, dead-code analysis, and documentation generation. Model-written documentation can be generated separately when needed.

repowise serve starts the dashboard and MCP server. An MCP-capable coding agent then queries the index instead of repeatedly grepping through the repository and opening files. The tool set is organized around repository tasks, including overview, dependency and caller analysis, change risk, tests, health, and architectural context.

Repowise also includes repowise distill, which reduces output from tests, installs, and Git commands while retaining error lines. Optional hooks can warn about fragile files and stale paths, and generated CLAUDE.md or AGENTS.md files can be kept aligned with the index.

Setup and configuration

Install the package with one of the supported Python tooling options:

bash
uv tool install repowise
# or: pipx install repowise
# or: pip install repowise

From the repository to analyze, initialize the index and start the service:

bash
repowise init --yes --no-prose
repowise serve

The --no-prose option initializes the graph and analysis layers without model-written prose. Run repowise generate later to add that documentation. The first serve run downloads the dashboard interface and requires Node.js 20 or newer. Initialization itself requires no API key. The setup flow can configure Claude Code for the repository; the service is also intended for other MCP-capable agents.

Tools and capabilities

  • Repository overview and indexed codebase questions
  • Dependency, caller, and architecture analysis
  • Change-risk analysis, including related files and affected tests
  • Per-file code-health scoring and prioritized remediation queues
  • Git-history analysis tied to defects and code risk
  • Dead-code detection and refactoring guidance
  • Generated repository and module documentation
  • Cross-repository service maps and contract impact checks
  • Dashboard answers with citations and charts
  • Command-output reduction through repowise distill

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Repowise

repowise-dev/repowise is an MCP server that connects coding agents to an indexed repository containing code, Git history, tests, and architectural decisions. Its tools provide repository overviews, dependency and caller analysis, change-risk and test impact, code-health findings, documentation, and related architecture context.

Install it with `uv tool install repowise`, `pipx install repowise`, or `pip install repowise`. In the target repository, run `repowise init --yes --no-prose`, then start the dashboard and MCP server with `repowise serve`.

No, repository indexing runs without an API key. The initialization command creates the graph, Git, health, dead-code, and documentation index locally; model-written prose can be generated later with `repowise generate`.

Yes, Cursor is listed among the supported MCP-capable agents. The server also names Claude Code and Codex, and its MCP interface is intended for any MCP-capable agent.

Node.js 20 or newer is required by `repowise serve`. The command starts the dashboard and MCP server and downloads the dashboard interface on its first run.

Related MCP servers

All in Version Control All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewRepowise AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/repowise-dev-repowise?style=directory)](https://allmcps.com/mcp/repowise-dev-repowise)
HTML Embed
<a href="https://allmcps.com/mcp/repowise-dev-repowise"><img src="https://allmcps.com/api/badge/repowise-dev-repowise?style=directory" alt="Repowise on AllMCPs" /></a>