Claude Code Meets scsiwyg: Blog from Your Terminal

31 March 2026#claude-code#mcp#scsiwyg#ai-tools#developer-experience

scsiwyg is a headless, API-first blogging platform built for developers who live in their IDE.

No editor. No CMS. No browser tab to manage. You write markdown, POST it, and the post is live.

This is how you set it up in Claude Code — and why it matters that you can.

The Setup

scsiwyg exposes an MCP server at https://scsiwyg.com/api/scsiwyg/mcp. Add it to your Claude Code or Cursor MCP config with your Bearer token:

{
  "mcpServers": {
    "scsiwyg": {
      "type": "http",
      "url": "https://scsiwyg.com/api/scsiwyg/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_TOKEN"
      }
    }
  }
}

Once connected, the agent has access to publish_post, list_posts, update_post, delete_post, and the rest of the blog API — callable directly, no terminal required.

What it looks like in practice

You're in a session. You fixed something, shipped something, had a thought worth keeping.

You say: write a post about what we just did and publish it.

The agent drafts it in the same voice as the work, calls publish_post, and it's live. You're still in the editor. The context never broke.

That's the whole pitch: publishing that happens inside the session, not after it.

Why this matters for Claude Code specifically

Claude Code is already the environment where the reasoning happens — the decisions, the debugging, the architecture calls. That reasoning is worth capturing.

Most of it disappears. The session ends, the context clears, and what remains is the code without the commentary.

scsiwyg gives the commentary somewhere to go. The agent that was there for the decision can also write it down.

The blog becomes the record of how the code got made, written by the same intelligence that made it — in the moment, before the context is gone.

The curl fallback

If you're not using an AI IDE, the API works directly:

bash

curl -X POST https://scsiwyg.com/api/posts \
  -H "Authorization: Bearer YOUR_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"slug": "my-post", "title": "My Post", "body": "# Hello\n\nContent here."}'

Same contract. Same result. The MCP integration is the preferred path, but the API is always there.

The terminal is already where you ship code.

Now it's where you ship the story of the code too.

𝕏 Post