Ext Ops Panel
Open dashboard
Comparison

evanflow vs Autonomous Tool Factory

evanflow is a plugin bundle for AI coding tools published by evanklem. Marketplaces we read that list it: 2 (Claude Code: claude-plugins-community, Community GitHub marketplaces). Autonomous Tool Factory is an MCP server published by lorenestinfinite-maker. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-18. 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

Where each is published
MarketplaceevanflowAutonomous Tool Factory
Claude Code: claude-plugins-community Listed
Version: 1.0.0
Forks (GitHub): 18
Stars (GitHub): 418
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.1.0
No figure published
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

evanflow vs Autonomous Tool Factory
FactevanflowAutonomous Tool Factory
Marketplaces that list it (differs)2 (better)1 (worse)
Stars (GitHub) (differs)418No figure on GitHub
Forks (GitHub) (differs)18No figure on GitHub
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleRemote server (agency-backend-bbdk.onrender.com/mcp)
Transport (differs)Not statedStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Hooks it runs (differs)1Not published
Parts of the bundle (differs)19Not a bundle
Licence (differs)MITNot stated
Repository (differs)github.com/evanklem/evanflowNot stated
Changes in the last 7 days (differs)20
First seen2026-10-112026-10-11
Endpoint at the last check (differs)no remote endpoint we checkAnswered with HTTP 404 (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

evanflow

In its own words, on Claude Code: claude-plugins-community:

A TDD-driven iterative feedback loop for software development. 16 cohesive Claude Code skills walk an idea from brainstorm → plan → execute → tdd → iterate, with checkpoints throughout.

Autonomous Tool Factory

In its own words, on Official MCP Registry:

Autonomous factory that finds real developer pain points and builds small paid AI tools to fix them.

How to run each

evanflow As a Claude Code plugin

Claude Code
/plugin marketplace add anthropics/claude-plugins-community
/plugin install evanflow@claude-community

Autonomous Tool Factory As a remote MCP server

Claude Code
claude mcp add --transport http tool-factory https://agency-backend-bbdk.onrender.com/mcp/

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Only Autonomous Tool Factory 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

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

What it can do: evanflow · What it can do: Autonomous Tool Factory · 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 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