Skip to main content
v2026.3Open SourceApache 2.0HeadlessMCP

Viglet Shio CMS

Viglet Shio CMS is an open-source headless CMS built for a different operator. A coding agent builds the site: over MCP, a REST surface designed for one call instead of a session, or content projected to files on disk. A curator approves it: approving, correcting and publishing in the console or straight on the rendered page. The Content Delivery API serves it: REST and GraphQL, with a TypeScript client, React hooks and a Next.js starter.

Shio hosts no model and no prompts. It is the substrate your agent drives, running on your own infrastructure, and what it competes on is the quality of that protocol: discoverable, deterministic, verifiable, and cheap in tokens.

What makes it different
🧭
One call, not a session

The instance describes itself: a manifest of every capability, plus a context pack of the site as it stands. An agent does not have to explore before it can write.

📁
Content is also files

Project a site to disk and author it with the cheapest tools an agent has, edit, write, grep, then push it back, with a per-field three-way merge so a curator's own edit is never overwritten.

🛡️
Nothing surprises the curator

Agent writes land as drafts, plans can run dry first, destructive operations need a confirm token naming what they remove, and a delete is a trash you can undo.

📐
Addressed, not id-shuffled

Content is reached by path, post:mysite/about, folder:mysite/blog, so no UUID has to survive between two calls, and the same write twice is the same result.

Proof without a screenshot

A content lint, a route check and a render digest give an agent cheap textual evidence that what it built actually works, instead of asking someone to look.

📉
Tokens are a budget

Responses carry measured size budgets and a benchmark runs in CI, so a token regression fails the build the same way a broken test does.

Quick Start
Who does which job
Learn the model
Reference