Contentrain MCP Server

Local-first MCP server for AI content governance — models, content, validation, i18n

Remote serverstreamable-httpPython

What is the Contentrain MCP server?

Contentrain MCP server is a hosted integration for AI assistants that speak the Model Context Protocol. Local-first MCP server for AI content governance — models, content, validation, i18n.

What you get

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.

  • 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 — — 24 tools (19 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

Setting it up

Being a remote server, there is no local install. You register the endpoint with your client, authorise it once, and the tools appear.

What the assistant can call

Once Contentrain is connected, these are the calls the assistant has available:

  • Git-native — every write goes through worktree isolation + review branches
  • Provider — agnostic engine** — the same tool surface runs over a local worktree, GitHub, or GitLab (self-hosted included) with zero tool-code changes. HTTP
  • Framework-agnostic — MCP doesn't know your framework. Agent + skills handle stack-specific logic
  • Kind — What it stores
  • Collection — Multiple typed entries
  • Singleton — Single entry per locale
  • Document — Markdown + frontmatter
  • Dictionary — Flat key-value strings
  • Package — npm
  • Template — Framework

Before you rely on it

  • Your data travels to the provider's service, so the usual questions apply about what you send and what they retain.
  • With 10 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch Contentrain.
  • MCP clients confirm each tool call by default. Leave that on until you have watched what the contentrain mcp server does with a few real requests.

Choosing this one

Plenty of developer tooling servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Contentrain's toolset — Git-native, Provider, Framework-agnostic and 7 more — is a fair guide to whether it matches your workflow. It is maintained by Contentrain; worth a glance at recent repository activity before you build anything load-bearing on it.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.

Available tools

ToolWhat it does
Git-nativeevery write goes through worktree isolation + review branches
Provideragnostic 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.
Framework-agnosticMCP doesn't know your framework. Agent + skills handle stack-specific logic
KindWhat it stores
CollectionMultiple typed entries
SingletonSingle entry per locale
DocumentMarkdown + frontmatter
DictionaryFlat key-value strings
Packagenpm
TemplateFramework

How to install the Contentrain MCP server

{
  "mcpServers": {
    "contentrain": {
      "command": "npx",
      "args": ["-y", "contentrain"]
    }
  }
}

Add to claude_desktop_config.json, then restart Claude Desktop.

Example prompts to try

  • Use Contentrain to Git-native.
  • Use Contentrain to Provider.
  • Use Contentrain to Framework-agnostic.

Frequently asked questions

It connects Contentrain to MCP-compatible AI assistants such as Claude and Cursor, exposing 10 tools (Git-native, Provider, Framework-agnostic, and more) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with Contentrain directly.