Define your content schema once. Manage it visually. Let AI help write it. Render it from any framework. Deploy anywhere.
Your content lives as flat JSON files in your git repo — readable by Next.js, Laravel, Django, Spring Boot, .NET, Rails, Hugo, or any other language. The CMS admin is a Next.js app, but the content layer is universal. See examples/consumers/ for working Java and .NET reference apps.
Public read-only MCP server for @webhouse/cms sites
2026-10-28
星數
—
工具
—
可用率
—
npm create @webhouse/cms my-site
cd my-site
bash start.sh
That's it. Claude Code or other AI platforms reads your schema, builds a Next.js site or through other frameworks, and you manage content through the admin UI.
What is this?
@webhouse/cms is a file-based, code-first content management system. You define collections and fields in cms.config.ts, and the CMS stores content as flat JSON files in a content/ directory. No database required. Git-committable. AI-native from day one.
Content is stored as JSON — read it directly in Next.js, Astro, or any framework:
// Read content — no SDK, no API, just files
import { readFileSync } from 'node:fs';
const post = JSON.parse(readFileSync('content/posts/hello-world.json', 'utf-8'));
console.log(post.data.title); // "Hello, World!"
Admin UI — 5 ways to run it
The visual admin interface for managing content. Open source, full-featured, works with any site.
1. Hosted cloud (coming soon)
https://webhouse.app
Sign in, connect your GitHub repo, manage content from anywhere. Zero setup.
2. npx — one command, local install
npx @webhouse/cms-admin-cli
Auto-detects cms.config.ts in your project. First run builds and caches the admin (~2 min). Subsequent starts are instant.
npx @webhouse/cms-admin-cli --config ./cms.config.ts # explicit config
npx @webhouse/cms-admin-cli -p 4000 # custom port
npx @webhouse/cms-admin-cli --update # force rebuild
3. Docker — isolated, reproducible
docker run -p 3010:3010 -v $(pwd):/site ghcr.io/webhousecode/cms-admin:latest
Published to GHCR for linux/amd64 + linux/arm64. Mounts your project at /site, auto-detects cms.config.ts, serves admin on port 3010.
Stable: :latest or :0.3.0 — tagged releases
Weekly: :weekly — automated Monday builds
4. Tarball — Node.js only, no Docker
curl -L https://github.com/webhousecode/cms/releases/latest/download/cms-admin.tar.gz | tar xz
cd cms-admin-*
./run.sh
Requires Node.js 22+. Runs on Linux, macOS, and Windows (WSL/Git Bash). First boot prompts for admin email + password via the setup wizard. See docs.webhouse.app/docs/releases for all download channels, or the plain-text releases.txt feed for scripts.
5. Git clone — full source access
git clone https://github.com/webhousecode/cms.git
cd cms
pnpm install
pnpm dev
Admin runs on localhost:3010. Set CMS_CONFIG_PATH to point at your site's config.
Note: Do not use npx cms — npm resolves it to an unrelated package. Use npx @webhouse/cms-cli if you prefer not to install globally.
Commands
Command
Description
cms init [name]
Scaffold a new project
cms dev [--port 3000]
Start dev server with REST API and hot reload
cms build [--outDir dist]
Build static site (HTML, sitemap, llms.txt)
cms serve [--port 5000]
Serve built site locally
AI commands
Require ANTHROPIC_API_KEY or OPENAI_API_KEY in .env.
Command
Description
cms ai generate <collection> "<prompt>"
Generate a new document with AI
cms ai rewrite <collection>/<slug> "<instruction>"
Rewrite existing content
cms ai seo [--status published]
Run SEO optimization across all documents
# Examples
cms ai generate posts "Write a guide to TypeScript generics"
cms ai rewrite posts/hello-world "Make it more concise and add code examples"
cms ai seo
MCP commands
Command
Description
cms mcp serve
Start stdio MCP server (for Claude Code / .mcp.json)
cms mcp keygen
Generate MCP API key
cms mcp test
Test MCP server connection
cms mcp status
Check MCP server status
Content creation — 3 ways
A) Via AI generation
cms ai generate posts "Write a blog post about TypeScript best practices"
> Create a blog post about why file-based CMS is the future
REST API
The dev server (cms dev) exposes a full REST API. See the complete OpenAPI specification.
Endpoints
Method
Endpoint
Description
GET
/api/manifest
CMS configuration and collection list
GET
/api/schema/:collection
JSON Schema for a collection
GET
/api/content/:collection
List all documents in a collection
GET
/api/content/:collection/:slug
Get a single document by slug
POST
/api/content/:collection
Create a new document
PATCH
/api/content/:collection/:slug
Update a document
DELETE
/api/content/:collection/:slug
Delete a document
GET
/api/content/:collection/:slug/_fieldMeta
Get field-level AI lock metadata
PATCH
/api/content/:collection/:slug/_fieldMeta
Update field locks
Example
# List all published posts
curl http://localhost:3000/api/content/posts?status=published
# Get a single post
curl http://localhost:3000/api/content/posts/hello-world
# Create a post
curl -X POST http://localhost:3000/api/content/posts \
-H "Content-Type: application/json" \
-d '{
"slug": "my-post",
"status": "draft",
"data": {
"title": "My First Post",
"content": "# Hello\n\nThis is my first post.",
"date": "2026-03-15"
}
}'
Building a site with Claude Code
Every scaffolded project includes a CLAUDE.md that teaches AI how to use the CMS. The @webhouse/cms npm package also ships with a comprehensive CLAUDE.md.
# Scaffold and let AI build your site
npm create @webhouse/cms my-site
cd my-site
claude "Build a portfolio site with Next.js and Tailwind. Read CLAUDE.md for CMS docs."
Or use the included start script:
bash start.sh "Build a dark-themed blog with categories and author pages"