Ext Ops Panel
Open dashboard
Comparison

io.github.Sahilll15/gocd vs io.github.mshegolev/gitlab-ci-mcp

io.github.Sahilll15/gocd is an MCP server published by Sahilll15. Marketplaces we read that list it: 1 (Official MCP Registry). io.github.mshegolev/gitlab-ci-mcp is an MCP server published by mshegolev. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-25. 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

Where each is published
Marketplaceio.github.Sahilll15/gocdio.github.mshegolev/gitlab-ci-mcp
Official MCP Registry Listed
Version: 0.1.2
Downloads/month (npm): 128
Downloads/week (npm): 19
Forks (GitHub): 0
Stars (GitHub): 1
Not marked · First seen
Listed
Version: 0.5.1
Downloads/month (PyPI): 172
Downloads/week (PyPI): 53
Forks (GitHub): 0
Stars (GitHub): 2
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

io.github.Sahilll15/gocd vs io.github.mshegolev/gitlab-ci-mcp
Factio.github.Sahilll15/gocdio.github.mshegolev/gitlab-ci-mcp
Marketplaces that list it11
Stars (GitHub) (differs)1 (worse)2 (better)
Forks (GitHub)00
Last releaseNot publishedNot published
Where it runs (differs)On your machine (gocd-mcp)On your machine (gitlab-ci-mcp)
Transportstdiostdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)2, secrets among them: 14, secrets among them: 1
LicenceNot statedNot stated
Repository (differs)github.com/sahilll15/gocd-mcpgithub.com/mshegolev/gitlab-ci-mcp
Changes in the last 7 days00
First seen2026-10-112026-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

io.github.Sahilll15/gocd

In its own words, on Official MCP Registry:

MCP server for GoCD: dashboard, pipelines, artifacts, agents. Context-lean output.

io.github.mshegolev/gitlab-ci-mcp

In its own words, on Official MCP Registry:

GitLab CI/CD MCP — pipelines, jobs, schedules, MRs, files. Any GitLab (SaaS or self-hosted).

How to run each

io.github.Sahilll15/gocd As a local MCP server: npm package

Claude Code
claude mcp add --env "GOCD_ACCESS_TOKEN=<YOUR_GOCD_ACCESS_TOKEN>" --env "GOCD_BASE_URL=<YOUR_GOCD_BASE_URL>" --transport stdio gocd -- npx -y gocd-mcp

Requires: GOCD_ACCESS_TOKEN (secret), GOCD_BASE_URL

io.github.mshegolev/gitlab-ci-mcp As a local MCP server: PyPI package

Claude Code
claude mcp add --env "GITLAB_TOKEN=<YOUR_GITLAB_TOKEN>" --env "GITLAB_URL=<YOUR_GITLAB_URL>" --transport stdio gitlab-ci-mcp -- uvx gitlab-ci-mcp

Requires: 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

Only io.github.Sahilll15/gocd asks for

  • GOCD_ACCESS_TOKEN (secret)
  • GOCD_BASE_URL

Only io.github.mshegolev/gitlab-ci-mcp asks for

  • GITLAB_PROJECT_PATH
  • GITLAB_SSL_VERIFY
  • GITLAB_TOKEN (secret)
  • GITLAB_URL

Settings as each marketplace publishes them. Asking for fewer is not better in itself.

What it can do: io.github.Sahilll15/gocd · What it can do: io.github.mshegolev/gitlab-ci-mcp · 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.

Where the data comes from: how the catalog is built