dev-pipeline vs io.github.vish288/mcp-gitlab
dev-pipeline is a plugin bundle for AI coding tools published by foyzulkarim. Marketplaces we read that list it: 1 (Community GitHub marketplaces). io.github.vish288/mcp-gitlab is an MCP server published by vish288. Marketplaces we read that list it: 2 (Official MCP Registry, PyPI (MCP servers)). As of our marketplace pass on 2026-10-24. 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 |  io.github.vish288/mcp-gitlab | |
|---|---|---|
| Community marketplace foyzulkarim/skills | Listed Version: 6.2.1 Forks (GitHub): 14 Stars (GitHub): 43 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 0.21.2 Downloads/month (PyPI): 19 493 Downloads/week (PyPI): 10 302 Forks (GitHub): 3 Stars (GitHub): 6 Not marked · First seen |
| PyPI (MCP servers) | Not listed | Listed Version: 0.21.2 Downloads/month (PyPI): 19 493 Downloads/week (PyPI): 10 302 Forks (GitHub): 3 Stars (GitHub): 6 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 | dev-pipeline | io.github.vish288/mcp-gitlab |
|---|---|---|
| Marketplaces that list it (differs) | 1 (worse) | 2 (better) |
| Stars (GitHub) (differs) | 43 (better) | 6 (worse) |
| Forks (GitHub) (differs) | 14 (better) | 3 (worse) |
| Last release (differs) | Not published | 2026-10-23 |
| Where it runs (differs) | Installs as a plugin bundle | On your machine (mcp-gitlab) |
| Transport (differs) | Not stated | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | Not published | 11, secrets among them: 4 |
| Parts of the bundle (differs) | 23 | Not a bundle |
| Licence (differs) | Not stated | MIT |
| Repository (differs) | github.com/foyzulkarim/skills | github.com/vish288/mcp-gitlab |
| Changes in the last 7 days (differs) | 2 | 6 |
| First seen (differs) | 2026-10-18 | 2026-10-11 |
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
dev-pipeline
A 5-phase development pipeline (requirement engineering, system architecture, task generation, verified implementation, code review) with an optional QA gate (plan-qa + execute-qa) for changes that have a running surface worth driving — independent of /review, run sequentially or in parallel at the developer's discretion — plus supporting skills for branch bootstrap, worktree lanes, issue archival, release notes, session stats, session cost tracking, and conventional commits
io.github.vish288/mcp-gitlab
GitLab MCP server (MCP 2026-07-28): projects, MRs, pipelines, CI/CD, issues; writes or read-only
How to run each
dev-pipeline As a Claude Code plugin
/plugin marketplace add foyzulkarim/skills
/plugin install dev-pipeline@foyzulkarim-skillsio.github.vish288/mcp-gitlab As a local MCP server: PyPI package
claude mcp add --env "GITLAB_HTTP_BEARER_TOKEN=<YOUR_GITLAB_HTTP_BEARER_TOKEN>" --env "GITLAB_OAUTH_CLIENT_SECRET=<YOUR_GITLAB_OAUTH_CLIENT_SECRET>" --env "GITLAB_OAUTH_JWT_KEY=<YOUR_GITLAB_OAUTH_JWT_KEY>" --env "GITLAB_TOKEN=<YOUR_GITLAB_TOKEN>" --env "GITLAB_URL=<YOUR_GITLAB_URL>" --transport stdio mcp-gitlab -- uvx mcp-gitlabRequires: GITLAB_HTTP_BEARER_TOKEN (secret), GITLAB_OAUTH_CLIENT_SECRET (secret), GITLAB_OAUTH_JWT_KEY (secret), GITLAB_TOKEN (secret), GITLAB_URL
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
The marketplaces of dev-pipeline publish no settings it asks for, so we do not compare settings.
What it can do: dev-pipeline · What it can do: io.github.vish288/mcp-gitlab · Compare two other plugins
Data comes from public marketplace files in GitHub repositories of their authors. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Package data comes from the Python Package Index (pypi.org). Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.