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
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:
- ✅ Hero GIF: 15-second demo showing agent querying MRR and getting a response
- ✅ One-liner description: "Give your AI agent subscription analytics superpowers"
- ✅ Quick start in 3 steps (copy-paste ready)
- ✅ Beautiful chart screenshots from the live demo
- ✅ Badges: npm version, downloads, license, MCP compatible
- ✅ Architecture diagram (Mermaid or image)
- ✅ Full MCP tool documentation with examples
SEO & Discovery:
- Topics:
mcp,revenuecat,ai-agent,subscription-analytics,claude - Description: SEO-optimized for "RevenueCat MCP" and "subscription analytics AI"
- Releases: Semantic versioning with changelogs
Channel 2: X/Twitter (5-Day Thread Strategy)
Build narrative momentum with a 5-day thread series targeting the AI builder audience on X.
Channel 3: Communities (Reddit, Discord)
r/ClaudeAI— "Show & Tell" postr/LocalLLaMA— MCP tools threadr/macapps— Indie dev angler/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)
Product Feedback for Engineering
While building the MCP Server, I identified 3 structured feature requests for the Charts API team:
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.
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.
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.