closedloop vs io.github.theluckystrike/agreement
closedloop is a plugin bundle for AI coding tools published by closedloop-ai. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). io.github.theluckystrike/agreement is an MCP server published by theluckystrike. Marketplaces we read that list it: 1 (Official MCP Registry). 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 | ||
|---|---|---|
| Claude Code: claude-plugins-community | Listed Version: 73d1995 Forks (GitHub): 16 Stars (GitHub): 123 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 0.22.5 Forks (GitHub): 0 Stars (GitHub): 2 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 | closedloop | io.github.theluckystrike/agreement |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 123 (better) | 2 (worse) |
| Forks (GitHub) (differs) | 16 (better) | 0 (worse) |
| Last release (differs) | Not published | 2026-10-14 |
| Where it runs (differs) | Installs as a plugin bundle | Remote server or your machine |
| Transport (differs) | Not stated | stdio, Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | Not published | 1, secrets among them: 1 |
| Licence | Not stated | Not stated |
| Repository (differs) | github.com/closedloop-ai/claude-plugins | github.com/theluckystrike/mcp-servers |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Responded 37 h ago |
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
closedloop
Open-source Claude Code plugins for multi-agent software delivery. Plan-first SDLC workflow, code review, LLM quality judges, and self-learning — grounded in your codebase. Bootstrap, Plan, & Ship.
io.github.theluckystrike/agreement
Reusable agreement and proposal clauses assembled into a real Word docx, variables filled.
How to run each
closedloop As a Claude Code plugin
/plugin marketplace add anthropics/claude-plugins-community
/plugin install closedloop@claude-community
io.github.theluckystrike/agreement As a remote MCP server
claude mcp add --transport http contract-clause-library-proposal-templat https://mcp.zovo.one/mcp/clauses --header "Authorization: Bearer <YOUR_TOKEN>"
Requires: MCP_LICENSE_KEY (secret), Authorization header
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only io.github.theluckystrike/agreement has a remote endpoint we check. How we check endpoints
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 closedloop publish no settings it asks for, so we do not compare settings.
What it can do: closedloop · What it can do: io.github.theluckystrike/agreement · 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.