Git vs GitLab MCP Server
Git is an MCP server published by Abhishekkumar2021. Marketplaces we read that list it: 2 (Official MCP Registry, Community GitHub marketplaces). GitLab MCP Server is an MCP server published by jmrplens. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-16. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.
Where each is published
| Marketplace |  Git |  GitLab MCP Server |
|---|---|---|
| Official MCP Registry | Listed Version: 0.2.0 Downloads/month (npm): 183 Downloads/week (npm): 32 Forks (GitHub): 0 Stars (GitHub): 1 Not marked · First seen |
Listed Version: 3.2.0 Forks (GitHub): 5 Stars (GitHub): 45 Not marked · First seen |
Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.
The facts side by side
| Fact | Git | GitLab MCP Server |
|---|---|---|
| Marketplaces that list it (differs) | 2 (better) | 1 (worse) |
| Stars (GitHub) (differs) | 1 (worse) | 45 (better) |
| Forks (GitHub) (differs) | 0 (worse) | 5 (better) |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (@abhishekmcp/git) | Remote server (mcp.jmrp.io/gitlab) |
| Transport (differs) | stdio | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | 2, secrets among them: 0 | 19, secrets among them: 1 |
| Parts of the bundle (differs) | 1 | Not a bundle |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/abhishekkumar2021/mcp-suite | github.com/jmrplens/gitlab-mcp-server |
| Changes in the last 7 days (differs) | 2 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Responded 44 h ago, requires a key |
Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.
What each says it does
Git
Local Git via MCP: status, log, diff, file history, branches, and gated stage/commit. Pure-JS.
GitLab MCP Server
Go MCP server for GitLab: 2 dynamic tools reach ~872 actions on Free/CE, up to ~1098 on Ultimate.
How to run each
Git As a local MCP server: npm package
claude mcp add --env "GIT_ROOTS=<YOUR_GIT_ROOTS>" --transport stdio git -- npx -y @abhishekmcp/gitRequires: GIT_ROOTS
GitLab MCP Server As a remote MCP server
claude mcp add --transport http gitlab-mcp-server https://mcp.jmrp.io/gitlab --header "Authorization: Bearer <YOUR_TOKEN>"Requires: GITLAB_TOKEN (secret), Authorization header
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only GitLab MCP Server has a remote endpoint we check. How we check endpoints
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
Only Git asks for
GIT_ROOTSGIT_WRITABLE
Only GitLab MCP Server asks for
GITLAB_MCP_ALLOWED_DOWNLOAD_DIRSGITLAB_MCP_ALLOWED_IMPORT_DIRSGITLAB_MCP_ALLOWED_UPLOAD_DIRSGITLAB_MCP_CAPABILITY_SURFACEGITLAB_MCP_EMBEDDED_RESOURCESGITLAB_MCP_EXCLUDE_TOOLSGITLAB_MCP_IGNORE_SCOPESGITLAB_MCP_LOG_LEVELGITLAB_MCP_META_PARAM_SCHEMAGITLAB_MCP_RATE_LIMIT_BURSTGITLAB_MCP_RATE_LIMIT_RPSGITLAB_MCP_READ_ONLY
Show the remaining 7
GITLAB_MCP_SAFE_MODEGITLAB_MCP_SKIP_TLS_VERIFYGITLAB_MCP_TIERGITLAB_MCP_TOOL_SURFACEGITLAB_MCP_UPLOAD_MAX_FILE_SIZEGITLAB_TOKEN (secret)GITLAB_URL
Settings as each marketplace publishes them. Asking for fewer is not better in itself.
What it can do: Git · What it can do: GitLab MCP Server · Compare two other plugins
Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Data comes from public marketplace files in GitHub repositories of their authors. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.