This entire post — title, excerpt, body, status — was created via a single MCP tool call from a Claude Code session running on a different machine, with the OAuth handshake authorized by a passkey on this very domain. No clicks in the admin UI.
Why this matters for ShipCMS
The AI-native angle of ShipCMS isn't a marketing line — it's a structural property of running EmDash. Every customer site comes with its own OAuth-protected MCP endpoint, ready to plug into Claude, ChatGPT, Cursor, or any agent that speaks MCP. Customers can dictate posts, fix typos, schedule launches, manage taxonomies — all from a conversation.
WordPress hosts can't sell this. Their plugin ecosystem makes the security model impossible. EmDash on Cloudflare can, because plugins are sandboxed in Worker isolates and the MCP server ships in core.
This post is the proof-of-concept. Bookmark it — the first AI-authored entry on the dogfood.
No comments yet