Server data from the Official MCP Registry
MCP server for Contentrain CMS — model, content & asset management with git sync
MCP server for Contentrain CMS — model, content & asset management with git sync
Set these up before or after installing:
Environment variable: CONTENTRAIN_REPO_PATH
Environment variable: CONTENTRAIN_BRANCH
Environment variable: CONTENTRAIN_REMOTE
Environment variable: CONTENTRAIN_AUTHOR_NAME
Environment variable: CONTENTRAIN_AUTHOR_EMAIL
Add this to your MCP configuration file:
{
"mcpServers": {
"io-github-contentrain-mcp": {
"env": {
"CONTENTRAIN_BRANCH": "your-contentrain-branch-here",
"CONTENTRAIN_REMOTE": "your-contentrain-remote-here",
"CONTENTRAIN_REPO_PATH": "your-contentrain-repo-path-here",
"CONTENTRAIN_AUTHOR_NAME": "your-contentrain-author-name-here",
"CONTENTRAIN_AUTHOR_EMAIL": "your-contentrain-author-email-here"
},
"args": [
"-y",
"@contentrain/mcp"
],
"command": "npx"
}
}
}This is a well-structured MCP server for Contentrain CMS with proper authentication, good code quality, and appropriate permissions for its purpose. The server requires API keys via environment variables and implements comprehensive validation and error handling. Only minor code quality findings were identified around broad exception handling patterns. Supply chain analysis found 4 known vulnerabilities in dependencies (1 critical, 3 high severity). Package verification found 1 issue.
Scanned 4 files · 7 findings
Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.
This plugin requests these system permissions. Most are normal for its category.
Be the first to review this server!