mobile-growth-mcp

MCP server for mobile growth & user acquisition. Connects your LLM to a curated knowledge base of ad optimization insights and a library of analytical skills (campaign audits, fatigue detection, weekly diagnostics). Focused on subscription apps.

For Meta Ads data, use Meta's official Meta Ads MCP / AI connector. The skills here interpret what it returns. This MCP intentionally does not ship Meta API tools — keeping users on the official path.

For Google Ads, this MCP includes direct API integration (your tokens stay on your machine).

Quick Start

Claude Desktop

1. Open the config file:

• macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
• Windows: %APPDATA%\Claude\claude_desktop_config.json

1. Add this to the file (create it if it doesn't exist):

{
  "mcpServers": {
    "mobile-growth": {
      "command": "npx",
      "args": ["-y", "mobile-growth-mcp"],
      "env": {
        "API_KEY": "me_YOUR_KEY"
      }
    }
  }
}

1. Replace me_YOUR_KEY with the API key from your account admin.
2. Restart Claude Desktop.
3. To analyze Meta data, also install Meta's official Meta Ads MCP — its connector data flows through your LLM into the skills here.

Note: Use the JSON config file, not the "Add custom connector" UI in Claude Desktop. That UI is for remote servers — this MCP runs locally.

Other clients

Same JSON format as above.

Alternative: CLI args

{
  "mcpServers": {
    "mobile-growth": {
      "command": "npx",
      "args": ["-y", "mobile-growth-mcp", "--api-key=me_YOUR_KEY"]
    }
  }
}

No API key?

The server still starts — you get the Google Ads tools (if configured) and a connection_status tool that explains what's missing and how to fix it.

How It Works

The MCP server runs as a local process on your machine, started by your MCP client (Claude Desktop, Cursor, etc.).

• Knowledge base (remote) — curated expert insights hosted on our server, accessed via your API key
• Google Ads API (local) — calls happen directly from your machine using your tokens
• Meta Ads data — sourced from Meta's official AI connector, not from this MCP

Your machine                          Our server
+---------------------------+         +------------------+
| MCP client (Claude, etc.) |         |                  |
|   |                       |         |  Knowledge base  |
|   v                       |  API    |  (insights,      |
| mobile-growth-mcp --------+--key--->|   search,        |
|   |                       |         |   embeddings)    |
|   |                       |         +------------------+
|   v
| Google Ads API (your tokens stay local)
|
| (Meta Ads data: comes via Meta's official AI connector,
|  not through this MCP)
+---------------------------+

Your ad platform tokens are used locally and are never sent to our servers.

What You Get

Knowledge base tools — search, browse, and retrieve expert insights on creative strategy, audience targeting, scaling, bid optimization, and more.

Google Ads API tools — pull campaigns, ad groups, assets, performance insights, and network mix directly from your Google Ads account.

Analytical skills (MCP prompts) — KB-grounded methodologies for ad fatigue, weekly performance, creative health, placement audits, audience composition, architecture reviews, campaign comparisons, attribution analysis, and full account audits. The Meta-flavored skills consume data from Meta's official AI connector or pasted CSVs.

Tools

Report Prompts (Skills)

Each Meta-flavored prompt takes an ad_account_id and walks the LLM through a structured analysis. Data comes from Meta's official AI connector or pasted CSV exports.

All reports reference specific knowledge base insight IDs so recommendations are grounded in expert knowledge, not generic advice.

Resources

Development

Setup

git clone https://github.com/kubachour/mobile-growth-mcp.git && cd mobile-growth-mcp
npm install
npm run build

Environment

cp .env.example .env
# Fill in API_KEY (get from admin)
# For Google Ads tools: run `npx mobile-growth-mcp auth google` to set up
# For ingestion/admin: also set SUPABASE_URL, SUPABASE_SERVICE_ROLE_KEY

Adding Insights

1. Create or edit JSON files in data/insights/
2. Follow the schema in packages/shared/src/types.ts
3. Run npm run ingest
4. Embeddings are generated automatically server-side

Publishing

cd packages/mcp-server
npm version patch
npm publish --access public

Project Structure

packages/shared/       — Types, Supabase client
packages/mcp-server/   — MCP server (published as mobile-growth-mcp)
  src/google/          — Google Ads API client
  src/tools/           — All MCP tools (KB + Google Ads)
  src/resources/       — MCP resources (vocabulary, instructions)
packages/ingestion/    — CLI to validate & upsert insight JSONs
data/insights/         — Curated insight JSON files
skills/                — Skill markdown files (analytical methodologies)
supabase/migrations/   — SQL migrations
supabase/functions/    — Edge Functions (embed, search)

License

This project uses a dual license:

• Code (everything except skills/) — MIT License
• Skill prompts (skills/*.md) — CC BY-NC-SA 4.0 — you can read, learn from, and adapt them for non-commercial use, but you can't use them to build a competing commercial product

The curated knowledge base is not included in this repository.