onlineitbd

Publishing this blog with an MCP server

1 min read onlineitbd team

Seed post — replace with your own. This is clearly-marked sample content, and doubles as the article published through the automation pipeline demo.

This site exposes its own MCP server. That means an assistant like Claude can connect to it directly and operate the blog: create a draft, edit it, schedule it, and publish — which commits Markdown to the repo and triggers a rebuild.

The pipeline

  1. Draft — posts.draft creates a new Markdown file with draft: true.
  2. Review — the draft renders on a preview deploy; edits go through posts.edit.
  3. Publish — posts.publish flips draft to false and commits.
  4. Deploy — deploy.trigger kicks a rebuild; deploy.status reports back.

No third-party SaaS automation sits in the middle — just the site’s MCP server, git, and a schedule. See /docs/automation.md for the exact recipe.