runbook-writer vs io.github.ai-4-devops/devops-practices
runbook-writer is no longer listed on any marketplace we read: these are its last known data, as of 2026‑10‑18.
runbook-writer is a plugin bundle for AI coding tools published by barnburner121. No marketplace we read lists it any more. io.github.ai-4-devops/devops-practices is an MCP server published by ai-4-devops. 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 |  io.github.ai-4-devops/devops-practices | |
|---|---|---|
| Community marketplace barnburner121/claude-plugin-marketplace | Removed on 2026-10-18 Version: 1.0.0 Forks (GitHub): 0 Stars (GitHub): 3 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 1.4.0 Downloads/month (PyPI): 92 Downloads/week (PyPI): 33 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 | runbook-writerno longer listed · | io.github.ai-4-devops/devops-practices |
|---|---|---|
| Marketplaces that list it (differs) | 0 | 1 |
| Stars (GitHub) (differs) | 3 | 0 |
| Forks (GitHub) | 0 | 0 |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (@barnburner121/plugin-hub-mcp) | On your machine (devops-practices-mcp) |
| Transport (differs) | Not stated | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Parts of the bundle (differs) | 2 | Not a bundle |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/barnburner121/claude-plugin-marketplace | github.com/ai-4-devops/devops-practices |
| 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 runbook-writer
Plugins still listed whose own names, descriptions, tools and skills are closest in meaning to it. Comparable, not endorsed.
-
Verify and Runbooks workflow automation via the aviator CLI
-
Site reliability engineering and incident response expert
-
Plan, document, and implement a backup and data-protection strategy for the current project — from architecture discovery through script generation and restore drills.
-
Skills voor ZAD deployment: linting, releases, action validatie, workflow generatie en deployment debugging voor Zelfservice voor Applicatie Deployment.
-
Use this agent when monitoring system health, optimizing performance, managing scaling, or ensuring infrastructure reliability. This agent excels at keeping studio applications…
-
Stateful runbooks for long-running coding agents using the statem CLI.
What each says it does
runbook-writer
Generate operational runbooks for services
io.github.ai-4-devops/devops-practices
Productivity framework for DevOps engineers using AI assistance (Claude Code) while working on PoCs
How to run each
runbook-writer
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
io.github.ai-4-devops/devops-practices As a local MCP server: PyPI package
claude mcp add --transport stdio devops-practices -- uvx devops-practices-mcp -m devops_practices_mcpCommands 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
Neither one's marketplaces publish the settings it asks for.
What it can do: runbook-writer · What it can do: io.github.ai-4-devops/devops-practices · 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.