Launch Engine — Business Execution OS
Run a structured, agent-driven pipeline from first idea through launch and early revenue without juggling dozens of disconnected prompts.
Overview
Launch Engine is an MCP server for the Launch phase that exposes 39 stateful tools to move a solo founder from idea to revenue inside a local project directory.
What is this MCP server?
- 39 MCP tools covering an end-to-end solo-founder pipeline from idea to revenue
- Persists pipeline state and assets via LAUNCH_ENGINE_PROJECT_DIR and pipeline-state.json
- stdio npm package launch-engine-mcp v1.1.0 for Claude Code, Cursor, and Codex
- Business Execution OS framing—planning, build tasks, and launch steps in one agent surface
- Local project directory model keeps artifacts on your machine rather than a black-box SaaS
- 39 MCP tools documented in server metadata
- Server version 1.1.0 (launch-engine-mcp npm package)
- stdio transport via npm registryType
Community signal: 3 GitHub stars.
What problem does it solve?
Solo builders lose weeks re-teaching agents their business context and never finish a coherent path from idea to first dollars.
Who is it for?
Indie founders who want one MCP-backed execution pipeline with local state and many launch-phase tools in a single stdio server.
Skip if: Teams that need enterprise PM integrations, fully hosted GTM suites, or a single-purpose API wrapper with no pipeline model.
What do I get? / Deliverables
After install, your agent can read and advance a persisted launch pipeline with on-disk assets instead of one-off chat plans.
- pipeline-state.json progress across launch phases
- Project assets folder managed alongside pipeline state
- Agent-invokable launch and revenue execution steps via 39 tools
Recommended MCP Servers
Journey fit
Launch Engine is shelved under Launch because its stated outcome is revenue and go-to-market execution, even though its 39 tools touch earlier phases. Distribution fits the canonical shelf: positioning, launch assets, and outbound motions that turn a built product into paying customers.
How it compares
Journey-wide MCP toolkit with 39 tools, not a single-phase agent skill or a raw skills.sh playbook.
Common Questions / FAQ
Who is Launch Engine for?
Solo and indie founders using Claude Code, Cursor, or Codex who want an agent-native pipeline from idea to revenue with local project state.
When should I use Launch Engine?
Use it when you are ready to execute—not just ideate—and want persisted pipeline steps, assets, and tools across validate, build, ship, and launch work.
How do I add Launch Engine to my agent?
Install the npm stdio package launch-engine-mcp, set LAUNCH_ENGINE_PROJECT_DIR to your project root, and register the MCP server in your agent’s MCP config.