Developer · Remote MCP server
Contentrain
Git-native content governance for AI agents - 27 deterministic MCP tools over stdio and HTTP.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.Contentrain/contentrain- Version
- 3.9.17
- Status
- Active
- Category
- developer
- Transport
- Streamable HTTP, stdio (local process)
- Package
- npm
- Published
- 2026-10-03
- Updated
- 2026-10-03
- Publisher
- Contentrain (GitHub)
- Namespace
- Namespace verified by the MCP Registry via GitHub (github.com/Contentrain) · how
- Website
- ai.contentrain.io/packages/mcp
- Repository
- github.com/Contentrain/ai (folder packages/mcp)
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://studio.contentrain.io/api/mcp/v1/{project_id}/mcp | Authorization (required, secret) |
Live check
This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.
- Checked
- Not requested: URL template placeholder
- Checked on
- 2026-10-05
Packages
| Registry | Package | Version | Transport |
|---|---|---|---|
| npm | @contentrain/mcp | 3.9.17 | stdio |
How to connect Contentrain
Contentrain is a remote MCP server: there is nothing to install. Its endpoint is https://studio.contentrain.io/api/mcp/v1/{project_id}/mcp, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.
The URL contains placeholders to fill in before connecting: {project_id}.
The registry entry declares an HTTP header for the connection: Authorization (required, secret). A secret header usually carries an API key or token issued by the service; clients that accept custom headers set it with the server's URL.
It can also run locally from a Node.js package published to the npm registry: @contentrain/mcp version 3.9.17. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Node.js; clients usually start it with npx - the usual command is npx -y @contentrain/mcp@3.9.17.
In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):
{
"mcpServers": {
"contentrain": {
"command": "npx",
"args": [
"-y",
"@contentrain/mcp@3.9.17"
]
}
}
}Derived from the registry entry, not tested here. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More developer servers
| Server | Runs |
|---|---|
| Contabo (VPS) MCP ServerContabo API (v1.0.0) as MCP tools for cloud provisioning, and management. Powered by HAPI MCP server. | Remote · HTTPLive check: ✗ no handshake |
| Container Host AIopsGoverned Docker + Portainer container-host ops: reads, RCA analyses, guarded writes. 38 tools. | Local · stdio |
| Containerization AssistTypeScript MCP server for AI-powered containerization workflows with Docker and Kubernetes support. | Local · stdio |
| Content SweepPrepaid copyright investigation and authorized enforcement, with a free agent sandbox. | Remote · HTTPLive check: ✓ handshake |
| Contest MCPLog amateur-radio QSOs to N3FJP logging software over its TCP API. | Local · stdio |
| Context - ctxt.ioShare text, markdown, code, or HTML as auto-expiring links. | Remote · HTTPLive check: ✓ handshake |
| Context AutopilotMines your Claude Code and Cursor sessions into evidence-based CLAUDE.md / AGENTS.md rules. | Local · stdio |
| Context CloudPersistent AI memory with shared team workspaces, typed knowledge chunks, and cross-tool support. | Remote & Local · SSE, stdioLive check: sign-in required |