Github Private vs GitVerse MCP
A side-by-side look at the Github Private and GitVerse MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
G
GitVerse MCPVersion Control · Local subprocess (stdio)MCP server for GitVerse: repositories, pull requests, reviews, comments and CI60GoodAuth: api key requiredVerdict: choose Github Private for version control work as a local process; choose GitVerse MCP 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.
GChoose GitVerse MCP when
- You need dedicated capabilities in the Version Control domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: API key required.
- You have the keys it needs:
GITVERSE_TOKEN. - You want tools like
listRepositories, getRepository, getPullRequests.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | G GitVerse MCP | |
|---|---|---|
| Category | Version Control | Version Control |
| Quality signal | 60/100 · Good | 60/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | API key required |
| Pricing | Not declared | Not declared |
| Required env vars | None listed | GITVERSE_TOKEN |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 1 |
| Directory activity | 4 views 0 installs 0 upvotes | 1 views 0 installs 0 upvotes |
| Tools | 6 | 27 |
| Full listing | View Github Private | View GitVerse MCP |
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.
GitVerse MCP tools 27
listRepositoriesList repositories. Without arguments lists the authenticated user's repositories; pass org to list organization repositories. Supports page/per_page.getRepositoryGet details of a specific repository.getPullRequestsList pull requests of a repository. state filters by open/closed. Supports page/per_page.createPullRequestCreate a pull request from head to base. GitVerse has no reviewer requests — use assignees instead. Pass draft=true to create a draft.getPullRequestGet details of a specific pull request.updatePullRequestUpdate a pull request: title, body, state (open|closed), base branch. assignees and labels are applied through the issue endpoint because a PR is an issue in GitVerse.getPullRequestActivityGet the activity/timeline of a pull request.approvePullRequestApprove a pull request by submitting an APPROVED review.unapprovePullRequestRemove your approval: finds your latest APPROVED review on the pull request and deletes it.declinePullRequestDecline (close) a pull request. An optional message is posted to the discussion before closing.requestChangesRequest changes on a pull request by submitting a REQUEST_CHANGES review.removeChangeRequestRemove your change request by superseding it with an APPROVED review (GitVerse has no dedicated un-request endpoint).- +15 more on 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"
]
}
}
}
GitVerse MCP
{
"mcpServers": {
"grigoriy-grisha-gitverse-mcp": {
"command": "npx",
"args": [
"-y",
"@grigoriy-grisha/gitverse-mcp@latest"
],
"env": {
"GITVERSE_TOKEN": "YOUR_GITVERSE_TOKEN_HERE"
}
}
}
}
Frequently asked questions
Github Private is categorized under Version Control and uses a local stdio subprocess. GitVerse MCP belongs to Version Control and uses a local stdio subprocess. Pick Github Private for version control work and GitVerse MCP 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. GitVerse MCP has no declared pricing — check the project's own site. Auth: api key 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 grigoriy-grisha-gitverse-mcp 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. GitVerse MCP has 60/100 (Good) with 1 views, 0 installs and 1 GitHub stars.