No user-submitted related servers found.
Scored across 22 tools
Most tools cleanly separate resources like model, content, vocabulary, and branch, but several clusters overlap: validate/doctor both report health, merge/reconcile both handle branch merging, and apply/bulk both run dry-run batch writes. The descriptions help clarify boundaries, yet an agent could still hesitate when choosing between these related operations.
All tools share the contentrain_ prefix and use snake_case, which provides a consistent namespace. However, the structure is mixed: resource-action names like content_save and branch_delete sit alongside bare-verb names like describe, init, validate, merge, scan, and doctor, so the naming pattern is not fully predictable.
At 22 tools, the server is on the heavier end but still reasonably scoped for a CMS platform that spans content, models, vocabulary, git branches, validation, and code scanning. Each tool addresses a distinct workflow area, though a few could potentially be consolidated.
The toolset covers the core content lifecycle well: content save/delete/list, model save/delete, vocabulary save/delete, branch management, validation, and scaffolding are all present. Minor gaps exist—no dedicated vocabulary_list or single-content get, and PR creation is delegated to the platform—but agents can work around these using status and content_list.
