Showdev time. I'm Aaron, and I just shipped SocialRoster (https://socialroster.dev) — a calendar scheduler for TikTok, Instagram, YouTube and Facebook, built for people who batch-produce short-form video. Import up to 50 clips, caption them, space them 1–24 hours apart, done.
The part I think this crowd will appreciate: instead of bolting on an "AI feature," I exposed the whole product as an MCP server. It uses OAuth 2.1 with PKCE and dynamic client registration — no API keys pasted into chat, no shared passwords. Two scopes: read (accounts, queue, plan) and write (drafts, scheduling, publishing). 15 tools total, including a bulk schedule_batch.
Hardest lesson so far: every platform's "publish" means something different. TikTok requires posts to be reviewed and published in-app, so my connector flatly excludes TikTok from instant publish and says so in the docs. Modeling each network's constraints as pre-flight checks beat four hand-rolled integrations.
It's $19.99/mo for 200 posts, $39.99 uncapped, 3-day free trial. Questions about the MCP auth flow very welcome — DCR in production has some sharp edges I'd happily compare notes on.
Top comments (1)
Treating each network's publish rules as pre-flight checks makes a lot of sense. Finding out at publish time that TikTok wants an in-app review is the kind of surprise that makes people stop trusting a scheduler, so refusing up front and saying why in the docs is the friendlier behavior.
On the DCR sharp edges: how are you handling cleanup of registered clients? If every assistant session can register itself, I'd expect a pile of abandoned client records fairly quickly. Do you expire unused ones, or tie each client to the user who approved the consent screen and let them revoke it from settings?