Asset Factory

Agentic pipeline that transforms ideas to revenue — for solo founders and bootstrappers.

npx -y asset-factory-mcp

Why Asset Factory?

Most MCP servers give you one tool. A GitHub integration. A database query. A Slack bot.

Asset Factory gives you 42 tools that work as a pipeline — the entire playbook from raw idea to validated revenue, running inside the AI client you already use.

• No more blank-page paralysis. Start with scout and the system tells you exactly what to do next, every step of the way.
• Every stage feeds the next. Buyer research flows into offer design. Offer design flows into campaign copy. Campaign copy flows into validation. Nothing is wasted.
• Math before assets. Unit economics are validated before you build anything. You'll never spend weeks building an offer that can't work at your budget.
• Test ideas for $50, not $5,000. rapid_test gives you signal in 3-5 days with a landing page and paid traffic — before you commit to the full pipeline.
• Your AI becomes a co-founder, not a chatbot. It doesn't just answer questions. It executes a structured business system with you.

Install

npm install -g asset-factory-mcp

Or run directly without installing:

npx -y asset-factory-mcp

Quick Start

Claude Desktop

Add to your claude_desktop_config.json:

{
  "mcpServers": {
    "asset-factory": {
      "command": "npx",
      "args": ["-y", "asset-factory-mcp"],
      "env": {
        "ASSET_FACTORY_PROJECT_DIR": "/path/to/your/project"
      }
    }
  }
}

Cursor

Add to your MCP settings (.cursor/mcp.json):

{
  "mcpServers": {
    "asset-factory": {
      "command": "npx",
      "args": ["-y", "asset-factory-mcp"],
      "env": {
        "ASSET_FACTORY_PROJECT_DIR": "/path/to/your/project"
      }
    }
  }
}

From Source

git clone https://github.com/ZionHopkins/asset-factory-mcp.git
cd asset-factory-mcp
npm install
npm run build
node dist/index.js

How It Works

Asset Factory is a two-layer tool system:

Layer A — 42 SOP Tools (read-only): Each tool validates prerequisites against pipeline-state.json, loads upstream context from previous stages, checks learnings.json for patterns, and returns full SOP instructions enriched with that context. Your AI executes the instructions.

Layer B — 3 Utility Tools (mutations): update_pipeline_state, save_asset, capture_learning. These handle all state writes and file creation. Your AI calls them after executing each SOP.

The Pipeline

Five entry points:

1. scout            → Full pipeline (research → offer → build → deploy → validate)
2. rapid_test       → Quick $50-100 test (signal in 3-5 days)
3. passive_deploy   → Marketplace assets (after research)
4. tournament       → Batch-evaluate 3-5 ideas through Layer 1 simultaneously
5. portfolio_triage → Rank existing pipelines by profit velocity, select top N

Full Pipeline Flow

LAYER 1 (Strategist):
  scout → autonomy → market_intel → research → build_blocks → stress_test → unit_economics

LAYER 2 (Builder):
  name_lock → platform + product → deploy → qa → validate_prep

LAYER 3 (Validator):
  validate_check (daily) → validate_decide → feedback → iterate

TRAFFIC (Paid):
  traffic_strategy → channels → creative_test → funnel_optimize → scale

ORGANIC GROWTH (runs parallel with paid):
  content_engine → content_repurpose → seo_c

... [View full README on GitHub](https://github.com/ZionHopkins/launch-engine-mcp#readme)