Github Private vs Repowise
A side-by-side look at the Github Private 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 Github Private 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 Github Private when
- You need dedicated capabilities in the Version Control domain.
- You prefer a local stdio subprocess transport.
- You want tools like
gh_list_repos, gh_get_repo, gh_list_issues.
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 | 0 | 7,875 |
| Directory activity | 4 views 0 installs 0 upvotes | 5 views 0 installs 0 upvotes |
| Tools | 6 | Not listed |
| Full listing | View Github Private | View Repowise |
Tools & capabilities
Github Private tools 6
gh_list_reposList all your repositories including private ones. Returns repo names, URLs, descriptions, language, stars, and last update time.gh_get_repoGet detailed info for a specific repository. Returns description, language, stars, forks, open issues, default branch, and access level.gh_list_issuesList issues in a repository. Specify owner and repo name (e.g., owner='octocat', repo='Hello-World'). Returns titles, numbers, status, assignees, and labels.gh_list_pullsList pull requests in a repository. Specify owner and repo name (e.g., owner='octocat', repo='Hello-World'). Returns titles, numbers, status, reviewers, and merge state.gh_list_orgsList organizations you're a member of. Returns org names, URLs, and your role (owner, member, etc.).gh_get_fileGet file contents from a repository. Specify owner, repo name, and file path (e.g., 'README.md'). Returns raw content and metadata.
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.
Github Private
{
"mcpServers": {
"github-private": {
"command": "npx",
"args": [
"-y",
"@pipeworx/mcp-github_private"
]
}
}
}
Repowise
{
"mcpServers": {
"repowise-dev-repowise": {
"command": "uvx",
"args": [
"repowise"
]
}
}
}
Frequently asked questions
Github Private is categorized under Version Control and uses a local stdio subprocess. Repowise belongs to Version Control and uses a local stdio subprocess. Pick Github Private 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.
Github Private 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 github-private and repowise-dev-repowise as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Github Private has a quality signal of 60/100 (Good) with 4 views, 0 installs and 0 GitHub stars. Repowise has 61/100 (Good) with 5 views, 0 installs and 7,875 GitHub stars.