An agent-ready CMS that allows AI clients to build, edit, and publish websites using content-as-files and a Model Context Protocol bridge.
Also known as openviglet/shio, shio, @viglet/shio
- Stars
- 3
- Tools
- —
- Downloads, 30 days
- —
- Latest version
- 2026.3.3
- Last commit
- Nov 11, 2026
- License
- Apache-2.0
What is Viglet Shio MCP?
Viglet Shio is an agent-ready CMS that allows AI clients to build, edit, and publish websites using content-as-files and a Model Context Protocol bridge.
Summary generated from the project's README
About Viglet Shio MCP server
Building and managing websites through an AI agent is possible with Viglet Shio, an agent-ready CMS that treats content as files. Developers can use this tool to scaffold Next.js sites, manage content models as code, and project entire websites into front-mattered Markdown on disk. By using the shio mcp command, the CMS connects to Claude Code or other MCP-capable agents via a stdio bridge.
The system provides thirteen specific tools including shio_write, shio_apply, and shio_publish to facilitate website construction. It supports a GitOps workflow where post-types are managed as JSON files, allowing for local edits and remote synchronization. Users can connect to their instances using a base URL, username, password, or a Content Delivery API token. This setup allows an AI to perform tasks like linting content with shio_verify or generating structural digests with shio_digest, making the entire web development lifecycle accessible through natural language instructions.
What you can do with it
- 1Automated website content managementAn AI agent can edit website pages by interacting with local Markdown files.
Written from the project's README. Every use case is checked against a quote from it.
How to install Viglet Shio MCP
Formats verified 10 Nov 2026Add to CursorAdd to GooseInstall Viglet Shio MCP in Claude Code
$ claude mcp add --env 'SHIO_PASSWORD=<YOUR_SHIO_PASSWORD>' --env 'SHIO_USER=<SHIO_USER>' shio -- npx -y @viglet/shioInstall Viglet Shio MCP in Cursor
~/.cursor/mcp.json
{
"mcpServers": {
"shio": {
"command": "npx",
"args": [
"-y",
"@viglet/shio"
],
"env": {
"SHIO_PASSWORD": "<YOUR_SHIO_PASSWORD>",
"SHIO_USER": "<SHIO_USER>"
}
}
}
}Install Viglet Shio MCP in VS Code
.vscode/mcp.json
{
"servers": {
"shio": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@viglet/shio"
],
"env": {
"SHIO_PASSWORD": "<YOUR_SHIO_PASSWORD>",
"SHIO_USER": "<SHIO_USER>"
}
}
}
}Install Viglet Shio MCP in VS Code CLI
$ code --add-mcp '{"name":"shio","type":"stdio","command":"npx","args":["-y","@viglet/shio"],"env":{"SHIO_PASSWORD":"<YOUR_SHIO_PASSWORD>","SHIO_USER":"<SHIO_USER>"}}'Install Viglet Shio MCP in Claude Desktop
claude_desktop_config.json
{
"mcpServers": {
"shio": {
"command": "npx",
"args": [
"-y",
"@viglet/shio"
],
"env": {
"SHIO_PASSWORD": "<YOUR_SHIO_PASSWORD>",
"SHIO_USER": "<SHIO_USER>"
}
}
}
}Install Viglet Shio MCP in Codex
$ codex mcp add shio --env 'SHIO_PASSWORD=<YOUR_SHIO_PASSWORD>' --env 'SHIO_USER=<SHIO_USER>' -- npx -y @viglet/shioInstall Viglet Shio MCP in Codex config.toml
~/.codex/config.toml
[mcp_servers.shio] command = "npx" args = ["-y", "@viglet/shio"] [mcp_servers.shio.env] SHIO_PASSWORD = "<YOUR_SHIO_PASSWORD>" SHIO_USER = "<SHIO_USER>"
Install Viglet Shio MCP in Gemini CLI
$ gemini mcp add -s user -e 'SHIO_PASSWORD=<YOUR_SHIO_PASSWORD>' -e 'SHIO_USER=<SHIO_USER>' shio npx -- -y @viglet/shioInstall Viglet Shio MCP in Gemini settings.json
~/.gemini/settings.json
{
"mcpServers": {
"shio": {
"command": "npx",
"args": [
"-y",
"@viglet/shio"
],
"env": {
"SHIO_PASSWORD": "<YOUR_SHIO_PASSWORD>",
"SHIO_USER": "<SHIO_USER>"
}
}
}
}Configuration
SHIO_PASSWORDRequiredSecretThat user's password
SHIO_USERRequiredConsole user the bridge signs in as
SHIO_URLThe Shio instance to drive
| Name | Description | |
|---|---|---|
| SHIO_PASSWORD | That user's password | RequiredSecret |
| SHIO_USER | Console user the bridge signs in as | Required |
| SHIO_URL | The Shio instance to drive |
Automated checks
Ran Nov 13, 2026Full report →Passed our automated checks. That is not a security audit: read the code and give the server the narrowest access it needs. How checks work
- Source repository linked and reachablePass
- Open source license (OSI)Pass
- Commit or release in the last yearPass
- Package name not close to a popular packagePass
- Remote endpoint uses HTTPSNot checked
- Destructive tools are labelledNot checked
- No hidden instructions to the modelPass
- No critical advisory in the package or its dependenciesPass
README
View on GitHub@viglet/shio — the Viglet Shio CLI
The command-line interface for Viglet Shio, the open source, agent-ready CMS. It is three things at once:
- the "JS dev, zero Java" workflow — scaffold a site, generate types, manage your content model as code;
- the content-as-files projection — your whole site as front-mattered Markdown on disk, with a three-way merge back;
- the MCP (Model Context Protocol) bridge —
shio mcpputs your CMS in front of Claude Code or any MCP-capable agent.
npm install -g @viglet/shio # or: npx @viglet/shio <command>
Requires Node ≥ 26.
Use it from Claude Code
claude mcp add shio -- npx -y @viglet/shio mcp
That exposes 13 tools — shio_context, shio_find, shio_read, shio_write,
shio_apply, shio_publish, shio_assets, shio_blueprint, shio_changes,
shio_verify, shio_digest, shio_remember, shio_forget — plus the
shio://manifest, shio://blueprints, shio://context and
shio://schema/{postType} resources. There is also a full Claude Code plugin
that adds skills and slash commands on top:
claude plugin marketplace add openviglet/shio
claude plugin install shio
See shio.viglet.org/claude-code.
Commands
Run shio <command> --help for a command's own flags.
Start a project
| Command | What it does |
|---|---|
shio init [name] |
Scaffold a Next.js site wired to the Content Delivery API (--blueprint <name> takes a starter from the instance instead) |
shio blueprints |
List the appliable starting points on the instance |
Author content
| Command | What it does |
|---|---|
shio pull |
Post-types into shio/post-types/*.json; --content also projects pages to shio/content/** |
shio push |
Apply local post-types back to Shio (--dry-run, --check, --prune, --content) |
shio apply [file] |
Plan/apply a desired-state content document, or a ready-made blueprint package |
shio publish [addr] |
Make drafts live, or take live pages down (--unpublish, --site … --all) |
shio import <file> |
Clone an exchange package (.zip) into this instance |
shio build |
Compile local DSL/JSON post-types to canonical JSON |
Understand the instance
| Command | What it does |
|---|---|
shio context |
The agent context pack — model + sitemap + conventions, in one call |
shio resolve <addr> |
Resolve a content address (post: / folder: / site: / id:) |
shio impact <addr> |
What a change to this template would affect: layouts, types, page counts |
shio changes |
What changed, with a cursor to resume from (--since, --cursor) |
shio remember |
Write down a decision the next session should not re-derive |
Prove the work
| Command | What it does |
|---|---|
shio verify |
Lint the content and its routes; exits non-zero on an error — the CI gate |
shio digest <page> |
Structural digest of one page: outline, landmarks, links, images |
shio audit <page> |
What is wrong with a rendered page, as text with a selector each |
shio snapshot <page> |
PNG of a page, and whether it looks different (needs Playwright) |
shio diff |
Compare what a replica serves with the capture that declared it |
shio report |
The human handoff: what changed, preview links, open questions |
Replicate an existing website
| Command | What it does |
|---|---|
shio clone <url> |
Capture a site that already exists — an inventory, and no content |
shio propose |
Which captured blocks could become sections, and what each would lose |
shio convert |
Apply the accepted plan: sections, theme and scripts, as DRAFT |
Front-end loop
| Command | What it does |
|---|---|
shio types |
Generate a .d.ts from the live post-types — autocomplete on post.attrs.* |
shio dev |
Generate types, start the site dev server, watch the model (--content syncs both ways) |
shio deploy |
push (apply) then types |
shio mcp |
Bridge stdio to this instance's MCP endpoint |
Connection
| Flag | Env | Used by |
|---|---|---|
--url <baseUrl> |
SHIO_URL (default http://localhost:2710) |
all |
--user / --password |
SHIO_USER / SHIO_PASSWORD |
pull / push / apply / deploy |
--token <token> |
SHIO_CDA_TOKEN |
types / dev / deploy |
Editing the content model is an admin act, so pull/push use the console
username and password; types uses a Content Delivery API token.
Post-types as code (GitOps)
shio pull --user admin --password admin # → shio/post-types/*.json
git add shio/post-types && git commit -m "snapshot content model"
# …edit a JSON: add a field, change a label…
shio push --dry-run # preview the diff
shio push # apply
shio push --check # CI drift guard: non-zero if the plan is non-empty
shio push --prune # also delete remote types absent locally
The JSON is a lossless view of each post-type (every field including Tab,
verbatim widgetSettings, nested Relator sub-fields), so the round-trip
preserves the full authoring model. System post-types are read-only.
shio/post-types/ may also hold .ts/.mjs sources written with the typed DSL
@viglet/shio-model —
push and build compile them to canonical JSON before diffing.
Content as files
shio pull --content # the whole site as front-mattered Markdown in shio/content/**
# …edit with your editor, or let an agent use Edit / Write / Grep…
shio push --content # three-way merge back (--ours, --theirs, --force)
This is the point of the design: files beat APIs for authoring, because
Edit, Write and Grep are the cheapest tools an agent has.
Related packages
| Package | For |
|---|---|
@viglet/shio-client |
Zero-dependency Content Delivery API client |
@viglet/shio-react-sdk |
React hooks and render components |
@viglet/shio-model |
Author the content model as typed code |
@viglet/shio-sections |
The page-section vocabulary |
@viglet/shio-editor-cors |
Inline visual editing with the Visual Editor |
@viglet/create-shio-app |
Next.js starter generator |
License
Apache-2.0 — Viglet Shio · github.com/openviglet/shio · shio.viglet.org/docs · part of the Viglet open source family.
Viglet Shio MCP questions
How do I add Viglet Shio MCP to Claude Code?
Run claude mcp add --env 'SHIO_PASSWORD=<YOUR_SHIO_PASSWORD>' --env 'SHIO_USER=<SHIO_USER>' shio -- npx -y @viglet/shio in your terminal. Add --scope user to make it available in every project.
How do I add Viglet Shio MCP to Cursor?
Open ~/.cursor/mcp.json and add the server under mcpServers, using the Cursor config shown in the install section above.
How can I use Shio with Claude Code?
You can add Shio to Claude Code by running the command: claude mcp add shio -- npx -y @viglet/shio mcp.
What tools does the MCP bridge expose?
The bridge exposes 13 tools including shio_context, shio_find, shio_read, shio_write, shio_apply, shio_publish, shio_assets, shio_blueprint, shio_changes, shio_verify, shio_digest, shio_remember, and shio_forget.
Can I manage my content model as code?
Yes, Shio supports a GitOps workflow where you can scaffold a site, generate types, and manage your content model as code using JSON or a typed DSL.
How does the content-as-files feature work?
It projects your entire site as front-mattered Markdown on your disk, allowing you to use standard file editing tools or agents to make changes and then merge them back.