The pitch
Every CMS operation — list types, create content, draft pages, set workflow states, run builds — is exposed as a tool. Drop the StaticOwl MCP into Claude Desktop and you can drive the product from a chat window.
Why this is more than a gimmick
Most "AI in your CMS" features are sidebars: a draft button, an inline rewrite, a search box. They sit on top of a closed CMS surface. You can't ask the AI to "find all FAQ pages with the old disclaimer, draft a rewrite using the new wording, and set them to review state" without a custom flow because the AI has no tool surface.
MCP changes that. Once the CMS is a tool surface, the AI agent can compose tools. The above is one prompt.
How we use it
This site
Most of these marketing pages were authored through the MCP. Same tools you'll get. We didn't have a UI button for "create 14 documentation pages from these markdown files" — but we did have a tool surface, and Claude was happy to drive it.
Voice profile + tool calls
Every draft, every edit, every email follows your brand tone. Configure once.
Content migration
Drop a Notion export. The agent matches sections to your content types, drafts a hierarchy of pages, lets you approve each. The most painful CMS task — re-keying — becomes a 10-minute review.
Site Health
The agent runs an audit and proposes fixes per issue. You approve in a click.
What you have to know
- MCP is a public standard. Not vendor-locked.
- The MCP key is scoped (per-site, TTL, rate-limited). Not "give the AI admin keys".
- AI-authored content goes through the same review pipeline as human-authored.
- Voice profile clamps prompts. Less off-brand output. (Not zero. Always review.)