Release Intel vs Repowise
A side-by-side look at the Release Intel and Repowise MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Release Intel for version control work as a local process; 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?
Choose Release Intel when
- You need dedicated capabilities in the Version Control domain.
- You prefer a local stdio subprocess transport.
- You want tools like
get_changes_between_refs, get_pull_requests_in_range, get_release_summary.
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 | ||
|---|---|---|
| Category | Version Control | Version Control |
| Quality signal | 60/100 · Good | 61/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | No auth required |
| Pricing | Not declared | Free |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 2 | 7,875 |
| Directory activity | 3 views 0 installs 0 upvotes | 5 views 0 installs 0 upvotes |
| Tools | 3 | Not listed |
| Full listing | View Release Intel | View Repowise |
Tools & capabilities
Release Intel tools 3
get_changes_between_refsGet all commits between two git refs enriched with associated PR metadata, author information, and linked issues. Uses the GitHub compare API.get_pull_requests_in_rangeGet all merged pull requests between two refs with full metadata including labels, linked issues, review counts, and files changed. PRs are categorized by label into: breaking, feature, fix, docs, chore, dependencies, other.get_release_summaryGenerate a structured release context object ready for AI synthesis into release notes. Combines commit data, PR metadata, linked issues, contributor list, and aggregate statistics for the range between two tags.
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.
Release Intel
{
"mcpServers": {
"release-intel": {
"command": "npx",
"args": [
"-y",
"@barissozudogru/release-intel-mcp"
]
}
}
}
Repowise
{
"mcpServers": {
"repowise-dev-repowise": {
"command": "uvx",
"args": [
"repowise"
]
}
}
}
Frequently asked questions
Release Intel is categorized under Version Control and uses a local stdio subprocess. Repowise belongs to Version Control and uses a local stdio subprocess. Pick Release Intel 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.
Release Intel has no declared pricing — check the project's own site. 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 release-intel and repowise-dev-repowise as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Release Intel has a quality signal of 60/100 (Good) with 3 views, 0 installs and 2 GitHub stars. Repowise has 61/100 (Good) with 5 views, 0 installs and 7,875 GitHub stars.