← Back to Discover

Repowise

Open-source codebase intelligence tool that indexes a repository's code, call graph, git history and docs on your machine, then answers impact, risk and health questions for developers and coding agents via MCP.

MCP serversCode reviewCommand-line tools
Visit website ↗

What it does

Repowise indexes a codebase once, locally, and builds a dependency and call graph across 27 parsed languages, along with git history signals, generated documentation and architectural decisions. Developers and coding agents can then ask what calls a function, what breaks if a file changes, what is dead code, and why something was built a certain way. It gives Claude Code, Codex, Cursor, VS Code and other MCP hosts ten task-shaped MCP tools, plus a CLI and a local web dashboard started with repowise serve. Change risk, health scores from 53 deterministic detectors, test impact and dead code detection make no LLM calls; model-written docs are an optional upgrade. Checks can run in CI through a GitHub Action, a GitLab template or plain CLI commands, with SARIF output. The site also describes a hosted version at repowise.dev and a commercial layer for organisation-wide use.

Capabilities

  • Call graph and dependency map across 27 parsed languages
  • Change risk, blast radius and tests-to-run for a diff
  • File health scores and ranked refactoring plans from 53 deterministic detectors
  • Generated docs, decision mining and doc-drift checks
  • Ten MCP tools for coding agents, plus a CLI and local dashboard
  • CI gates with SARIF output

When to use it

  • You want a coding agent to query a pre-built index instead of rediscovering the repository each task
  • You need to estimate what a change or pull request could break and which tests to run
  • You want to decide which files to refactor or delete first
  • You want change and coverage gates running in CI

Alternatives to explore

  • CodeScene