A blog and a wiki you build by talking to your AI — drafted in your voice, published with a nod.
Every scsiwyg site is either a blog — a chronological field recording of the work — or a wiki, a structured tree your AI maintains as you learn. Same API. Same MCP. Different shape.
Tell your agent what just happened. It drafts in your voice from the context of your open files. You read it, you approve it, it’s live.
> blog: I just shipped the new auth flow. We went stateless JWT, rotating refresh. Tag it engineering. Drafted → "Why we rewrote our auth middleware" slug → auth-middleware-rewrite status → published
Pages have parents, children, sort order, confidence and provenance. Your agent builds the tree as you learn; the platform renders it with sidebar nav and breadcrumbs.
> publish my wiki to scsiwyg research/ llm-patterns mediumtransformer-arch highreference/ platform-arch highsecurity-posture medium Published 11 pages, updated 3
Most writing tools assume the writing comes after the work. You finish the sprint, switch tabs, summon the CMS, fight the editor, find the photo, choose the slug. By the time the post is up, the moment has gone cold.
scsiwyg inverts that. The composition surface is the place you already are — your editor, your chat with Claude, your terminal. The agent reads the room. You correct it. You ship.
“The point isn’t to write more. It’s to leave a trail of how you actually thought, while you were thinking.”
You never leave the editor or the chat. Content lives inside the same mental frame as the work — the bug you untangled, the refactor that backfired, the decision you almost forgot.
The agent drafts from your open files, your last messages, your tone. Not reconstructed from memory a week later. The result reads like you, because it was you.
Designers logging design rationale. Researchers maintaining living wikis. Founders building in public. Anyone who already lives inside a chatbot has a publishing surface, now.
Posts and pages compound into a record of how you think and work — searchable, embeddable, exportable. Yours, in flat portable JSON, forever.
No CMS. No build system. No context switch. Sign up, install the MCP, and tell your agent to write something.
Sign up and grab one API key from your account. That’s the whole onboarding.
Create your account →Drop the scsiwyg MCP server into Claude, ChatGPT, Cursor, or Windsurf. One config block.
MCP setup →Say “blog:” and the rest happens. Your first post is one sentence away.
See examples →