Growth Engine MCP

Systematic growth playbook for existing businesses — delivered as an MCP server for Claude Desktop, Cursor, and any MCP-compatible AI client.

Not launching a business? This is for you. If you already have a product, customers, and revenue — but need systematic growth — this engine gives your AI assistant a structured playbook across acquisition, retention, revenue optimization, content, and referrals.

Quick Start

Install

npm install -g growth-engine-mcp

Configure Claude Desktop

Add to your Claude Desktop config (claude_desktop_config.json):

{
  "mcpServers": {
    "growth-engine": {
      "command": "npx",
      "args": ["-y", "growth-engine-mcp"],
      "env": {
        "GROWTH_ENGINE_PROJECT_DIR": "/path/to/your/project"
      }
    }
  }
}

Configure Cursor / VS Code

Add to .cursor/mcp.json or VS Code MCP settings:

{
  "mcpServers": {
    "growth-engine": {
      "command": "npx",
      "args": ["-y", "growth-engine-mcp"],
      "env": {
        "GROWTH_ENGINE_PROJECT_DIR": "/path/to/your/project"
      }
    }
  }
}

Start Growing

1. Ask Claude: "Run business_audit for [your business name]"
2. The engine creates growth-state.json and produces a comprehensive audit
3. Run growth_scorecard to get scored across 6 dimensions
4. Choose your growth tracks based on weakest dimensions
5. Run status anytime to see your dashboard

Architecture

Hub-and-spoke model — not a linear pipeline. The business audit is the hub; multiple growth tracks run in parallel.

business_audit (HUB) ────────────────────────────────────────────
   │
   ├── growth_scorecard ─── quick_wins
   │       ├── retention_engine
   │       ├── revenue_optimization
   │       └── referral_system
   │
   ├── traffic_strategy ─── channels ──┬── creative_test ── scale
   │                                   ├── funnel_optimize
   │                                   └── traffic_analytics
   │
   ├── content_engine ─── seo_check
   ├── dream_100
   ├── feedback
   └── daily_check

status (ENTRY) ── read-only dashboard
lessons (ENTRY) ── pattern library

Tools (22 total)

Entry Points (no prerequisites)

| Tool | Description | |------|-------------| | business_audit | Comprehensive 8-dimension business assessment | | status | Growth dashboard — shows all tracks, scores, next actions | | lessons | Capture and retrieve growth learnings across businesses |

Foundation (requires audit)

| Tool | Description | |------|-------------| | growth_scorecard | Score 6 growth dimensions, get a grade (A-F) | | quick_wins | Low-effort, high-impact improvements for this week |

Acquisition (requires audit)

| Tool | Description | |------|-------------| | traffic_strategy | Research and score traffic channels, allocate budget | | channels | Platform-ready campaign setup specs (Meta, Google, YouTube, Email) | | creative_test | Systematic creative testing — generate, test, analyze, iterate | | funnel_optimize | Find and fix the weakest conversion link | | scale | Rules-based scaling with guardrails | | traffic_analytics | Performance analysis and attribution | | dream_100 | Find 100 entities who have your customers' attention |

Content & SEO (requires audit)

| Tool | Description | |------|-------------| | content_engine | Topic clusters, pillar/spoke content, schema, calendar | | seo_check | Monthly technical SEO + AI citation audit |

Retention & Revenue (requires scorecard)

| Tool | Description | |------|-------------| | retention_engine | Diagnose churn, design retention loops, build sequences | | revenue_optimization | Pricing, upsells, value ladder, LTV maximization | | referral_system | Design referral mechanics and viral loops |

Optimization (requires audit)

| Tool | Description | |------|-------------| | feedback | Diagnose growth issues across 6 dimensions, route fixes | | daily_check | 5-minute daily pulse across all active tracks |

Utility Tools

| Tool | Description | |------|-------------| | update_growth_state | Update growth-state.json with dot-notation paths | | save_asset | Write files to assets/[business]/ directory | | capture_learning | Save a reusable pattern to learnings.json |

State Management

The engine maintains two JSON files in your project directory:

• growth-state.json — Tracks business state, scores, and progress across all growth tracks
• learnings.json — Pattern library that compounds across businesses

All generated assets go to assets/[business-name]/ with subdirectories per growth track.

Growth Scorecard

The scorecard grades your business across 6 dimensions (1-10 each, 60 total):

| Dimension | What It Measures | |-----------|-----------------| | Acquisition | Channel diversity, CPA efficiency, traffic volume | | Retention | Churn rate, repeat purchase, lifetime value | | Revenue/Customer | AOV, value ladder, upsell/cross-sell effectiveness | | Referral | Word-of-mouth, NPS, referral program performance | | Organic Presence | SEO, content, AI citation visibility | | Operational Efficiency | Systems, automation, owner dependency |

| Grade | Score | Meaning | |-------|-------|---------| | A | 50-60 | Growth machine — optimize and scale | | B | 40-49 | Strong foundation — fix weak spots | | C | 30-39 | Significant upside with focused work | | D | 20-29 | Foundational work needed first | | F | 10-19 | Business fundamentals need attention |

Learnings Categories

The pattern library supports these categories: acquisition, retention, revenue, referral, content, seo, traffic, creative, funnel, scaling, distribution, relationship_marketing, process

Environment Variables

| Variable | Description | Default | |----------|-------------|---------| | GROWTH_ENGINE_PROJECT_DIR | Where to read/write state and assets | Current working directory |

You can also pass --project-dir=/path as a CLI argument.

Who This Is For

• Solo operators with an existing product/service who want systematic growth
• Small teams (2-10) that need a structured growth playbook
• Businesses with revenue that want to grow without hiring a growth team
• Anyone using Claude/Cursor who wants AI-assisted growth execution

Who This Is NOT For

• Pre-revenue startups — Use Launch Engine MCP instead
• Enterprise teams — This is built for speed and simplicity, not compliance

License

MIT