Repowise MCP Server: Setup for Claude Code, Cursor and Codex

• Summarizes the architecture of your repo

  Returns an architecture summary, module map, entry points and git health. The README says to call it first on an unfamiliar codebase.

  Try: “Use Repowise get_overview to summarize this repository.”

  Read · get_overview

• Answers a question about the code with sources

  Searches code and docs, expands through the dependency graph and returns one cited answer with a confidence score.

  Try: “How does login work in this repo?”

  Read · get_answer

• Gives a quick card for files, modules or symbols

  Returns a summary, signatures, hotspot flag and governing decisions for several targets at once. You can ask for callers, callees, owners and metrics too.

  Try: “Give me context on src/auth.py and src/session.py.”

  Read · get_context

• Shows the source of one function or class

  Returns one indexed symbol's source with exact line bounds.

  Try: “Show me the source of auth.py::verify_token.”

  Read · get_symbol

• Searches code and docs by symbol, path or idea

  Runs a hybrid search over code and documentation.

  Try: “Find where we handle rate limiting.”

  Read · search_codebase

• Shows how risky a file or change is

  Returns hotspots, dependents, co-change partners, owners, test gaps and bug history. Pass changed files to review a pull request.

  Try: “What breaks if I change src/auth.py?”

  Read · get_risk

• Scores what a commit or diff made worse

  Compares a commit, range or uncommitted change on defect risk, maintainability and performance, and lists the tests that touch it.

  Try: “How risky is my uncommitted change?”

  Read · get_change_risk

• Explains why the code is the way it is

  Returns architectural decisions with their evidence, and falls back to git history when no decision is recorded.

  Try: “Why do we use a queue between the API and the worker?”

  Read · get_why

• Lists code nobody uses

  Returns unreachable code by confidence tier.

  Try: “What dead code can I safely delete?”

  Read · get_dead_code

• Shows code health scores and what to fix first

  Returns health scores and findings, coverage, trends, doc drift and refactoring plans.

  Try: “What should I fix first in this repo?”

  Read · get_health

• Finds how two files are connected (opt-in)

  Finds the shortest dependency path between two files or modules. Turn it on with the tools option.

  Try: “How is billing.py connected to auth.py?”

  Read · get_dependency_path

• Traces what runs from an entry point (opt-in)

  Shows the top entry points with a call trace from each. Turn it on with the tools option.

  Try: “What runs when the CLI starts?”

  Read · get_execution_flows

• Drafts a code diff for a refactoring plan (opt-in)

  Turns one refactoring plan into code and a unified diff. It calls your own language model. Turn it on with the tools option.

  Try: “Draft the diff for the first refactoring plan.”

  Network · generate_refactoring_code

• Records a verdict on a refactoring plan (opt-in)

  Saves a triage verdict for one plan in the index, such as marking it a false positive. Turn it on with the tools option.

  Try: “Mark that refactoring plan as a false positive.”

  Write · set_finding_status

• Lists the repos a workspace serves (workspace mode)

  In workspace mode, returns each configured repo's alias and paths so you can pass one to the other tools. Workspace mode only; on by default there.

  Try: “Which repos does this workspace cover?”

  Read · list_repos

• Scores coupling across services (opt-in, workspace)

  Reports how tightly your services depend on each other, the largest cycle and a 1 to 10 architecture score. Workspace mode only, and turned on with the tools option.

  Try: “How coupled are our services?”

  Read · get_architecture

• Lists services a change could reach (opt-in, workspace)

  Walks the cross-repo graph from the service or symbol you name and ranks the downstream services reachable from it. The ranking is a heuristic, not proof of breakage. Workspace mode only, and turned on with the tools option.

  Try: “Which services depend on the billing service?”

  Read · get_blast_radius

• Finds dependency-rule breaks (opt-in, workspace)

  Lists cross-repo dependencies that break the allow and deny rules you declared, plus circular service dependencies. Workspace mode only, and turned on with the tools option.

  Try: “Does our architecture still follow our dependency rules?”

  Read · get_conformance

Watch out for

• Opt-in tools can write or call your model

  One opt-in tool writes triage verdicts to the index and another calls your own language model to draft a diff. Leave them off unless you need them. github.com

• Usage numbers are sent unless you turn them off

  The README says the open-source version sends anonymous CLI telemetry, which you can switch off. github.com

• Code stays local unless you enable prose

  Indexing needs no key. The README says your LLM provider receives code only if you turn on prose generation. github.com

Security advisories