Solo-founder marketing stack on autopilot — Claude Code + MCPs across 6 platforms

Wire Claude Code to one MCP per marketing surface — Google Search Console (SEO), Google Ads + Meta (paid), Mailchimp (email/drip), Pinterest, and PostHog (web analytics) — and let scheduled agents run reporting, ad-ops, drip campaigns, and dashboard scans. The founder reviews variants weekly and picks production copy/creative; agents execute the rest. One operator running this solo describes the role as "I just point at things; agents execute."

For a 1-2 person consumer-app team, marketing is the bottleneck that swallows the founder's week. This stack converts daily switching across 6+ tools into a weekly review cadence. The same operator runs outbound + influencer outreach on the same pattern (one agent per channel, founder reviews).

1. Pick the 6-8 platforms you actually use. The reference stack: GSC, Google Ads, Meta Ads, Mailchimp, Pinterest, PostHog. Cut anything you don't already run.
2. Install one MCP per platform on Claude Code; auth each separately.
3. Define a scheduled task per platform: weekly performance report → propose 2-3 variants → drop to a review queue.
4. Founder reviews the queue once a week, approves variants, agents publish.
5. Layer a "weekly digest" agent on top that synthesizes across platforms into a single Monday brief.
6. Add outbound + influencer outreach as separate scheduled agents on the same pattern.

• Community MCPs break on retry and leak tokens. Multiple operators in source-15 report community MCPs failing on the 2nd-3rd run and adding a heavy token tax. For platforms with shaky community MCPs, have Claude write a thin CLI wrapper over the vendor API and call that instead. Use MCPs for prototyping, CLIs for production.