Contentrain AI
Website · Docs · Discord · Twitter · LinkedIn
Extract, govern, and ship structured content from your codebase.
Contentrain helps teams turn hardcoded UI text, docs, and structured content into a governed, reviewable content layer. Agents can extract, create, translate, and update content, while Contentrain enforces schema, Git review, and portable file output.
Agent extracts or updates content → Contentrain standardizes → Human reviews → Any platform consumes
Try it in 30 seconds
npx contentrain init # create .contentrain/ workspace
npx contentrain serve # open the local review UI
That's it. You now have a governed content workspace with models, validation, review branches, and a local UI — no account, no cloud, no proprietary content format.
Start here:
What Contentrain is for
- Rescuing hardcoded strings from existing apps and turning them into structured, translatable content
- Starting new projects with a real content layer instead of scattering copy across components
- Serving the same content across web, docs, mobile, and backend systems from plain JSON and Markdown in Git
What it is not
- Not an AI writing app
- Not a database-first or dashboard-first CMS replacement for every team
- Not a proprietary content runtime that locks your app to one platform
What it looks like
Before: Hardcoded strings scattered across your codebase — no structure, no translations, no review.
export default function Hero() {
return (
<section>
<h1>Welcome to our platform</h1>
<p>Start your free trial today</p>
<button>Get Started</button>
</section>
)
}
After: Content lives in .contentrain/, typed and structured. Source files use i18n keys.
export default function Hero() {
const t = useTranslations()
return (
<section>
<h1>{t('hero.title')}</h1>
<p>{t('hero.subtitle')}</p>
<button>{t('hero.cta')}</button>
</section>
)
}
// .contentrain/content/marketing/hero/en.json
{
"cta": "Get Started",
"subtitle": "Start your free trial today",
"title": "Welcome to our platform"
}
The normalize flow extracts strings, creates models, and patches your source files — all through reviewable git branches.
This is the strongest entry point into the product:
take the content chaos already in your codebase and turn it into a governed, reviewable content layer.
How it works
┌─────────────┐ ┌──────────────────┐ ┌──────────────┐
│ AI Agent │────▶│ MCP (27 tools) │────▶│ .contentrain/│
│ (decides) │ │ (enforces) │ │ (stores) │
└─────────────┘ └──────────────────┘ └──────┬───────┘
│
┌──────────────────┐ │
│ Review UI / Git │◀─────────────┘
│ (human approves)│
└──────────────────┘
- Agent decides what content should exist and where it should come from
- Contentrain enforces schemas, validation, canonical serialization, and git workflow
- Human reviews through branches, PRs, or the local Serve UI
- Output is plain JSON + Markdown that any language or framework can consume
4 content kinds
27 field types (string, email, url, image, relation, array, object, markdown, ...) with built-in validation.
Use your content anywhere
Content is plain JSON and Markdown. Any language reads it directly.
For TypeScript projects, generate a typed SDK:
npx contentrain generate
import { query, singleton, dictionary, document } from '#contentrain'
const hero = singleton('hero').locale('en').get()
const posts = query('blog-post').locale('en').include('author').all()
const labels = dictionary('ui-labels').locale('tr').get('auth.login')
const article = document('docs').locale('en').bySlug('getting-started')
Works with Nuxt, Next.js, Astro, SvelteKit, Vue, React, Node, Go, Python, Swift, Flutter, and 20+ stacks.
Why teams use it
- Git-native — every write goes through worktree isolation + review branches
- Normalize flow — scan codebase for hardcoded strings → extract → create i18n-ready content → patch source files
- MCP engine — 27 tools (22 core + 5 media) over stdio or HTTP transport, works with Claude Code, Cursor, Windsurf, or any MCP client
- Provider-agnostic engine — the same tool surface runs over a local worktree, GitHub, or GitLab (self-hosted included) with zero tool-code changes. HTTP transport available for remote drivers such as Studio.
- Canonical serialization — sorted keys, deterministic output, clean git diffs, conflict-free parallel edits
- Agent rules & skills — behavioral policies and step-by-step workflows ship as npm packages
- Serve UI — local web dashboard for browsing models, content, validation, and normalize status
- Framework-agnostic — MCP doesn't know your framework. Agent + skills handle stack-specific logic
Agent Skills
This repo ships 16 Agent Skills — reusable workflow procedures that any AI coding agent can load on demand.
Install all skills to your agent:
npx skills add Contentrain/ai/packages/skills
Or install a specific skill:
npx skills add Contentrain/ai/packages/skills --skill contentrain-normalize
Skills work with Claude Code, Cursor, Windsurf, GitHub Copilot, OpenAI Codex, Gemini CLI, and 40+ other agents.
See AGENTS.md for the full skill catalog and agent guidance.
Packages
Starter Templates
Production-ready templates with Contentrain content models, generated SDK client, and framework-specific patterns:
Each template is a GitHub template repo — click "Use this template" to start.
templates/astro-starter lives in this repository: the base a WordPress migration starts from — posts, pages, archives and permalinks, SEO, RSS, sitemap, search, Studio forms and comments, Gutenberg block styles — and it passes its own gates (astro check, knip, build, built-site checks, Lighthouse) with no content. node scripts/starter-gates.mjs runs them on a standalone copy; CI runs them with the SDK at HEAD, empty and with templates/fixtures/wp-demo.
Quick reference
npx contentrain init # initialize project
npx contentrain serve # local review UI (port 3333)
npx contentrain serve --stdio # MCP over stdio for IDE agents
npx contentrain validate # check content health
npx contentrain generate # generate typed SDK client
npx contentrain status # project overview
npx contentrain doctor # setup health check
npx contentrain reconcile # merge a diverged base branch, content-aware
npx contentrain studio login # authenticate with Studio
npx contentrain studio connect # connect repo to Studio project
Documentation
- 2-Minute Demo — the fastest way to understand the product
- Getting Started — install, connect an agent, and run the first workflow
- Normalize Guide — the main hardcoded-string rescue flow
- Ecosystem Map — package-to-product bridges across AI and Studio
- Contentrain Studio — open-core team operations for Git-native structured content, self-hostable or available as managed plans (Starter/Pro/Enterprise)
- Full Docs — guides, package reference, and framework integration
Development
pnpm install && pnpm build && pnpm test
pnpm lint # oxlint, warnings treated as errors
pnpm docs:check # the docs must not state a number the code disagrees with
pnpm docs:check runs two guards, both needing pnpm build first:
- facts — resolves counts (MCP tools, skills, field types, capability keys)
from the packages that own them and compares every place the docs, this
README and
AGENTS.mdstate one. - examples — every
@contentrain/*import in a documented example must name a real export, and no example may mix CommonJS with a top-levelawait(a shape that runs in no module system at all).
Both self-test against real defects from this repo's history before they run, so a check that stops catching fails loudly instead of passing silently.
See RELEASING.md for the versioning and publish workflow.
Community
- Discord — chat with the team and community
- GitHub Discussions — questions and ideas
- Twitter / X — product updates and announcements
- LinkedIn — company news
- YouTube — tutorials and demos
- GitHub Issues — bug reports and feature requests
If Contentrain AI is useful to you, consider giving it a star — it helps others discover the project.
License
MIT