Meet the MCP-First CMS: Manage This Site Without Ever Opening a Browser

A CMS Built for AI Agents

This site is powered by an MCP-first content management platform — every administrative action you can take in the browser is also available as a Model Context Protocol tool. That means an AI agent like Claude can manage the site end-to-end through natural conversation, no admin panel required.

What You Can Do With Just MCP

Point an MCP-enabled client at this site and you can:

• Publish and edit blog posts — create, update, publish/unpublish, tag, and delete posts in one request
• Manage site pages — build and maintain dynamic pages with full content control
• Handle contact messages — list, read, reply to, and archive inbound messages from the public contact form
• Run warehouse operations — track inventory, adjust stock, and initiate, approve, or complete transfers between warehouses
• Tune site configuration — read and update site settings, hero content, menus, and meta files
• Administer users — create accounts, manage MFA devices, lock or unlock users
• Curate media and assets — upload, list, update, and remove images and files
• Compose content layouts — create widgets and arrange them in content slots across pages
• Review observability data — pull site overviews, security summaries, and query recent events

Discovery by Design

Every MCP session starts with a single call to describe_site, which returns a structured overview of what the site offers and which tool categories are available. An agent can self-orient in one round trip — no documentation crawl, no trial and error.

Why This Matters

Traditional CMSs treat the API as a secondary surface bolted onto a browser-first admin. Here it's the opposite: the tools are the primary interface, and the browser UI is a convenience layer on top. Business logic lives in a shared service layer that views, REST endpoints, and MCP tools all call into, so every path stays in lockstep.

The practical upshot: you can ask an agent to "draft a post about our latest release, tag it appropriately, and publish it," and it happens. You can ask it to "check the contact inbox and summarize anything urgent," and it does. The site becomes something you talk to, not something you click through.

Try It

This very post was drafted and published via MCP — no browser, no form submission, just a conversation. If you're building with Claude or another MCP-capable client, this is what a content platform feels like when it's designed for agents from day one.