October 17, 2026
Publishing with Claude
A lot of clients ask me to make content changes on their website instead of using their CMS. I get it. I know all the code. I know what goes where. Also, I can use the power of AI and make multiple changes in seconds instead of minutes. It makes sense. But what if I told you that your own AI agent can already do the same?
It can read (and understand) all source code, and you can tell it what you want in plain language. It can write for you and make changes instantly. Amazing, right? It is like having me around 24/7, but then for free.
Setting it up is quite easy. Usecue CMS has an MCP server. MCP is a standard that lets an AI assistant use tools. In Claude, add a custom connector and enter its address: https://cms.usecue.com/mcp.php. You can find this URL in your account settings in the CMS. During onboarding, the CMS website shows an
allow dialog where you approve the connection. After that, Claude can see your sites and work on them.
I used this method to publish this post. First, I told Claude which site I wanted to work on. Then I asked for a blog post about this workflow, so Claude looked up what the site can store: two languages, the available shortcodes, and which files are writable. I have a certain tone of voice, so Claude listed my existing posts and read two recent ones to copy the front matter and my style. Finally, it wrote a new Markdown file with today’s date in its name, right where all my other posts live, and showed it to me.
And then it stopped. Nothing was live yet, because changes in this CMS stay unpublished until I ask for them to be published. Claude did the typing, I kept the final say. I reviewed it and decided I wanted to add an image, so I asked Claude. It gave me an upload link, and I uploaded my image. Claude found the file and added it to this very post, with a sentence to introduce it.
I love it. It is so effertless. I also really like the guardrails. The CMS only lets Claude write Markdown and YAML files. Raw HTML, JavaScript, CSS and shortcodes the site does not have are refused. So even if I ask for something silly, the assistant cannot break my website. It can only write content that my site accepts and every edit is stored in Git.
It also fits the idea behind my fastest CMS in the world: publishing should be effortless. A static site that rebuilds in under a second, plus an assistant that can make content changes instantly.
Do you want effortless website editing? Contact me.
Happy coding!
() Joost van der Schee