GitHub CI/CD MCP Server vs Woodpecker CI
GitHub CI/CD MCP Server is an MCP server published by devstephenke-sys. Marketplaces we read that list it: 1 (Official MCP Registry). Woodpecker CI is an MCP server published by ni-c. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-18. 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 CI/CD MCP Server |  Woodpecker CI |
|---|---|---|
| Official MCP Registry | Listed Version: 1.2.2 Forks (GitHub): 0 Stars (GitHub): 2 Not marked · First seen |
Listed Version: 0.4.0 Downloads/month (npm): 220 Downloads/week (npm): 45 Forks (GitHub): 0 Stars (GitHub): 0 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 | GitHub CI/CD MCP Server | Woodpecker CI |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 2 (better) | 0 (worse) |
| Forks (GitHub) | 0 | 0 |
| Last release (differs) | Not published | 2026-10-15 |
| Where it runs (differs) | On your machine (@kinus/github-cicd-mcp) | On your machine (@ni-c/woodpecker-ci-mcp) |
| Transport | stdio | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | 4, secrets among them: 1 | 7, secrets among them: 1 |
| Licence | Not stated | Not stated |
| Repository (differs) | github.com/devstephenke-sys/github-free-mcps | github.com/ni-c/woodpecker-ci-mcp |
| Changes in the last 7 days | 2 | 2 |
| First seen (differs) | 2026-10-13 | 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
GitHub CI/CD MCP Server
GitHub CI/CD MCP server with 70 tools for repos, PRs, Actions, deployments, billing, and more.
Woodpecker CI
Read Woodpecker CI repositories, pipelines and logs, and drive builds, secrets and crons
How to run each
GitHub CI/CD MCP Server As a local MCP server: npm package
claude mcp add --env "GITHUB_TOKEN=<YOUR_GITHUB_TOKEN>" --transport stdio github-cicd -- npx -y @kinus/github-cicd-mcpRequires: GITHUB_TOKEN (secret)
Woodpecker CI As a local MCP server: npm package
claude mcp add --env "WOODPECKER_TOKEN=<YOUR_WOODPECKER_TOKEN>" --env "WOODPECKER_URL=<YOUR_WOODPECKER_URL>" --transport stdio woodpecker-ci-mcp -- npx -y @ni-c/woodpecker-ci-mcpRequires: WOODPECKER_TOKEN (secret), WOODPECKER_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 GitHub CI/CD MCP Server asks for
GITHUB_API_URLGITHUB_GRAPHQL_URLGITHUB_HOSTGITHUB_TOKEN (secret)
Only Woodpecker CI asks for
WOODPECKER_ALLOW_TOOLSWOODPECKER_API_PREFIXWOODPECKER_DENY_TOOLSWOODPECKER_INSECURE_TLSWOODPECKER_READ_ONLYWOODPECKER_TOKEN (secret)WOODPECKER_URL
Settings as each marketplace publishes them. Asking for fewer is not better in itself.
What it can do: GitHub CI/CD MCP Server · What it can do: Woodpecker CI · 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.