@cmssy/mcp-server
OfficialRelated Servers
Alternatives to @cmssy/mcp-server
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityNot gradedmaintenanceProvides AI agents with full access to Strapi 5.x CMS for managing content types, entries, media, and schemas. It supports full CRUD operations, relation management, and secure authentication for comprehensive content administration.-
- AlicenseAqualityNot gradedmaintenanceEnables AI agents to manage Contentrain CMS content, models, and assets with automatic git branch synchronization across different environments. It provides standardized tools for performing CRUD operations on git-based headless CMS projects through natural language.14-
- AlicenseCqualityAmaintenanceEnables interaction with Concrete CMS sites through the Concrete CMS REST API, allowing content management, user operations, and file uploads via natural language.376MIT
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to interact directly with Strapi v5 CMS content through full CRUD operations, media uploads, and content type exploration using Strapi's Document Service API.286 npm1MIT
- FlicenseNot gradedqualityNot gradedmaintenanceEnables comprehensive management of Storyblok CMS through natural language interactions. Supports story creation and publishing, asset management, component schema updates, release workflows, and content discovery across all major Storyblok APIs.8 npm-
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to interact with Axolot CMS for content, design tokens, media, and module management with site context awareness.21 npmMIT
TDQS
Scored across 87 tools
Most tools follow clear resource+action pairs, but several clusters overlap: mark_order_paid/record_order_payment, update_block_content/patch_block_content, and list_records/list_products can be misselected. The detailed descriptions disambiguate, but with 87 tools the boundary between 'full' vs 'partial' payment and 'replace' vs 'patch' block content is not obvious from names alone.
The dominant verb_noun pattern (list_*, get_*, create_*, update_*, delete_*) is consistent and predictable across resources. Minor deviations (edit_order, mark_order_paid, patch_block_content, clear_cart_config, take_over_page_lock) break the pattern slightly but remain readable.
87 tools is far beyond the 50+ threshold and would overwhelm an agent even though the server covers multiple domains. The same surface would be more coherent split into content, commerce, and webhook-focused servers.
Most modules have solid CRUD coverage: forms, models/records, pages, and webhooks are nearly complete. Notable gaps remain: individual media assets cannot be deleted/updated, discounts can only be disabled not deleted, and there is no dedicated cart detail tool—these create dead ends for common admin workflows.