Launch Engine — Business Execution OS MCP server
io.github.ZionHopkins/launch-engine·v1.1.0·4 starsAgentic pipeline — 39 tools from idea to revenue for solo founders.
4 stars
Reviews
Write oneNobody has reviewed Launch Engine — Business Execution OS yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
Launch Engine — Business Execution OS tools
No tool declarations could be read from the package source. They show once the server is installed.
Public scan report
scanner v0.1.9 · 2026-09-27 · same rubric, same numbers if you re-run it
- Code scan164 source files scanned25/25
- –Live reliabilityno gateway calls yet and no remote to proben/a
- –Tool poisoningtools not inspected (local package is not executed); not countedn/a
- Auth qualitylocal package, no credentials required12/15
- Maintenancelast push 177 days ago8/15
- Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
How Launch Engine — Business Execution OS compares
Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 82/100
- higher than 63% of 48,255 servers
- GitHub stars
- 4
- more than 82% of 28,688 servers
Install Launch Engine — Business Execution OS in Claude Code, Cursor or VS Code
Runs npx -y launch-engine-mcp on your machine. Read the scan report first; the gateway never runs local packages.
claude mcp add launch-engine -- npx -y launch-engine-mcp
What the publisher says
From the Launch Engine — Business Execution OS repository's README, as published. We do not edit it. Read it on GitHub
Asset Factory
Agentic pipeline that transforms ideas to revenue — for solo founders and bootstrappers.
npx -y asset-factory-mcpWhy 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-mcpOr run directly without installing:
npx -y asset-factory-mcpQuick Start
Claude Desktop
Add to your claudedesktopconfig.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.jsHow 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): updatepipelinestate, saveasset, capturelearning. 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 NFull 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 → scaleShortened. The full README is on GitHub.
Nothing above is checked by us. What we check is on the safety report.
Launch Engine — Business Execution OS: common questions
- Is Launch Engine — Business Execution OS MCP server safe?
- Mostly: it is graded B (82/100). Read the Launch Engine — Business Execution OS safety report
- How do I install Launch Engine — Business Execution OS?
- It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
- Does Launch Engine — Business Execution OS need an API key?
- No secret keys are declared. It reads 1 setting from the environment.
- Is Launch Engine — Business Execution OS maintained?
- The last commit was 214 days ago (2026-04-04). The latest release is v1.1.0.
- How does Launch Engine — Business Execution OS compare with other MCP servers?
- safety score 82/100 (higher than 63% of 48,255 servers); github stars 4 (more than 82% of 28,688 servers). Full comparison.