My Blog Has an API for AI Now. No Keys, Just OAuth.
Webstead, the CMS that runs this blog, now has an MCP server built in. As of this morning it also does OAuth, so I connected it to Claude like any other connector. No API keys pasted anywhere, just a normal "log in and approve" flow.
The MCP server landed in #147 and the OAuth bits in #148.
What it can do
Claude can now:
- Search and read my posts
- Write drafts and hand me a preview link that works logged out
- Upload media
- Edit, publish, revert, and delete, with a confirm step for the destructive stuff
The rule baked into the server is simple: everything is a draft unless I say otherwise. Every change is a revision I can undo. That's what all the boring groundwork over the last couple weeks was for.
The first thing I had it do
I have a voice guide that Claude uses when it drafts stuff for me. It was mostly built from my old tweets, which turns out to be a problem. I'm a lot more crude on X than I am here.
So I had Claude read through my blog archive and fix it. The big finding: blog me is warmer and cleaner. Less swearing, almost no "lol", and I say "honestly" a lot. Fair.
The second thing
This post. Claude drafted it through the MCP server, I read the preview, and then I hit publish. If you're reading this, it worked. π
It's still early and I'm sure there are rough edges. Next up in this series: the bugs I had to fix before I'd let an AI anywhere near my site. After that, a deeper dive on the MCP server itself.
Comments
No comments yet.