I Gave the Website More Power. What Could Possibly Go Wrong?

The new MCP server for the website is up and running, which means my devlog workflow is about to involve considerably less copying, pasting, and wondering which window I was supposed to be copying into.

Naturally, the first thing I'm doing is asking it to help post an update about itself.

I'm sure that's how all the reassuring AI stories start.

The old copy-and-paste obstacle course

Until now, getting a development update onto the website looked something like this:

Notepad++ notes → ChatGPT → Copy/paste post content → Copy/paste metadata → Generate header image → Upload image → More copying and pasting → Finally publish.

Somewhere in there, I would usually remember another field that needed filling in. Because apparently writing the actual post wasn't enough of an activity on its own.

There's a lot of unnecessary back and forth for something that starts as a few notes about what I've been working on.

A much shorter journey from notes to post

The new setup lets ChatGPT work directly with the website through MCP. In normal-person terms, that means it can use tools I've provided to create a draft and fill in the relevant bits instead of handing everything back to me for another round of clipboard gymnastics.

Once the tools are finished, the idea is for the workflow to look more like this:

Notepad++ notes → ChatGPT → Review draft on website → Publish.

That includes figuring out which games I'm talking about, setting the related game fields when appropriate, sorting out the post details, and getting a proper header image into place.

This particular update is about the website itself, so there isn't a game to attach. A small but useful test of whether the system knows when to leave something alone.

The first test: post while I'm elsewhere

As a matter of fact, this should be the first post created using the new workflow. The plan is to schedule it for about 30 minutes after creation, while I should hopefully be sitting at the doctor's office.

If you're reading this when it's supposed to appear, then at least this part of the experiment worked.

If the header image looks like a menacing server labelled SKYNET, wrapped in chains and locked in a cage... that's just sensible equipment storage.

Probably.

For the three of you who like me

I promise that making updates easier doesn't mean I'm going to start spamming them. The goal is to spend less time administering posts and more time making things worth posting about.

But if you'd like to keep up, there's now a subscribe option in the website header and footer.

Nothing fancy. Just a new-post update when I post something.

For the three of you who like me, this should be very convenient.

Anyway, here goes nothing. Let's see whether the new workflow behaves itself.