Concrete CMS MCP Server
Related Servers
Alternatives to Concrete CMS MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityAmaintenanceEnables interaction with WordPress sites through the WordPress REST API via natural language, supporting single and multi-site management, content and taxonomy operations, media uploads, and more.215 npm99GPL 3.0

@cmssy/mcp-serverofficial
AlicenseBqualityBmaintenanceEnables AI agents to create and manage pages, blocks, custom models, and commerce data in Cmssy CMS, with internationalization (i18n) support.872,404 npm1MIT- AlicenseAqualityBmaintenanceEnables comprehensive management of WordPress sites including posts, users, media, categories, tags, and site settings via the WordPress REST API.201Apache 2.0
- FlicenseBqualityDmaintenanceEnables interaction with Frappe and ERPNext sites through their REST API endpoints. It supports standard HTTP methods for performing CRUD operations and managing site data using natural language.12-
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to interact with WordPress sites through the REST API. Supports multiple WordPress sites with secure authentication, enabling content management, post operations, and site configuration through natural language.48 npmMIT
- AlicenseAqualityDmaintenanceEnables AI assistants to manage WordPress sites through natural conversation, supporting post creation, content updates, site queries, and draft-to-publish workflows via the WordPress REST API.9MIT
TDQS
Scored across 37 tools
Most tools clearly target a distinct resource and action, such as page CRUD, user management, or block operations. However, get_page_content and update_page_content could be confused with get-page-by-id and update-page-by-id, since both relate to page content, though the descriptions help differentiate them.
The dominant pattern is hyphenated lowercase verb-noun (e.g., list_files, add_group), but two tools break this with snake_case: get_page_content and update_page_content. This mixed convention makes the naming inconsistent, though the majority is predictable.
With 37 tools, this server exceeds the typical scope for an MCP server. While it covers many CMS entities (pages, files, users, groups, blocks, sites), the number feels heavy and could be consolidated; it goes beyond the 'borderline heavy' range.
The tool surface provides solid coverage for pages, page versions, blocks, files, and users with CRUD operations and content-specific tools. Obvious gaps include missing update/delete for groups and lack of site management beyond read operations, but these are minor for the core CMS domain.