The MCP ecosystem is moving fast enough that a server shipping today is already competing with dozens that shipped last week. But most indie builders have no distribution infrastructure — one Reddit post, maybe a Dev.to article, then silence while the project quietly rots.
I built marketing-pipeline because I kept watching this happen to my own tools. The problem isn't quality. It's that consistent distribution requires daily decisions I don't want to make.
Onboarding a new project takes one command:
marketing onboard --name my-tool --repo owner/repo --kind mcp-server
That fetches the README, sends it to Claude, and writes a projects.yml entry with the problem, a fact bank, and a set of rotation angles. From there, a daily GitHub Actions cron at 14:00 UTC picks the least-recently-used angle, drafts a post for whichever channel is up in the rotation, and publishes it — Bluesky, Mastodon, Dev.to, Hashnode, plus directory listings on MCP Registry, Smithery, and Glama for servers.
The kind field matters here. mcp-server routes to MCP-specific directories. claude-skill targets awesome-claude-code. browser-extension hits Chrome Web Store, Firefox AMO, and Edge Add-ons. One config field, different distribution paths.
The part I spent the most time on was the anti-slop gate in pipeline/antislop.py. It hard-rejects specific tokens before anything gets published: 'excited', 'game-changer', 'unlock', 'empower', 'AI-powered', emoji, hashtags, exclamation points, rhetorical questions. Most auto-generated marketing reads like a press release written by someone who has never used the tool. The gate doesn't fix that entirely, but it eliminates the worst tells.
Per-channel length limits are enforced too — Bluesky at 300 chars, X at 280, Dev.to/Hashnode between 150 and 400 words — so the same post draft doesn't get published verbatim everywhere.
One honest limitation: awesome-claude-code submissions can't be automated. Their rules require a human to submit via their GitHub issue form. The pipeline generates the payload; you submit it once.
github.com/robertnowell/marketing-pipeline
Top comments (0)