Contentrain
Integrations

Works with your agent, framework, and deployment path.

Contentrain stores content as plain JSON and Markdown in Git, exposes MCP tools to agents, and provides SDK/CDN access for runtime consumers.

Open Studio
Works with your agent, framework, and deployment path.

AI agents

MCP-compatible coding agents can read project context, operate content models, validate changes, and submit review branches without owning the whole repository.

Claude CodeClaude Code
CursorCursor
WindsurfWindsurf
GitHub CopilotGitHub Copilot
ClineCline
ContinueContinue
AiderAider
Any MCP clientAny MCP client

Frameworks

Generated query clients keep content access close to the framework runtime, whether the page is static, server-rendered, mobile, or a backend service.

Nuxt
Next.js
Astro
SvelteKit
Vue
React
React Native
Node

Platforms

Git providers, deployment platforms, and self-hosted infrastructure stay interchangeable because the content contract remains file-based and reviewable.

GitHubGitHub
GitLab
VercelVercel
NetlifyNetlify
CloudflareCloudflare
DockerDocker
AWSAWS
Self-hosted

Agents

Connect AI agents through MCP

Contentrain integrates with MCP-compatible agents through local stdio and HTTP transports. The agent gets structured tools for status, content, models, validation, scanning, normalize, branch submission, and bulk operations.

  • Local desktop agent workflows
  • HTTP transport for hosted or embedded agent paths
  • Bounded tool calls instead of arbitrary file edits
Connect AI agents through MCP

Frameworks

Generate framework-friendly content access

The SDK supports modern JavaScript application workflows by generating a content query client. Nuxt, Next, Astro, SvelteKit, Vite, Node, Expo, and React Native projects can consume content without coupling to a database CMS.

  • Generated JavaScript query client
  • Locale-aware reads
  • Static, server-rendered, and app runtime usage
Generate framework-friendly content access

Git providers

Work with local, GitHub, and GitLab provider paths

The provider architecture separates content operations from the place where the repository lives. Local provider access is strongest for normalize; GitHub and GitLab paths support hosted repository workflows.

  • Local provider for source scanning and file writes
  • GitHub provider for remote repository operations
  • GitLab provider for teams using GitLab infrastructure
Work with local, GitHub, and GitLab provider paths

Studio APIs

Use Studio APIs when content leaves the repository

Studio adds delivery and operational integration points: CDN routes, conversation APIs, form submissions, webhooks, billing, usage, and workspace APIs. These are the surfaces product teams need once content becomes part of operations.

  • CDN and manifest delivery
  • Forms, submissions, and webhook dispatch
  • Conversation API for external content operations
Use Studio APIs when content leaves the repository

Deployment

Keep deployment choices open

Contentrain can stay local for a developer, run as a Nuxt Studio app, or be deployed in self-managed infrastructure. The content contract stays file-based while delivery and team workflows can move closer to production needs.

  • Local development and review UI
  • Studio SaaS path
  • Self-managed deployment path for controlled environments
Keep deployment choices open

Common questions

Which agents can use Contentrain?

Any environment that can use the Contentrain MCP server can operate the content system through bounded tools. The integration point is MCP, not a single proprietary agent.

Does the app need a CMS API at runtime?

Not always. Many apps can use generated content access at build or server time. Studio CDN and APIs are available when runtime delivery is needed.

Why separate local and remote providers?

Normalize and source patching need real source access. Remote providers are better for repository workflows where content changes are reviewed through hosted Git operations.

Next paths

Continue through the content system

Developer implementation playbook

Install, model, validate, generate, and ship runtime access.

AI agent governance playbook

Bound MCP tools, rules, review, and validation for coding agents.

Studio adoption playbook

Move from local packages into seats, review, media, CDN, and enterprise paths.

Normalize migration playbook

Move hardcoded UI copy into structured content safely.

Start local. Scale to Studio.

Build a governed content layer before content becomes product debt.

Developers can start with the MIT packages. Teams can move into Studio when review, roles, delivery, and licensing matter.

Open Studio