Your content, from the chat: Contentrain Studio MCP Cloud is now in Claude's connectors directory

As of this week, Contentrain Studio MCP Cloud is listed in Claude's connectors directory. Open the directory in Claude, search for Contentrain, click Connect, pick a project in the browser, and Claude can read and edit that project's content. It is listed as a community connector: it went through the directory's automated review.

The listing's one-liner is "Edit your Git-backed product content, safely". This post is about that word "safely": what MCP Cloud can do, what it deliberately can't, and why there is a hosted endpoint at all when the Contentrain MCP server is MIT-licensed and runs on your laptop.

Contentrain keeps content as typed models in a Git repository: plain JSON and Markdown under.contentrain/, read by your site through a generated, typed client. Contentrain Studio is the web app on top of that repository: an AI- and Git-native CMS with roles, review and publishing.

MCP Cloud is Studio's remote MCP endpoint:

https://studio.contentrain.io/api/mcp/remote Enter fullscreen mode Exit fullscreen mode It is one URL for everyone. Which project a connection works on is decided when you sign in, not by the URL. Authentication is OAuth 2.1 with PKCE, so Claude never sees a password or a GitHub token. The directory listing points at exactly this endpoint.

Not in Claude? The same endpoint works in other MCP clients. Studio documents setup for Claude Code, ChatGPT (developer mode), Codex and MCP Inspector:

claude mcp add --transport http contentrain https://studio.contentrain.io/api/mcp/remote Enter fullscreen mode Exit fullscreen mode What Claude can do with it On a connected project Claude gets 12 tools, or 17 on a project that can use media. They are the contentrain_* tools from the open MCP package, served by Studio:

Every write is validated against your schema before anything is committed, so the model can't invent a field or break a locale. Read tools and destructive tools are annotated separately, so Claude knows which calls change something. Deleting content needs an explicit confirmation.

This is the part that makes it "safe" rather than just "convenient". Claude never writes to your main branch directly:

The connection also acts as you, with your current role. A project editor can save drafts, but only workspace owners and admins can publish. The role is checked on every call, so someone removed or demoted after connecting loses the access their new role doesn't allow.

You already have a web editor. Here is what MCP Cloud adds to it:

You can, and for a developer working alone in a repository it is often the right choice. The Contentrain MCP server is MIT-licensed, needs no account, and runs over stdio next to your code with 23 tools, including the local ones the remote endpoint never offers ( init, scaffold, scan, bulk, branch management).

The local server needs a checkout, Node and Git on the machine of whoever is editing, and an agent that runs next to that checkout. That's fine for you. It doesn't work for:

Both write the same.contentrain/ format into the same kind of repository, so you can start local and add Studio later, or use both on one project.

The local MCP server gave agents a safe way to edit content in a repository they can reach. MCP Cloud does the same for everyone else: people who live in a chat window, teams that need roles and review, and content that includes images. In both cases the result is the same, plain files and Git commits in your repository.

If you already have a Studio project, find Contentrain in Claude's connectors directory and connect it. If you don't, you can start a 14-day trial, connect a repository, and try the same prompts. The MCP Cloud docs cover the other clients, and the privacy addendum explains what MCP Cloud stores.

We'd like to know what you'd ask your content first. The comments are open.