Plone MCP Serverofficial
A
licenseA
qualityC
maintenanceEnables AI assistants to manage Plone CMS content, search, workflows, and Volto blocks via REST API.
22
21 npm
7
MIT
Plone Dynamic Pages MCP Server
by codesyntax
Related Servers
Alternatives to Plone Dynamic Pages MCP Server
No user-submitted related servers found.
Related Servers
@cmssy/mcp-serverofficial
AlicenseBqualityBmaintenanceEnables AI agents to create and manage pages, blocks, custom models, and commerce data in Cmssy CMS, with internationalization (i18n) support.871,833 npm1MIT- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to interact with Optimizely CMS via its GraphQL and Content Management APIs, supporting dynamic content discovery, retrieval, and management.8 npm6MIT
- AlicenseCqualityAmaintenanceEnables interaction with Concrete CMS sites through the Concrete CMS REST API, allowing content management, user operations, and file uploads via natural language.377MIT
- FlicenseNot gradedqualityCmaintenanceEnables AI assistants to manage components and pages on the Journey/SameUp CMS through the CMS REST API, including listing, retrieving, and creating components with automatic authentication.-
- AlicenseAqualityCmaintenanceEnables an AI design agent to connect to any WordPress site, inspect its real rendered CSS/JS/theme, and create or update pages through the WordPress REST API and optional companion plugin routes.68 npmMIT
TDQS
B3.1/5.0
Scored across 13 tools
Disambiguation4/5
Most tools have clear, distinct purposes (e.g., get_site_definitions vs. get_dynamic_page_content). However, overlap exists between create_content and the specialized row creation tools, and between upload_file and upload_local_asset, which could lead to confusion about which to use.
Naming Consistency5/5
All tool names follow a consistent verb_noun pattern using lowercase with underscores (e.g., create_content, patch_content, search_content). The naming is uniform and predictable, with no mixing of conventions.
Tool Count5/5
The server has 13 tools, which is within the ideal 3-15 range. Each tool serves a distinct functional need—configuration, CRUD, dynamic page operations, and file uploads—without being excessive or sparse.
Completeness4/5
The tool set covers the core domain of Dynamic Page management, including creation, retrieval, update, delete, search, and specialized row operations. A notable gap is the lack of a generic get_content tool for non-DynamicPage objects, but search_content can serve that purpose, so the gap is minor.
Maintenance
ActivityMaintained
ResponsivenessNo issues