harness-kit vs io.github.ai-4-devops/devops-practices
harness-kit is a plugin bundle for AI coding tools published by romabeckman. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). 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-13. 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 |  io.github.ai-4-devops/devops-practices | |
|---|---|---|
| Claude Code: claude-plugins-community | Listed Version: 1.3.8 Forks (GitHub): 7 Stars (GitHub): 30 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 1.4.0 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 | harness-kit | io.github.ai-4-devops/devops-practices |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 30 (better) | 0 (worse) |
| Forks (GitHub) (differs) | 7 (better) | 0 (worse) |
| Last release | Not published | Not published |
| Where it runs (differs) | Installs as a plugin bundle | 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) | 19 | Not a bundle |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/romabeckman/harness-kit | github.com/ai-4-devops/devops-practices |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 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
harness-kit
HarnessKit is a professional-grade engineering framework that empowers AI agents with a robust 'harness' of structured controls and specialized personas. Built on the principles of Harness Engineering, it enforces a disciplined development workflow—from domain-driven scope refinement to strict TDD implementation and Socratic technical reviews—ensuring your AI assistant maintains architectural integrity, comprehensive test coverage, and persistent project memory throughout the entire software lifecycle.
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
harness-kit
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: harness-kit · What it can do: io.github.ai-4-devops/devops-practices · Compare two other plugins
Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. 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.