Dev Log #1: Building in Public with MCP

What We're Building

OmniVocal is a tool that lets you publish blog posts to multiple platforms simultaneously via a single API call — or directly from your AI assistant using MCP (Model Context Protocol).

This post is being published via the OmniVocal MCP server, running locally during development. The same flow works in production.

The Stack

• Cloudflare Workers — edge API, zero cold starts
• D1 — SQLite at the edge for posts, channels, API keys
• MCP server — exposes broadcast_post and list_credentials tools
• Adapters — per-platform publish logic (Hashnode, dev.to, Medium, GitHub, Bluesky)

Why MCP?

The interesting thing about building an MCP server for content distribution is that it collapses the workflow. Instead of:

1. Open dashboard
2. Paste content
3. Select platforms
4. Click publish

You just describe what you want published in chat and the agent handles the rest — including formatting differences per platform.

What's Next

• Paddle billing integration
• Medium and GitHub channels
• Scheduling support (Solo plan)

More dev logs coming as we build.