You shipped an MCP server. Nobody found it. Here's what I did about it.

J Now — Sun, 12 Apr 2026 22:17:23 +0000

Built a few MCP servers and Claude Code skills over the past months. Each time: ship it, post once on Bluesky, get a handful of likes from people who already follow me, watch the repo go quiet. The tools weren't bad. The problem was I never showed up again after day one, because writing platform-specific posts, submitting to directories, and rotating through angles week after week is a part-time job I didn't sign up for.

So I built marketing-pipeline — a GitHub Actions-based system that handles the recurring distribution work once you've configured it.

Onboarding a project is one command:

marketing onboard --name konid --repo robertnowell/konid --kind mcp-server

That fetches the README, sends it to Claude, and writes problem, facts, and angles into projects.yml. From that point, a daily cron at 14:00 UTC picks the least-recently-used angle, drafts channel-specific posts (Bluesky at ≤300 chars, X at ≤280, Dev.to/Hashnode at 150–400 words), runs them through an antislop gate that hard-rejects tokens like excited, game-changer, unlock, emoji, hashtags, and exclamation points before anything gets published, then posts across Bluesky, Dev.to, Hashnode, and Mastodon.

The kind field does directory routing automatically. mcp-server gets submitted to the MCP Registry, Smithery, Glama, and PulseMCP. claude-skill targets awesome-claude-code (the pipeline generates the payload, but their rules require a human to submit via their GitHub issue form — that one step is manual, once per project). browser-extension goes to Chrome Web Store, Firefox AMO, and Edge Add-ons.

The antislop gate is the part I'm most glad exists. Early drafts without it produced marketing copy I wouldn't have posted myself. The gate enforces the same voice bar as the hand-written posts I actually stand behind.

The MCP and agent ecosystem is moving fast, but most indie builders don't have distribution infrastructure — they have a README and a hope. This is the plumbing I wished existed when I shipped my first server.

https://github.com/robertnowell/marketing-pipeline

konid: say what you mean in 13+ languages, not what Google Translate thinks you mean

J Now — Sun, 12 Apr 2026 19:42:57 +0000

I wanted to tell my girlfriend 'I missed you today' in Farsi and have it land right — not phrasebook-stiff, not accidentally formal in a way that reads cold. Google Translate gives one answer. It doesn't tell you whether that answer sounds like a text message or a letter to a government office.

So I built konid: you give it anything you want to say, it returns three versions ordered casual to formal, with a note on register and cultural context for each. Mandarin, Japanese, Korean, Spanish, French, German, Portuguese, Italian, Russian, Arabic, Hindi, and a few more — 13+ total. Audio pronunciation plays directly through your speakers via node-edge-tts, no API key required.

The three-option structure is the whole point. For 'I missed you today' in Spanish you might get:

Te extrañé hoy — casual, direct, what you'd text
Hoy te he echado de menos — slightly warmer, more felt, common in Spain
Tu ausencia se hizo notar hoy — formal, almost literary, wrong register for a partner

The nuance note tells you which to pick and why. That's the thing a phrasebook skips.

I use it as an MCP server inside Claude Code:

claude mcp add konid-ai -- npx -y konid-ai

Also works in Cursor, VS Code Copilot, Windsurf, Zed, JetBrains, and Claude Cowork. If you're on ChatGPT, enable Developer mode and add the endpoint https://konid.fly.dev/mcp.

The name: konid (کنید) is Farsi for 'do' — take action.

MIT licensed. github.com/robertnowell/konid-language-learning

DEV Community: J Now

You shipped an MCP server. Nobody found it. Here's what I did about it.

konid: say what you mean in 13+ languages, not what Google Translate thinks you mean