GitVerse MCP vs Gitlab MCP
A side-by-side look at the GitVerse MCP and Gitlab 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 GitVerse MCP for version control work as a local process; choose Gitlab MCP for version control. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
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.
Choose Gitlab MCP when
- You need dedicated capabilities in the Version Control domain.
- You want tools like
get_me, resolve_url, search_projects.
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 | 45/100 · Fair |
| Install command | Confirmed | Not confirmed yet |
| Transport | Local subprocess (stdio) | — |
| Auth | API key required | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | GITVERSE_TOKEN | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 1 | 0 |
| Directory activity | 1 views 0 installs 0 upvotes | 2 views 0 installs 0 upvotes |
| Tools | 27 | 80 |
| Full listing | View GitVerse MCP | View Gitlab MCP |
Tools & capabilities
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
Gitlab MCP tools 80
get_meWho is signed in, with which scopes, and what GitLab reports about itselfresolve_urlTurn a GitLab web URL into the arguments another tool takes, and name that toolsearch_projectsFind projects by name, or within a groupget_projectOne project: default branch, visibility, what it has turned onlist_membersWho has access to a project, and with which rolefind_usersAccounts by exact username or by namesearch_issuesFind issues across gitlab.com, a group or a projectget_issueOne issue, its description marked as untrusted content, and its linked merge requestscreate_issueCreate an issue; labels, assignees and milestone checked firstupdate_issueChange an issue's fields, refused if it changed since you read itlist_discussionsThe comment threads on an issue or a merge requestlist_item_eventsAn issue's or a merge request's label, state, milestone and weight changes, newest first- +68 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.
GitVerse MCP
{
"mcpServers": {
"grigoriy-grisha-gitverse-mcp": {
"command": "npx",
"args": [
"-y",
"@grigoriy-grisha/gitverse-mcp@latest"
],
"env": {
"GITVERSE_TOKEN": "YOUR_GITVERSE_TOKEN_HERE"
}
}
}
}
Gitlab MCP
No confirmed install command for Gitlab MCP yet — follow the setup steps linked from its listing page rather than a guessed package name.
Frequently asked questions
GitVerse MCP is categorized under Version Control and uses a local stdio subprocess. Gitlab MCP belongs to Version Control and uses an install path we have not confirmed yet. Pick GitVerse MCP for version control work and Gitlab 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. Gitlab MCP has no confirmed install command yet — follow its own setup instructions.
GitVerse MCP has no declared pricing — check the project's own site. Auth: api key required. Gitlab MCP has no declared pricing — check the project's own site. 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 grigoriy-grisha-gitverse-mcp and gitlab-mcp-2 as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, GitVerse MCP has a quality signal of 60/100 (Good) with 1 views, 0 installs and 1 GitHub stars. Gitlab MCP has 45/100 (Fair) with 2 views, 0 installs and 0 GitHub stars.