Ext Ops Panel
Open dashboard
Comparison

cli-builder vs io.github.GoatInAHat/toolfactory

cli-builder is no longer listed on any marketplace we read: these are its last known data, as of 2026‑10‑18.

cli-builder is a plugin bundle for AI coding tools published by barnburner121. No marketplace we read lists it any more. io.github.GoatInAHat/toolfactory is an MCP server published by GoatInAHat. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-19. 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

Where each is published
Marketplacecli-builderio.github.GoatInAHat/toolfactory
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: 0.4.6
Downloads/month (npm): 1 834
Downloads/week (npm): 631
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

cli-builder vs io.github.GoatInAHat/toolfactory
Factcli-builderno longer listed · io.github.GoatInAHat/toolfactory
Marketplaces that list it (differs)01
Stars (GitHub) (differs)30
Forks (GitHub)00
Last releaseNot publishedNot published
Where it runs (differs)On your machine (@barnburner121/plugin-hub-mcp)On your machine (toolfactory)
Transport (differs)Not statedstdio
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Parts of the bundle (differs)2Not a bundle
LicenceMITMIT
Repository (differs)github.com/barnburner121/claude-plugin-marketplacegithub.com/goatinahat/toolfactory
Changes in the last 7 days44
First seen (differs)2026-10-142026-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 cli-builder

Plugins still listed whose own names, descriptions, tools and skills are closest in meaning to it. Comparable, not endorsed.

  • ruflo-plugin-creator

    Scaffold, validate, and publish new Claude Code plugins with proper structure

    by ruvnet · Plugin bundle

    Listed on: Community GitHub marketplaces · Describes nearly the same job

  • claude-forge

    Evidence-first Claude Code plugin for repeatable, spec-driven development workflows.

    by JunghyunRyu · Plugin bundle

    Listed on: Claude Code: claude-plugins-community · Describes nearly the same job

  • sf

    Guides you from requirements to working code — define a spec, implement it, and generate docs, all from your terminal. Installs as a Claude Code plugin, or as skills on 15+ other…

    by Szymon Graczyk · Plugin bundle

    Listed on: Community GitHub marketplaces · Describes nearly the same job

  • Packkit

    Scaffold modern npm packages, CLIs, services and apps as a native tool for AI agents.

    by DanMat · MCP server

    Listed on: Official MCP Registry · Describes nearly the same job

  • claude-code-bootstrapper

    Analyze any project and generate a complete .claude/ automation structure: agents, pipelines, skills, memory, hooks, and settings. Supports fresh generation and validation modes.

    by BeMySlaveDarlin · Plugin bundle

    Listed on: Claude Code: claude-plugins-community · Describes nearly the same job

Its card, with similar plugins by marketplace

What each says it does

cli-builder

In its own words, on Community GitHub marketplaces:

Generate CLI tools from function signatures

io.github.GoatInAHat/toolfactory

In its own words, on Official MCP Registry:

Build an agent tool once; ship it as Agent Skills, MCP servers, Agent Plugins / Claude / Codex

How to run each

cli-builder

No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.

io.github.GoatInAHat/toolfactory As a local MCP server: npm package

Claude Code
claude mcp add --transport stdio toolfactory -- npx -y toolfactory

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

Neither one's marketplaces publish the settings it asks for.

What it can do: cli-builder · What it can do: io.github.GoatInAHat/toolfactory · 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.

Where the data comes from: how the catalog is built