REA
Reverse engineer anything from your terminal or agent with one CLI and MCP server.
Ask how your codebase works. Hosted codebase intelligence for repos indexed on repowise.dev.
Pick the AI app you use, then copy the settings.
Passed 5/5 checks · What you ask goes through the maker’s server (api.repowise.dev)
First: which AI do you use?
Pick your app and the steps appear below.
Works with Claude · about 2 min
No key, nothing to install · Set it up once on claude.ai or the desktop app, then use it in chat · free accounts can add 1 · on Team/Enterprise an Owner adds it
CustomizeConnectors
Copy each value into the field with the same name in Claude, then click Continue
Repowise (Hosted)https://api.repowise.dev/mcpLeave Authentication as Claude detected it, then click Add
+ConnectorsRepowise (Hosted)
Use Repowise (Hosted) and tell me what you can do for me, then show me one thing✓ If Claude says it is using Repowise (Hosted) or shows a Repowise (Hosted) tool in the answer, you are connected
Menu names checked against Anthropic’s help page on Nov 11, 2026 · your screen may differ slightly by app version
Works with ChatGPT on business plans only
ChatGPT Business, Enterprise or Edu on the web, added by a workspace admin or owner · On Free, Plus or Pro: your ChatGPT plan cannot connect MCP yet
Plugins+Add custom MCP server
Enter a name, paste the address under Connection, tick the risk warning and click Create as a plugin
Repowise (Hosted)https://api.repowise.dev/mcpStart a new chat and pick Repowise (Hosted) from your plugins before typing
Use Repowise (Hosted) and tell me what you can do for me, then show me one thing✓ If ChatGPT says it is using Repowise (Hosted) or shows a Repowise (Hosted) tool in the answer, you are connected
Menu names checked against OpenAI’s help page on Nov 11, 2026 · your screen may differ slightly by app version
Works with Claude Code · about 2 min
No key, nothing to install
Mac: press Command+Space and type Terminal · Windows: open PowerShell
claude mcp add --transport http --scope user repowise-hosted https://api.repowise.dev/mcpYou should see Repowise (Hosted) listed as connected
Use Repowise (Hosted) and tell me what you can do for me, then show me one thing✓ If Claude Code says it is using Repowise (Hosted) or shows a Repowise (Hosted) tool in the answer, you are connected
Menu names checked against Anthropic’s help page on Nov 11, 2026 · your screen may differ slightly by app version
Works with Cursor · about 2 min
No key, nothing to install
Use Repowise (Hosted) and tell me what you can do for me, then show me one thing✓ If Cursor says it is using Repowise (Hosted) or shows a Repowise (Hosted) tool in the answer, you are connected
Menu names checked against Cursor’s help page on Nov 11, 2026 · your screen may differ slightly by app version
Works with VS Code · about 2 min
No key, nothing to install
Use Repowise (Hosted) and tell me what you can do for me, then show me one thing✓ If VS Code says it is using Repowise (Hosted) or shows a Repowise (Hosted) tool in the answer, you are connected
Menu names checked against VS Code’s help page on Nov 11, 2026 · your screen may differ slightly by app version
Other apps that use MCP, such as Windsurf, Zed or Gemini CLI, each add servers differently. See how in the app list.
Address for apps that connect over the web
https://api.repowise.dev/mcpJSON settings are under “For developers” below
Claude Code
claude mcp add --transport http --scope user repowise-hosted https://api.repowise.dev/mcpCursor (~/.cursor/mcp.json)
{
"mcpServers": {
"repowise-hosted": {
"url": "https://api.repowise.dev/mcp"
}
}
}VS Code (mcp.json)
{
"servers": {
"repowise-hosted": {
"type": "http",
"url": "https://api.repowise.dev/mcp"
}
}
}These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
Based on how this server connects and on each app’s own docs, checked Nov 10, 2026.
Connect over the internet in
ClaudeChatGPTGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatOpen WebUIRaycast
The server asks you to sign in before it lists its tools.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 12, 2026
The registry name was verified against the domain repowise.dev (the registry checks domain ownership)
Code last changed today
Uses AGPL-3.0
Responded in 128 ms (HTTP 401)
Declares OAuth sign-in, so your AI app can take you to log in
Not checked yet; we read the tool list when we check the endpoint
Ask, share a tip or report that it does not work. Sorted by what people marked helpful.
No posts yet. Be the first to ask or share.
Posts here are written by users, not the PopNx team.
No reviews yet
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 5 of 5 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
The registry does not list a required key, though some servers ask you to sign in on first use.
It runs in the maker’s cloud. Connect over the internet with nothing to install, but what you send passes through the maker’s servers.
The GitHub repo last changed today, and the latest version (1.0.0) reached the registry 6 days ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. It connects by URL, so apps that accept remote MCP servers work too, such as ChatGPT Business and above.
Servers in the same category from other makers, sorted by stars.
Reading a card:↓ Downloads per weeki★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
Reverse engineer anything from your terminal or agent with one CLI and MCP server.
A powerful toolkit for coding, providing semantic retrieval and editing capabilities.
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
Stop paying your agent to re-read your codebase.
Repowise indexes your code, git history, tests and decisions once, on your machine.
Your coding agent asks the index instead of grepping and opening files, so it does about half the work.
You get the same answers in a dashboard: what calls this, what breaks, what to fix first, and why.
Half the tool calls your agent opens 3 files where it opened 7 · 31.6% less output Up to 99% less noise from test runs, installs and git output · every error line kept 88% of the right files found in one call · next best tool: 61%
Graph, risk, health, tests and dead code make zero LLM calls · no API key to index · 28 languages · Claude Code, Codex, Cursor and any MCP host · free and open source
Quickstart · For your agent · What it does · Hosted · Benchmarks · Teams · Docs
Open Claude Code, Codex, Cursor or any MCP-capable agent in your repository and paste:
Read https://docs.repowise.dev/setup.md and set up Repowise in this repository.
The agent installs Repowise, indexes the repo with no API key, connects itself to the index, and asks you before anything costs money. To do it by hand:
uv tool install repowise # or: pipx install repowise / pip install repowise
cd /path/to/your/repo repowise init --yes --no-prose # graph, git, health, dead code, docs. No key, no spend.
repowise serve # dashboard + MCP server (needs Node 20+; first run downloads the UI)
serve opens the dashboard in your browser. After a first index it starts with a short guided tour, and Setup is where you connect agents, turn on sync and add coverage or a model.
Restart Claude Code or run /mcp, then ask *"What breaks if I change src/auth.py?"* or *"Use Repowise get_overview to summarize this repository."* init wires Claude Code for this repo and adds the global repowise MCP entry when there is none; it never moves one that serves another repo. Full setup for every agent →
Without an index, an agent rediscovers your codebase on every task: grep, open a file, open three more, grep again. Repowise answers those questions ahead of time, so the agent asks once and gets on with the work.
In a measured run on django/django, an agent with Repowise made 3.8 tool calls instead of 7.2, opened 3.0 files instead of 7.2 and wrote 31.6% less, with answers just as good. That is the largest saving of the five context tools we tested. On a small local model the output cut reaches 47.9%. How it was measured →
repowise distill trims test, install and git output before the agent reads it and keeps every error line. Distill →CLAUDE.md and AGENTS.md current from the index.repowise saved and the dashboard's Usage and savings page count the tokens your agent no longer has to read.One index of your code, its history and its decisions, used three ways: to understand the code, to change it safely, and to keep improving it.
See how it fits together A call graph across 28 languages, an architecture map you can explore, C4 views, and a generated wiki for every module and file.
The graph · Docs
Know what breaks Every caller of what you changed, the files that usually change with it but are missing from your diff, and the tests that reach it.
Change risk · Tests
Fix what matters A 1 to 10 health score for every file, validated against real bug history, a ranked fix-first queue, refactoring plans and dead code.
Code health · Refactoring
Follow it across repos Services and the HTTP, gRPC and event contracts between them, with a guard for breaking changes and the consumer files they affect.
Workspaces
Ask it anything Cited answers and charts from the dashboard, or the same answers through MCP for your agent.
Dashboard · MCP tools
Remember why Decisions mined from ADRs, comments, commits, PRs and agent sessions, each tied to the code it governs, plus docs checked against the code.
Decisions · Doc drift
Every question it answers
| You ask | Repowise gives you |
|---|---|
| *How does checkout work in this repo?* | A cited answer built from the call graph and the generated docs, in one call. Search and answers |
| *What calls this function, and what does it call?* | A call graph across 28 parsed languages, every edge stamped with how it was resolved and how far to trust it, plus traced execution flows from each entry point. The graph |
| *Can I get docs for this codebase?* | A wiki for every module and file, rendered from the code's structure with no key, or written by a model when you choose. It updates incrementally after each commit. Docs |
| *Which of our docs are wrong?* | Markdown checked against the tree: every reference to a file or symbol the code no longer has, with the line to edit. Doc drift |
| *Why is it built this way?* | Decisions mined from ADRs, # WHY: comments, commit and PR history and your agent sessions, each tied to the code it governs and flagged when it goes stale. Decisions |
| *Who knows this code?* | Owners, bus factor, fading ownership when the main author goes quiet, and suggested reviewers. Ownership |
| *Can I see the architecture?* | An explorable dependency map, C4 views, and a Structurizr export, no model involved. Dashboard |
| You ask | Repowise gives you |
|---|---|
| *What breaks if I change this?* | Symbol-level blast radius: the callers of what you changed, the files that historically change with it but are missing from your diff, and the tests that reach it. Change risk |
| *How risky is this PR?* | Where the change ranks against your repository's own recent commits, with the reasons, as a directive your agent can act on. Change risk |
| *Which tests should run?* | The tests a diff actually exercises, from a coverage report if you have one and from the call graph if you do not. Test intelligence |
| *Did this PR add untested lines?* | Patch coverage, branch coverage on changed lines and path-scoped gates in CI, on GitHub, GitLab or any runner. CI gates |
| *Will this API change break another r