Dev Changes vs Repowise
A side-by-side look at the Dev Changes and Repowise MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
D
Dev ChangesVersion Control · Remote HTTP/SSETurn described changes into reviewed pull requests: propose, triage, review, dependency audits.43FairAuth: oauth 2.0Verdict: choose Dev Changes 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?
DChoose Dev Changes when
- You need dedicated capabilities in the Version Control domain.
- You prefer a remote HTTP/SSE transport.
- Its auth model fits you: OAuth 2.0.
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 | D Dev Changes | |
|---|---|---|
| Category | Version Control | Version Control |
| Quality signal | 43/100 · Fair | 61/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Remote HTTP/SSE | Local subprocess (stdio) |
| Auth | OAuth 2.0 | No auth required |
| Pricing | Not declared | Free |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | — | 7,902 |
| Directory activity | 0 views 0 installs 0 upvotes | 6 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View Dev Changes | View Repowise |
Tools & capabilities
Dev Changes 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.
Dev Changes
{
"mcpServers": {
"dev-changes": {
"url": "https://openhelm.ai/mcp/dev-changes"
}
}
}
Repowise
{
"mcpServers": {
"repowise-dev-repowise": {
"command": "uvx",
"args": [
"repowise"
]
}
}
}
Frequently asked questions
Dev Changes is categorized under Version Control and uses a remote HTTP/SSE transport. Repowise belongs to Version Control and uses a local stdio subprocess. Pick Dev Changes 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.
Dev Changes has no declared pricing — check the project's own site. Auth: oauth 2.0. 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 dev-changes and repowise-dev-repowise as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Dev Changes has a quality signal of 43/100 (Fair) with 0 views, 0 installs and 0 GitHub stars. Repowise has 61/100 (Good) with 6 views, 0 installs and 7,902 GitHub stars.