Contentrain

Official registry Developer tools

Git-native content governance for AI agents — 27 deterministic MCP tools over stdio and HTTP.

Install

Add this to your client's MCP configuration (Claude Desktop: claude_desktop_config.json; Cursor: .cursor/mcp.json; VS Code and others use the same "mcpServers" shape).

Remote (streamable-http)
Claude Code
claude mcp add --transport http contentrain 'https://studio.contentrain.io/api/mcp/remote'
JSON configuration (Claude Desktop, Cursor, VS Code)
{
    "mcpServers": {
        "contentrain": {
            "type": "http",
            "url": "https://studio.contentrain.io/api/mcp/remote"
        }
    }
}
Remote (streamable-http)
Claude Code
claude mcp add --transport http contentrain 'https://studio.contentrain.io/api/mcp/v1/{project_id}/mcp' --header 'Authorization: <Bearer token using a Contentrain Studio MCP Cloud API key.>'
JSON configuration (Claude Desktop, Cursor, VS Code)
{
    "mcpServers": {
        "contentrain": {
            "type": "http",
            "url": "https://studio.contentrain.io/api/mcp/v1/{project_id}/mcp",
            "headers": {
                "Authorization": "<Bearer token using a Contentrain Studio MCP Cloud API key.>"
            }
        }
    }
}
NPM package @contentrain/mcp
Claude Code
claude mcp add contentrain -- npx -y @contentrain/mcp@3.11.16
JSON configuration (Claude Desktop, Cursor, VS Code)
{
    "mcpServers": {
        "contentrain": {
            "command": "npx",
            "args": [
                "-y",
                "@contentrain/mcp@3.11.16"
            ]
        }
    }
}

Documentation

From the project's README on GitHub, refreshed weekly. Links open on GitHub.

Contents
  1. Contentrain AI
  2. Try it in 30 seconds
  3. What Contentrain is for
  4. What it is not
  5. What it looks like
  6. How it works
  7. 4 content kinds
  8. Use your content anywhere
  9. Why teams use it
  10. Agent Skills
  11. Packages
  12. Starter Templates
  13. Quick reference
  14. Documentation
  15. Development
  16. Community
  17. License

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

KindWhat it storesStorageExample
CollectionMultiple typed entriesJSON object-mapBlog posts, products, team
SingletonSingle entry per localeJSON objectHero section, site config
DocumentMarkdown + frontmatter.md filesDocs, articles, changelog
DictionaryFlat key-value stringsJSON flat mapi18n 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 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

PackagenpmRole
@contentrain/mcp27 MCP tools + stdio / HTTP transport + Local / GitHub / GitLab providers
contentrainCLI + Serve UI + MCP stdio entrypoint
@contentrain/queryGenerated TypeScript query SDK
@contentrain/typesShared type definitions + constants
@contentrain/rulesAgent quality rules for IDE integration
@contentrain/skillsWorkflow procedures + framework guides
@contentrain/wp-importWordPress WXR / REST → RawIR → .contentrain store
@contentrain/emitter-astroProjectIR → a complete Astro project
@contentrain/verifySEO, indexing, link and asset gates for a built site
@contentrain/astro-kitCopy-in Astro components + catalog + builder mapping tables
@contentrain/decideTyped decisions — rule first, then Jev, then Claude Haiku — cached, budgeted, audited

Starter Templates

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

TemplateFrameworkUse Case
astro-blogAstroBlog / editorial
astro-landingAstroLanding page
next-commerceNext.jsE-commerce storytelling
next-multi-surface-saasNext.jsMarketing + app + docs unified
next-saas-dashboardNext.jsSaaS dashboard UI copy
next-white-label-portalNext.jsWhite-label / multi-tenant
nuxt-admin-consoleNuxtAdmin console / operations
nuxt-saasNuxtSaaS marketing site
sveltekit-editorialSvelteKitEditorial / publication
vitepress-docsVitePressDocumentation site

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.md state one.
  • examples — every @contentrain/* import in a documented example must name a real export, and no example may mix CommonJS with a top-level await (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

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 Contentrain?

Git-native content governance for AI agents — 27 deterministic MCP tools over stdio and HTTP.

How do I install Contentrain?

It runs as a remote server. In Claude Code: claude mcp add --transport http contentrain 'https://studio.contentrain.io/api/mcp/remote'. For other clients, paste the JSON configuration from this page into their MCP settings.

Does Contentrain need an API key?

Yes. It expects Authorization, which you set in its configuration.

Is Contentrain open source?

Yes. Its code is on GitHub under the MIT license.

Who maintains Contentrain?

It is published by Contentrain. AI.tn lists it but does not maintain or endorse it.

From the official MCP Registry. Listing is not an endorsement: review a server's code and permissions before giving it access to your data.