Ext Ops Panel
Open dashboard
Comparison

io.github.mshegolev/gitlab-ci-mcp vs io.github.ofershap/github-actions

io.github.mshegolev/gitlab-ci-mcp is an MCP server published by mshegolev. Marketplaces we read that list it: 1 (Official MCP Registry). io.github.ofershap/github-actions is an MCP server published by ofershap. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-12. 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.mshegolev/gitlab-ci-mcpio.github.ofershap/github-actions
Official MCP Registry Listed
Version: 0.5.1
Forks (GitHub): 0
Stars (GitHub): 2
Not marked · First seen
Listed
Version: 1.0.1
Forks (GitHub): 1
Stars (GitHub): 4
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.mshegolev/gitlab-ci-mcp vs io.github.ofershap/github-actions
Factio.github.mshegolev/gitlab-ci-mcpio.github.ofershap/github-actions
Marketplaces that list it11
Stars (GitHub) (differs)2 (worse)4 (better)
Forks (GitHub) (differs)0 (worse)1 (better)
Last releaseNot publishedNot published
Where it runs (differs)On your machine (gitlab-ci-mcp)On your machine (mcp-server-github-actions)
Transportstdiostdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)4, secrets among them: 1Not published
LicenceNot statedNot stated
Repository (differs)github.com/mshegolev/gitlab-ci-mcpgithub.com/ofershap/mcp-server-github-actions
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.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).

io.github.ofershap/github-actions

In its own words, on Official MCP Registry:

GitHub Actions MCP — view runs, read logs, re-run jobs, and manage CI/CD.

How to run each

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

io.github.ofershap/github-actions As a local MCP server: npm package

Claude Code
claude mcp add --transport stdio github-actions -- npx -y mcp-server-github-actions

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 io.github.ofershap/github-actions publish no settings it asks for, so we do not compare settings.

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