Contentrain
Give Claude or Cursor a local-first MCP layer so generated marketing copy, docs, and UI strings stay aligned to your content models, pass validation rules, and ship in multiple locales without driftin
Overview
Contentrain is a Build-phase MCP server that provides local-first AI content governance—models, validated content, and i18n—for agent-driven docs and product copy.
What is this MCP server?
- Local-first MCP server — content models and drafts stay on your machine, not a hosted CMS lock-in
- Content governance tools for models, instances, and validation rules agents must respect
- Built-in validation so AI-generated copy fails fast instead of publishing inconsistent fields
- Internationalization (i18n) support for multi-locale catalogs, docs, and product strings
- Stdio npm package @contentrain/mcp v1.4.0 for Claude Code, Cursor, and other MCP clients
- Package version 1.4.0
- Transport: stdio
- Registry: npm @contentrain/mcp
Community signal: 3 GitHub stars.
What problem does it solve?
Agents happily generate marketing and docs text that looks fine in chat but breaks your content model, misses required fields, or diverges across languages with no single source of truth.
Who is it for?
Indie SaaS and content sites where you define JSON or schema-driven content models and want Claude Code or Cursor to edit catalogs, docs, and strings under validation without a heavyweight hosted CMS.
Skip if: Teams that only need occasional one-off blog posts in plain markdown with no schemas, validation rules, or localization pipeline.
What do I get? / Deliverables
After you register Contentrain in your MCP client, the agent reads and writes governed structured content with validation and locale awareness instead of unstructured blobs.
- Agent-accessible governed content records aligned to your models
- Validation feedback on AI-generated fields before publish or deploy
- Locale-aware content updates manageable from the agent session
Recommended MCP Servers
Journey fit
Content governance and structured authoring sit in Build because schemas, validation, and i18n are defined while the product and its information architecture are still taking shape. The docs subphase is the canonical shelf for model-driven content, editorial rules, and translation workflows that agents apply before or alongside code changes.
How it compares
Structured content-governance MCP server, not a visual page builder or a generic file-search skill.
Common Questions / FAQ
Who is Contentrain MCP for?
Solo builders and small teams shipping content-heavy products who want AI agents to edit schema-backed copy and docs locally with validation and i18n, not unstructured drafts.
When should I use Contentrain MCP?
Use it during Build and Docs work when you are defining or updating content models, validating agent-generated fields, or maintaining multiple locales before launch.
How do I add Contentrain to my agent?
Install the npm package @contentrain/mcp, add it as a stdio MCP server in Claude Code, Cursor, or Windsurf per your client’s MCP config, then point the agent at your local Contentrain project or data root.