Contentrain MCP
OfficialRelated Servers
Alternatives to Contentrain MCP
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceProvides a local-first MCP server for AI-native software delivery, enabling structured specifications, human approval gates, controlled repository operations, verification evidence, review, and traceability.Apache 2.0
- AlicenseAqualityAmaintenanceMCP server for deterministic document infrastructure, enabling canonical normalization, schema validation, and grammar compilation for structured AI artifacts.4298 PyPI53Apache 2.0
- AlicenseNot gradedqualityBmaintenanceAn open-source, local-first MCP server for automated Schema.org JSON-LD generation, GA4 metric validation, /llm.txt auditing, and content stickiness analytics.MIT
- AlicenseAqualityDmaintenanceMCP server exposing content contract validators (SEO.md, PRODUCTHUNT.md, LINKEDIN.md) as tools so AI agents can verify generated content against concrete rules without maintaining linters. It provides linting and JSON-LD export tools with config and content passed as parameters, not file paths.4MIT

NomaCMS MCP Serverofficial
AlicenseBqualityDmaintenanceMCP server for NomaCMS. Manage collections, fields, content, and assets via AI agents.3937 npm1MIT- AlicenseNot gradedqualityCmaintenanceA local, stdio-based MCP server that lets AI agents create and maintain a brand project through typed tools covering identity, palette, typography, voice, assets and guide chapters, then validate it and export a self-contained, client-facing static guidelines site that can be hosted anywhere.MIT
TDQS
Scored across 23 tools
Most tools target clearly distinct resources and actions (model vs content vs vocabulary vs branch), and descriptions clarify adjacent operations like merge (cr/* branch into contentrain) vs reconcile (diverged contentrain ↔ base three-way merge). A few pairs are mildly confusable: contentrain_status vs contentrain_doctor (project state vs health checks), contentrain_describe vs contentrain_describe_format (model schema vs file-format spec), and contentrain_bulk vs contentrain_content_delete (bulk delete overlaps single delete, though a cross-reference notes status changes belong elsewhere).
All tools share a contentrain_ prefix and snake_case convention, and most follow a resource_action pattern (content_save, model_delete, branch_list, vocabulary_delete). A few deviate to bare verbs or nouns (init, scaffold, status, doctor, describe, apply), but the prefix and casing keep the set readable and predictable.
At 23 tools the surface is on the heavy side, but the domain is genuinely broad—modeling, content lifecycle, vocabulary, git branch workflow, validation, scanning, and scaffolding—and each tool covers a distinct operation. Nothing looks redundant enough to trim, though a couple of read-only helpers could be consolidated.
Coverage is strong: init/scaffold, model save/delete (with describe and status exposing models), full content save/list/delete/status plus bulk, vocabulary save/delete, validation, scan/apply, and a complete branch lifecycle (submit/merge/reconcile/branch_list/branch_delete). Minor gaps exist—no explicit model_list or vocabulary_list—but these are workable via contentrain_status and describe.