Git vs Gitlab Public
A side-by-side look at the Git and Gitlab Public MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Git for version control work as a local process; choose Gitlab Public 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 Git 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.
- You want tools like
repo_path, context_lines, target.
Choose Gitlab Public when
- You need dedicated capabilities in the Version Control domain.
- You prefer a local stdio subprocess transport.
- You want tools like
search_projects, get_project, search_issues.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Version Control | Version Control |
| Quality signal | 81/100 · Excellent | 60/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | No auth required | Not declared |
| Pricing | Free | Not declared |
| Required env vars | None listed | None listed |
| Verified owner | Verified | Community listing |
| GitHub stars | 91,512 | 1 |
| Directory activity | 49 views 0 installs 0 upvotes | 3 views 0 installs 0 upvotes |
| Tools | 16 | 3 |
| Full listing | View Git | View Gitlab Public |
Tools & capabilities
Git tools 16
repo_pathcontext_linestargetmessageMERGE_HEADHEADfilesmax_countstart_timestampend_timestampbranch_namebase_branch- +4 more on the listing page
Gitlab Public tools 3
search_projectsSearch public GitLab projects by keyword, sorted by popularity. Returns project ID, name, description, star count, fork count, open issues, and web URL.get_projectGet full details for a public GitLab project by numeric ID or "namespace/project" path (e.g., "gitlab-org/gitlab"). Pass the path as written, with a plain slash — do not URL-encode it, the tool handles that internally. Returns name, description, stars, forks, default branch, topics, and last activity date.search_issuesSearch issues across public GitLab projects by keyword. Returns issue title, state, author, labels, project ID, and direct URL.
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.
Git
{
"mcpServers": {
"git": {
"command": "uvx",
"args": [
"installations"
]
}
}
}
Gitlab Public
{
"mcpServers": {
"gitlab-public": {
"command": "npx",
"args": [
"-y",
"@pipeworx/mcp-gitlab-public"
]
}
}
}
Frequently asked questions
Git is categorized under Version Control and uses a local stdio subprocess. Gitlab Public belongs to Version Control and uses a local stdio subprocess. Pick Git for version control work and Gitlab Public 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.
Git is listed as free. Auth: no auth required. Gitlab Public 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 git and gitlab-public as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Git has a quality signal of 81/100 (Excellent) with 49 views, 0 installs and 91,512 GitHub stars. Gitlab Public has 60/100 (Good) with 3 views, 0 installs and 1 GitHub stars.