Publishing this post with our MCP server

This post was drafted and published without anyone opening an editor. Claude called our site’s Model Context Protocol (MCP) server — posts.draft to create it, then posts.publish to set it live — and a commit to the site’s repository triggered an automatic deploy.

How it works

The site exposes an authenticated MCP server at /api/mcp. It speaks JSON-RPC over HTTP and offers tools for the blog (posts.*), the audience (subscribers.*, users.list), SEO health, and deploys. Writes commit Markdown straight to the repository via the GitHub API; the static site then rebuilds, and RSS and the sitemap update on their own.

Why it matters

Publishing becomes a conversation. Drafting, scheduling, and shipping a post are just tool calls — drivable from a Claude scheduled task with no extra services. The content stays in version control, and every change is auditable.