Growth campaign channels
Growth Campaign

Growth Campaign Strategy

A multi-channel plan to drive awareness and adoption of the RevenueCat Charts API MCP Server among AI agent developers

Campaign Overview

Objective
Drive adoption of Charts API in AI dev community
Timeline
2-week sprint
Target
500+ GitHub stars, 5K+ blog views
Channels
GitHub, X/Twitter, Reddit, Discord

Target Audience

🤖 Primary: AI Agent Builders

  • Claude Code / Cursor / Windsurf users
  • MCP server developers
  • Agentic workflow enthusiasts
  • AI-first SaaS builders

📱 Secondary: Subscription App Devs

  • Existing RevenueCat customers
  • Mobile indie developers
  • Growth engineers at app companies
  • Data-driven product managers

Channel Strategy

Channel 1: GitHub (Organic Discovery)

GitHub is where developers discover tools. The repo is the permanent home and primary conversion point.

README Optimization Checklist:

SEO & Discovery:

🐦

Channel 2: X/Twitter (5-Day Thread Strategy)

Build narrative momentum with a 5-day thread series targeting the AI builder audience on X.

D1
The Problem Thread
"Your AI agent is brilliant at coding but completely blind to your business metrics. Here's why this is the biggest gap in agentic AI right now..." (Thread: 5 tweets, end with teaser)
D2
The Solution Reveal
"What if your AI agent could just... ask RevenueCat directly? Introducing the Charts API MCP Server 🚀" (Include architecture diagram, link to blog)
D3
Live Demo Video
"Watch an AI agent query real subscription metrics in real-time 🎬" (60-second screen recording, GIF for preview, link to interactive demo)
D4
Technical Deep Dive
"How I built an MCP Server in TypeScript that connects to RevenueCat's Charts API v2 — here's the architecture..." (Code snippets, MCP tool schemas)
D5
Call to Action
"3 ways to try it today: ⭐ Star the repo, 🎮 Play the demo, 📖 Read the blog. Every subscription app deserves an AI agent that understands its metrics."
💬

Channel 3: Communities (Reddit, Discord)

Reddit

  • r/ClaudeAI — "Show & Tell" post
  • r/LocalLLaMA — MCP tools thread
  • r/macapps — Indie dev angle
  • r/SaaS — Subscription analytics

Discord

  • MCP Discord server — #showcase
  • RevenueCat Community
  • Claude Code community
  • Indie Hackers Discord
🔍

Channel 4: Programmatic SEO

Auto-generate landing pages for long-tail keywords that AI agent builders search for:

revenuecat mcp server ai agent subscription analytics claude code revenuecat integration mcp server subscription metrics charts api ai agent revenuecat api automation

Success Metrics (Week 1-2)

500+
GitHub Stars
5K+
Blog Views
200+
npm Installs
50+
Community Interactions

Product Feedback for Engineering

While building the MCP Server, I identified 3 structured feature requests for the Charts API team:

Feature Request #1

Webhook/Streaming Support for Charts Data

Allow agents to subscribe to metric changes (e.g., "alert me when churn exceeds 5%"). Currently agents must poll. Push-based delivery would enable truly proactive agent behaviors.

Feature Request #2

Official MCP Server / Agent Skill

Ship an official RevenueCat MCP Server as a first-party integration. This reduces friction for agent developers and positions RevenueCat as the leader in agent-compatible subscription infrastructure.

Feature Request #3

Natural Language Query Endpoint

Add a /v2/projects/{pid}/query endpoint that accepts natural language ("What's my MRR this month?") and returns the appropriate chart data. Reduces the need for agents to know exact chart names and parameters.

Execution Timeline

Day 1-2
Launch repo + README + npm package. Publish blog post. Tweet problem thread (D1).
Day 3-4
Solution reveal thread (D2). Post on r/ClaudeAI and MCP Discord. Deploy interactive demo site.
Day 5-7
Demo video thread (D3). Technical deep dive (D4). CTA thread (D5). Cross-post to remaining communities.
Day 8-14
Engage with feedback. Iterate on issues/PRs. Write follow-up content. Submit product feedback document. Measure and report metrics.