aio-devops vs Woodpecker CI
aio-devops is no longer listed on any marketplace we read: these are its last known data, as of 2026‑10‑19.
aio-devops is a plugin bundle for AI coding tools published by aiocean. No marketplace we read lists it any more. 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-22. A plugin in this pair is no longer listed on any marketplace we read, so search engines are asked not to index the page.
Where each is published
| Marketplace |  Woodpecker CI | |
|---|---|---|
| Community marketplace aiocean/claude-plugins | Removed on 2026-10-19 Version: 1.0.6 Forks (GitHub): 1 Stars (GitHub): 4 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | 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 | aio-devopsno longer listed · | Woodpecker CI |
|---|---|---|
| Marketplaces that list it (differs) | 0 | 1 |
| Stars (GitHub) (differs) | 4 | 0 |
| Forks (GitHub) (differs) | 1 | 0 |
| Last release (differs) | Not published | 2026-10-15 |
| Where it runs (differs) | Installs as a plugin bundle | On your machine (@ni-c/woodpecker-ci-mcp) |
| Transport (differs) | Not stated | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | Not published | 7, secrets among them: 1 |
| Parts of the bundle (differs) | 3 | Not a bundle |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/aiocean/claude-plugins | github.com/ni-c/woodpecker-ci-mcp |
| Changes in the last 7 days (differs) | 2 | 0 |
| First seen (differs) | 2026-10-14 | 2026-10-11 |
Lines where the two differ have a tinted background and bold values. No value is marked better or worse: a plugin no marketplace lists any more is shown with its last known data, which we do not rank against current figures.
What to use instead of aio-devops
Plugins still listed whose own names, descriptions, tools and skills are closest in meaning to it. Comparable, not endorsed.
-
Inspect repositories, triage pull requests and issues, debug CI, and publish changes through a hybrid GitHub connector and CLI workflow.
-
GitLab workflow best practices and glab CLI usage
-
Skills for Gitea/Forgejo workflows using the tea CLI
-
Connect AI assistants to GitHub - manage repos, issues, PRs, workflows, and git operations.
-
GitLab through the glab CLI — the glab skill, the mr-status skill and its state script, the mr-watch agent, and MR commands for pipeline and comment state
-
Connect AI assistants to GitHub - manage repos, issues, PRs, and workflows through natural language.
What each says it does
aio-devops
GitHub, GitLab, and git worktree workflows in one toolkit — manage repos, PRs, MRs, pipelines, and parallel branches without juggling CLIs.
Woodpecker CI
Read Woodpecker CI repositories, pipelines and logs, and drive builds, secrets and crons
How to run each
aio-devops
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
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
The marketplaces of aio-devops publish no settings it asks for, so we do not compare settings.
What it can do: aio-devops · What it can do: Woodpecker CI · 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. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.