RepoPilot vs Repowise
A side-by-side look at the RepoPilot and Repowise MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
R
RepoPilotVersion Control · Remote HTTP/SSERepository evidence for agents before they adopt dependencies, enter codebases, compare, or merge.39FairAuth: no auth requiredVerdict: choose RepoPilot for version control work over a hosted endpoint; choose Repowise for version control as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
RChoose RepoPilot when
- You need dedicated capabilities in the Version Control domain.
- You prefer a remote HTTP/SSE transport.
- Its auth model fits you: No auth required.
Choose Repowise when
- You need dedicated capabilities in the Version Control domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: No auth required.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | R RepoPilot | |
|---|---|---|
| Category | Version Control | Version Control |
| Quality signal | 39/100 · Fair | 61/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Remote HTTP/SSE | Local subprocess (stdio) |
| Auth | No auth required | No auth required |
| Pricing | Not declared | Free |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | — | 7,891 |
| Directory activity | 1 views 0 installs 0 upvotes | 5 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View RepoPilot | View Repowise |
Tools & capabilities
RepoPilot tools
No tool names declared yet. Check the project README from the listing page.
Repowise tools
No tool names declared yet. Check the project README from the listing page.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
RepoPilot
{
"mcpServers": {
"repopilot": {
"command": "npx",
"args": [
"-y",
"repopilot"
]
}
}
}
Repowise
{
"mcpServers": {
"repowise-dev-repowise": {
"command": "uvx",
"args": [
"repowise"
]
}
}
}
Frequently asked questions
RepoPilot is categorized under Version Control and uses a remote HTTP/SSE transport. Repowise belongs to Version Control and uses a local stdio subprocess. Pick RepoPilot for version control work and Repowise for version control.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
RepoPilot has no declared pricing — check the project's own site. Auth: no auth required. Repowise is listed as free. Auth: no auth required. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add repopilot and repowise-dev-repowise as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, RepoPilot has a quality signal of 39/100 (Fair) with 1 views, 0 installs and 0 GitHub stars. Repowise has 61/100 (Good) with 5 views, 0 installs and 7,891 GitHub stars.