{"slug": "you-shipped-an-mcp-server-nobody-found-it-here-s-the-fix", "title": "You shipped an MCP server. Nobody found it. Here's the fix.", "summary": "A developer built marketing-pipeline, an open-source tool that automates distribution for indie projects, especially MCP servers. It handles directory submissions, social posting, and content rotation via a daily GitHub Actions cron, with an antislop gate to reject promotional language. The tool aims to solve the recurring distribution problem that kills most open-source projects.", "body_md": "The problem isn't quality. Most OSS tools die because the author posted once, got silence, and never had time to keep showing up. Distribution is a recurring job — directory submissions, social posts, content rotation across channels — and for most indie builders it's either skip it or do it manually every week forever.\n\nI built marketing-pipeline to handle the recurring part.\n\nOnboarding a project takes one command:\n\n```\nmarketing onboard --name my-tool --repo owner/repo --kind mcp-server\n```\n\nIt fetches the README, sends it to Claude, and writes the problem statement, facts, and content angles to `projects.yml`\n\n. From there, a daily GitHub Actions cron (`marketing cycle`\n\n, 14:00 UTC weekdays) rotates through projects × angles × channels, picks the least-recently-used angle, drafts a post, and publishes it.\n\nFor MCP servers specifically, the `kind`\n\nfield routes directory submissions to MCP Registry, Smithery, Glama, and PulseMCP automatically. Claude Code skills go to awesome-claude-code (the pipeline generates the payload; their rules require a human to submit via their GitHub issue form once per project — that one step can't be automated). Browser extensions route to Chrome Web Store, Firefox AMO, and Edge Add-ons.\n\nSocial posting covers Bluesky (≤300 chars), X (≤280), Mastodon (≤500), Dev.to, and Hashnode. Per-channel length limits are enforced in code.\n\nThe part I spent the most time on: an antislop gate in `pipeline/antislop.py`\n\nthat hard-rejects posts before they publish. Banned tokens include 'excited', 'game-changer', 'unlock', 'empower', 'AI-powered', emoji, hashtags, exclamation points, and rhetorical questions. Anything that reads like vendor copy gets killed before it touches an API.\n\nThe MCP/agent ecosystem moves fast. Most indie builders in it don't have distribution infrastructure — they have a README and a prayer. This is the infrastructure layer I wanted to exist.", "url": "https://wpnews.pro/news/you-shipped-an-mcp-server-nobody-found-it-here-s-the-fix", "canonical_source": "https://dev.to/palo_alto_ai/you-shipped-an-mcp-server-nobody-found-it-heres-the-fix-10b9", "published_at": "2026-06-26 11:00:05+00:00", "updated_at": "2026-06-26 11:03:51.484178+00:00", "lang": "en", "topics": ["developer-tools", "ai-agents", "large-language-models"], "entities": ["Claude", "MCP Registry", "Smithery", "Glama", "PulseMCP", "Bluesky", "X", "Mastodon"], "alternates": {"html": "https://wpnews.pro/news/you-shipped-an-mcp-server-nobody-found-it-here-s-the-fix", "markdown": "https://wpnews.pro/news/you-shipped-an-mcp-server-nobody-found-it-here-s-the-fix.md", "text": "https://wpnews.pro/news/you-shipped-an-mcp-server-nobody-found-it-here-s-the-fix.txt", "jsonld": "https://wpnews.pro/news/you-shipped-an-mcp-server-nobody-found-it-here-s-the-fix.jsonld"}}