Strategist · Designer · Operator
Threads scheduling that an AI can drive — drafting and publishing through MCP, not a dashboard.
Win: First product with real users, and an MCP surface so an agent runs it.
A Threads scheduling platform: drafts, bulk drafting, scheduling, publishing and post analytics. The difference from every other scheduler is that it exposes an MCP server, so the whole workflow can be driven from a chat session instead of a dashboard.
The platform, plus the MCP layer that makes it agent-operable. Two things I did not skip and should not have: a single architecture document that is the source of truth for structure and deploy, and a written API-call analysis, because a scheduler that trips a rate limit at the wrong moment silently stops being a scheduler. The read and write paths are split by design and that split is documented rather than discovered later.
Live at bestthriends.com and tracked as a real property. My first product with real users — it never carried pricing — and the first place I built an MCP surface, the pattern I have used on everything since.