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:

• See the 2-minute demo
• Open the normalize guide
• Read the docs

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 15 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

Package	npm	Role
@contentrain/mcp		27 MCP tools + stdio / HTTP transport + Local / GitHub / GitLab providers
contentrain		CLI + Serve UI + MCP stdio entrypoint
@contentrain/query		Generated TypeScript query SDK
@contentrain/types		Shared type definitions + constants
@contentrain/rules		Agent quality rules for IDE integration
@contentrain/skills		Workflow procedures + framework guides
@contentrain/wp-import		WordPress WXR / REST → RawIR → .contentrain store
@contentrain/emitter-astro		ProjectIR → a complete Astro project
@contentrain/verify		SEO, indexing, link and asset gates for a built site

Starter Templates

Production-ready templates with Contentrain content models, generated SDK client, and framework-specific patterns: