Schema | Plone Dynamic Pages MCP Server

Plone Dynamic Pages MCP Server

Describes the environment variables required to run the server.

Name	Required	Description
`PLONE_TOKEN`	No	Bearer token for authentication.
`PLONE_COOKIE`	No	Session cookie (__ac) for authentication (alternative to token).
`PLONE_API_URL`	No	The base URL of your Plone REST API (optional if provided in tool calls).

Features and capabilities supported by this server

Capability	Details
`tools`	{}

Functions exposed to the LLM to take actions

Name	Description
check_credentials_statusA	Checks if Plone credentials (token or cookie) are provided in the arguments.
set_session_contextC	Sets the default site URL and credentials for the current session.
get_site_definitionsC	Fetches site-specific definitions (Schemas and Row Types) from Plone.
get_dynamic_page_contentB	Fetches the full JSON structure of a DynamicPage including rows and featured items.
create_contentC	Creates any content type in Plone.
create_dynamic_page_rowC	Creates a DynamicPageRow in Plone.
create_dynamic_page_row_featuredC	Creates a DynamicPageRowFeatured in Plone.
search_contentC	Searches for content in the Plone site.
patch_contentC	Updates an existing Plone object (PATCH).
delete_contentA	Deletes a Plone object. Confirmation required.
move_dynamic_page_rowC	Moves a row to a new position.
upload_fileC	Uploads a file to Plone.
upload_local_assetB	Reads a file from the local filesystem and uploads it to Plone.

Interactive templates invoked by user choice

Name	Description
No prompts

Contextual data attached and managed by the client

Name	Description
No resources

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/codesyntax/cs-dynamicpages-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server