MCP Gitlab vs Gitlab Public
MCP Gitlab is an MCP server published by crunchtools. Marketplaces we read that list it: 1 (Official MCP Registry). Gitlab Public is an MCP server published by pipeworx-io. 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 |  MCP Gitlab |  Gitlab Public |
|---|---|---|
| Official MCP Registry | Listed Version: 0.4.1 Downloads/month (PyPI): 89 Downloads/week (PyPI): 144 Forks (GitHub): 1 Stars (GitHub): 2 Not marked · First seen |
Listed Version: 0.1.2 Forks (GitHub): 0 Stars (GitHub): 1 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 | MCP Gitlab | Gitlab Public |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 2 (better) | 1 (worse) |
| Forks (GitHub) (differs) | 1 (better) | 0 (worse) |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (mcp-gitlab-crunchtools) | Remote server (gateway.pipeworx.io/gitlab-public/mcp) |
| Transport (differs) | stdio | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Licence | Not stated | Not stated |
| Repository (differs) | github.com/crunchtools/mcp-gitlab | github.com/pipeworx-io/mcp-gitlab-public |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Responded 7 h ago |
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
MCP Gitlab
Secure MCP server for GitLab projects, merge requests, issues, and pipelines
Gitlab Public
GitLab Public MCP — wraps the GitLab REST API v4 (public endpoints, no auth)
How to run each
MCP Gitlab As a local MCP server: PyPI package
claude mcp add --transport stdio gitlab -- uvx mcp-gitlab-crunchtoolsGitlab Public As a remote MCP server
claude mcp add --transport http gitlab-public https://gateway.pipeworx.io/gitlab-public/mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only Gitlab Public 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
Neither one's marketplaces publish the settings it asks for.
What it can do: MCP Gitlab · What it can do: Gitlab Public · Compare two other plugins
Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.