Repowise

listing.by

Index a codebase once and give coding agents cited answers, change impact, git history, decisions and code-health data.

state.local.long (state.local.title)listing.badge.runs_with

listing.install

listing.local.explain

uvx repowise

listing.local.needs listing.local.note

listing.share.h

listing.share.p_local

mcp.tc/i/repowise

listing.about

Repowise indexes a repository's dependency graph, git history, tests, documentation and architectural decisions, then exposes the results to coding agents through MCP tools. Agents can ask who calls a function, what breaks if a file changes, which files are risky, and why code was written a certain way. It also reports code-health scores and dead code.

It runs locally over stdio from the PyPI package repowise (uvx or pip install repowise). Run repowise init in your repository, then repowise serve. Core analysis stays on your machine and needs no API key; model-written prose is optional. The project is AGPL-3.0, with a commercial license available.

listing.can

  • Get a cited overview of a repository with get_overview
  • Check symbol-level blast radius before changing a file
  • Surface hotspots, ownership and co-change from git history
  • Score code health and find defect-prone files
  • Detect dead code
  • Recover architectural decisions behind the code
  • Find which tests a diff exercises

listing.tools

listing.notools.local

listing.prompts

  • Use Repowise get_overview to summarize this repository

  • What breaks if I change src/auth.py?

  • Which files in this repo are the most defect-prone?

  • Find dead code in this project and suggest what to remove

listing.setup.h

listing.setup.local

Claude Code

  1. Run this in a terminal, in your project folder:
claude mcp add --transport stdio repowise -- uvx repowise
  1. Start Claude Code and type /mcp. repowise should show as connected.

Add --scope user to make it available in every project.

Claude Desktop

  1. Open Settings → Developer → Edit Config. It opens claude_desktop_config.json. Add:
claude_desktop_config.json
{
  "mcpServers": {
    "repowise": {
      "command": "uvx",
      "args": [
        "repowise"
      ]
    }
  }
}
  1. Save the file and restart Claude Desktop.

Needs uv (Python) on your computer. The file lives in ~/Library/Application Support/Claude/ on macOS and %APPDATA%\Claude\ on Windows.

Cursor

Or add it by hand to ~/.cursor/mcp.json (all projects) or .cursor/mcp.json (this project):

mcp.json
{
  "mcpServers": {
    "repowise": {
      "command": "uvx",
      "args": [
        "repowise"
      ]
    }
  }
}

Needs uv (Python) on your computer.

VS Code

Or from a terminal:

code --add-mcp '{"name":"repowise","type":"stdio","command":"uvx","args":["repowise"]}'

Or commit it to the repo in .vscode/mcp.json:

.vscode/mcp.json
{
  "servers": {
    "repowise": {
      "type": "stdio",
      "command": "uvx",
      "args": [
        "repowise"
      ]
    }
  }
}

Needs uv (Python) on your computer.

Devin Desktop

  1. Add it to ~/.config/devin/mcp_config.json (macOS and Linux) or %APPDATA%\devin\mcp_config.json (Windows):
mcp_config.json
{
  "mcpServers": {
    "repowise": {
      "command": "uvx",
      "args": [
        "repowise"
      ]
    }
  }
}
  1. Refresh the MCP server list in Cascade.

Devin Desktop is the new name for Windsurf.

Codex

codex mcp add repowise -- uvx repowise

Or edit ~/.codex/config.toml directly:

config.toml
[mcp_servers.repowise]
command = "uvx"
args = ["repowise"]

Needs uv (Python) on your computer.

Gemini CLI

gemini mcp add repowise uvx repowise

This adds it to the current project. Add -s user to use it everywhere.

Any client

Most clients that start local servers accept this shape:

{
  "mcpServers": {
    "repowise": {
      "command": "uvx",
      "args": [
        "repowise"
      ]
    }
  }
}

Zed puts servers under context_servers in its settings, with the same command, args and env fields.

Needs uv (Python) on your computer.

listing.faq

Can I paste mcp.tc/i/repowise into my MCP client?

No. Repowise runs on your own computer, started by your client, so it has no web address to connect to. The quick link is the page to share; the install command is uvx repowise.

Does Repowise need an API key?

No. It doesn't declare any keys or environment variables. It runs with your user account's permissions, so check what its tools can reach.

Is Repowise a remote or a local server?

Local. Your client starts it as a process on your computer with uvx repowise, which needs uv (Python).

What can Repowise do?

You can get a cited overview of a repository with get_overview, check symbol-level blast radius before changing a file and surface hotspots, ownership and co-change from git history.

Which clients can use it?

Any client that starts local servers: Claude Code, Claude Desktop, Cursor, VS Code, Devin Desktop, Codex, Gemini CLI, Zed and others. claude.ai and ChatGPT only connect to remote servers.

Who wrote this page?

mcp.tc's robot read Repowise's public metadata (its package and repository pages), and an AI model drafted the text from it. A person reviews anything the checks can't confirm. The text can still be wrong, so if you spot a mistake, use Report this listing on this page.

listing.em.h

listing.em.lead_local listing.em.how

listing.em.badge

em.prev_lightem.prev_dark
Markdown
[![Repowise on mcp.tc](https://mcp.tc/i/repowise/badge.svg)](https://mcp.tc/i/repowise)
HTML
<a href="https://mcp.tc/i/repowise"><img src="https://mcp.tc/i/repowise/badge.svg" alt="Repowise on mcp.tc" height="20"></a>

listing.em.badge_note

listing.em.widget

HTML
<script src="https://mcp.tc/w/repowise.js" async></script>

listing.em.widget_note

iframe

HTML
<iframe src="https://mcp.tc/embed/repowise" title="Repowise on mcp.tc" width="420" height="200" loading="lazy" allow="clipboard-write" style="border:0;border-radius:8px;max-width:100%"></iframe>

listing.em.iframe_note

JSON

listing.em.json_local

https://mcp.tc/i/repowise.json

listing.em.fields

listing.disclaimer_checked