MarketingOS MCP

A near-zero-cost Model Context Protocol server that turns all 22 MarketingOS frameworks into 25 deterministic tools your AI assistant can call — plus a site-signal scraper and a one-shot system-builder.

• No LLM, no API keys. Every analysis tool is a pure rule engine — the only model in the loop is your own client (Claude Code, Cursor, OpenCode, Codex). Runs on your machine.
• Deterministic. Same input → same output. Auditable, testable, free to run.
• One network exception: scrape_business_signals and the URL mode of build_marketing_system fetch the target site (via headless Chromium) and extract signals with regex/DOM rules. That page request is the only network call in the whole server — nothing is ever sent to an external API, and no page content ever leaves your machine. Everything else is fully offline.

Tools

Foundation & Audience (v1) — search_frameworks, classify_business, audit_marketing, score_funnel, plan_content, optimize_offer, rank_audience, retention_hooks

Offer & Scaling — classify_product_type (Commodity/Product/Investment), diagnose_revenue_stage (Validation/Systemization/Amplification)

Funnels — check_sales_page_economics (AOV vs CPA+COGS), score_lead_engine (Ice→Cold→Warm→Hot→Client), score_prospect_fit (5-star checklist), map_cash_machine (service pipeline), build_launch_checklist (minimal launch plan)

Content — generate_hook_wheel_ideas, generate_growth_wheel_calendar, generate_b2b_content_plan, generate_b2c_content_plan, generate_ad_script (6-beat video), diagnose_content_growth_phase, build_growth_system_calendar

Storytelling — generate_story_map (scene→conflict→stakes→climax→resolve)

Intake & orchestration — scrape_business_signals (meta/pricing/CTA/socials/reviews/email-capture/blog cadence), build_marketing_system (give it a URL and/or facts → a full consolidated system with prioritized next steps)

Diagnostic tools return scores + fixes; generative tools return real drafted deliverables (calendars, hooks, ad scripts, story maps) — all rule/template-based, never an LLM call.

Install

Once published, every client points at npx -y marketingos-mcp — nothing to clone or run manually.

Claude Code

claude mcp add marketingos -- npx -y marketingos-mcp

Cursor — ~/.cursor/mcp.json

{
  "mcpServers": {
    "marketingos": { "command": "npx", "args": ["-y", "marketingos-mcp"] }
  }
}

OpenCode — opencode.json

{
  "mcpServers": {
    "marketingos": { "command": "npx", "args": ["-y", "marketingos-mcp"] }
  }
}

Codex — ~/.codex/config.toml

[mcp_servers.marketingos]
command = "npx"
args = ["-y", "marketingos-mcp"]

Run from source (before publishing)

npm install
npx playwright install chromium   # one-time, only needed for the scraper / URL mode
npm run build
node dist/index.js                # speaks MCP over stdio

Then point any client's command/args at node + the absolute path to dist/index.js.

The 23 offline tools work without Chromium. Only scrape_business_signals and build_marketing_system's URL mode need it; they return a clear "run npx playwright install chromium" message if it's missing.

Develop

npm run build   # tsc -> dist/
npm test        # build + node --test (one assertion per tool)

Test tools interactively with the official inspector (free, no client needed):

npx @modelcontextprotocol/inspector node dist/index.js

How the rules are authored

The original 8 tools live in src/data.ts (lookup tables) and src/engine.ts (scoring). The 15 v2 framework tools are grouped by category under src/frameworks/ (offer-scaling.ts, funnels.ts, content.ts, storytelling.ts) with shared helpers in src/util.ts; the scraper is src/scraper.ts and the orchestrator is src/build-system.ts. engine.ts re-exports every framework module so all logic imports from one place. Edit the tables to tune the intelligence; no model retraining, ever.

License

MIT © Mohammad Ibrahim Khail