dev-pipeline vs GitHub
dev-pipeline is a plugin bundle for AI coding tools published by foyzulkarim. Marketplaces we read that list it: 1 (Community GitHub marketplaces). GitHub is an MCP server published by github. Marketplaces we read that list it: 2 (Official MCP Registry, Docker MCP Catalog). 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 |  GitHub | |
|---|---|---|
| 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: 2.0.3 Forks (GitHub): 5 227 Stars (GitHub): 33 911 Not marked · First seen |
| Docker MCP Catalog | Not listed | Listed Version: sha256:250bc6ce7078 Forks (GitHub): 5 227 Stars (GitHub): 33 911 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 | GitHub |
|---|---|---|
| Marketplaces that list it (differs) | 1 (worse) | 2 (better) |
| Stars (GitHub) (differs) | 43 (worse) | 33 911 (better) |
| Forks (GitHub) (differs) | 14 (worse) | 5 227 (better) |
| Last release (differs) | Not published | 2026-10-22 |
| Where it runs (differs) | Installs as a plugin bundle | Remote server or your machine |
| Transport (differs) | Not stated | Streamable HTTP, stdio |
| Tools it declares (differs) | Not published | 40 |
| Environment variables it asks for (differs) | Not published | 1, secrets among them: 1 |
| Parts of the bundle (differs) | 23 | Not a bundle |
| Licence (differs) | Not stated | MIT |
| Repository (differs) | github.com/foyzulkarim/skills | github.com/github/github-mcp-server |
| Changes in the last 7 days (differs) | 2 | 3 |
| First seen (differs) | 2026-10-18 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Responded 17 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
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
GitHub
Connect AI assistants to GitHub - manage repos, issues, PRs, and workflows through natural language.
How to run each
dev-pipeline As a Claude Code plugin
/plugin marketplace add foyzulkarim/skills
/plugin install dev-pipeline@foyzulkarim-skillsGitHub As a remote MCP server
claude mcp add --transport http github-mcp-server https://api.githubcopilot.com/mcp/ --header "Authorization: Bearer <YOUR_TOKEN>"Requires: Authorization header
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only GitHub has a remote endpoint we check. How we check endpoints
Tools each declares
The marketplaces of dev-pipeline publish no list of tools, so we do not compare tools.
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: GitHub · 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. Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.