Repo-native content governance for AI agents. Extract, review, and deliver UI text, docs, and structured content from Git.
Documentation
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 consumesTry it in 30 seconds
npx contentrain init # create .contentrain/ workspace
npx contentrain serve # open the local review UIThat'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 (
)
}After: Content lives in `.contentrain/`, typed and structured. Source files use i18n keys.
export default function Hero() {
const t = useTranslations()
return (
)
}// .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
| Kind | What it stores | Storage | Example |
|---|---|---|---|
| Collection | Multiple typed entries | JSON object-map | Blog posts, products, team |
| Singleton | Single entry per locale | JSON object | Hero section, site config |
| Document | Markdown + frontmatter | `.md` files | Docs, articles, changelog |
| Dictionary | Flat key-value strings | JSON flat map | i18n translations, UI labels |
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 generateimport { 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/skillsOr install a specific skill:
npx skills add Contentrain/ai/packages/skills --skill contentrain-normalizeSkills 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` |  | 26 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 |
Starter Templates
Production-ready templates with Contentrain content models, generated SDK client, and framework-specific patterns:
| Template | Framework | Use Case |
|---|---|---|
| astro-blog | Astro | Blog / editorial |
| astro-landing | Astro | Landing page |
| next-commerce | Next.js | E-commerce storytelling |
| next-multi-surface-saas | Next.js | Marketing + app + docs unified |
| next-saas-dashboard | Next.js | SaaS dashboard UI copy |
| next-white-label-portal | Next.js | White-label / multi-tenant |
| nuxt-admin-console | Nuxt | Admin console / operations |
| nuxt-saas | Nuxt | SaaS marketing site |
| sveltekit-editorial | SvelteKit | Editorial / publication |
| vitepress-docs | VitePress | Documentation site |
Each template is a GitHub template repo — click "Use this template" to start.
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 projectDocumentation
- **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 testSee `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
Frequently asked questions
What is ai?
ai is Repo-native content governance for AI agents. Extract, review, and deliver UI text, docs, and structured content from Git.
How do I install ai?
Open the GitHub repository and follow its README. Most MCP servers are added to your client's MCP config, then called by your agent.
Is ai open source?
Yes — it is hosted on GitHub at https://github.com/Contentrain/ai and has 4 stars.
Related MCP tools
Open-source cross-agent memory layer for coding agents via MCP. Compatible with Claude Code, Codex, Cursor, Windsurf, Gemini CLI, Antigravity, OpenClaw, Hermes Agent, Oh-my-Pi, Pi, Copilot, Kiro, OpenCode, and Trae.
Cut AI token costs 95%+ on code exploration. The leading MCP server for precise, symbol-level GitHub code retrieval via tree-sitter AST. Works with Claude Code, Cursor & any MCP client. 313B+ tokens saved.
Open-source coding agent memory. Records issues, attempts, fixes and decisions, then warns your agent before it repeats an approach that already failed. Native MCP server for Claude Code, Cursor, Antigravity and Codex. 100% local, no cloud, no telemetry. MIT.
The go-to web for your AI coding agent — local-first search, fetch, crawl & research over MCP. No API keys, no cloud, $0/query. Public beta.
Browser automation clicks buttons. OpenTabs calls APIs.
AI Skills, MCP Tools, and CLI for Unity Engine. Full AI develop and test loop. Use cli for quick setup. Efficient token usage, advanced tools. Any C# method may be turned into a tool by a single line. Works with Claude Code, Gemini, Copilot, Cursor and any other absolutely for free.
Run your own MCP server? See who uses it and what to fix.
Measure it with TrackMCP