Magnolia (Enterprise Headless CMS)

Magnolia (Enterprise Headless CMS) MCP Connector for Claude

A+

Manage enterprise content via Magnolia CMS — query JCR nodes, audit template schemas, and orchestrate headless delivery.

10 tools Official Updated Jun 28, 2026 Official Vinkius Partner

Connect your Magnolia CMS instance to any AI agent and take full control of your enterprise-grade headless content and JCR repository management through natural conversation.

What you can do

  • Node Orchestration — List, retrieve, and create hierarchical JCR nodes directly from your agent, allowing for precise structural content management
  • JCR Discovery — Execute complex property-based queries using native JCR logic to identify specific content fragments and textual mappings securely
  • Template Schema Audit — Extract detailed component and page template definitions to understand which fields and properties a component expects natively
  • Delivery Layer Management — Navigate through explicitly configured delivery endpoints (e.g., pages, tours) to verify JSON mappings and content boundaries
  • Workspace Visibility — Discover and list active JCR workspaces (website, dam, configuration) to understand how your project data is distributed
  • Operational Commands — Trigger automated workspace commands including activation and publishing workflows to move content through its lifecycle
  • Cloning & Relocation — Copy or move content nodes across your repository while maintaining structural matching and delivery logic integrity

How it works

  1. Subscribe to this server
  2. Enter your Magnolia Host, Port, and Basic Auth (Base64)
  3. Start managing your enterprise repository from Claude, Cursor, or any MCP-compatible client

Who is this for?

  • Headless Developers — test delivery API results and verify JCR node properties through natural conversation without manual REST tools
  • Content Architects — audit component schemas and manage hierarchical content trees across multiple site environments efficiently
  • Digital Ops Teams — monitor workspace health and execute publishing commands across your entire Magnolia instance
jcr-repositorycontent-orchestrationdigital-experiencenode-managemententerprise-cmsapi-driven-content

10 tools expose this connector's capabilities to your AI agent.

mg.copy_delivery_node

Retrieve the exact structural matching verifying Delivery cloning logic

mg.create_cms_node

Provision a highly-available JSON Payload writing models natively

mg.wipe_cms_node

Irreversibly vaporize explicit App nodes dropping live Database bytes

mg.execute_workspace_command

Dispatch an automated validation check routing explicit Platform logic

mg.get_delivery_children

Perform structural extraction of properties driving active Branch nesting

mg.get_delivery_node

rest/delivery/ENDPOINT/PATH` returning pure JSON mappings from the JCR tree securely. Identify bounded routing spaces inside the Headless Magnolia Delivery layers

mg.get_template_schema

Enumerate explicitly attached structured rules exporting active fields

mg.list_jcr_workspaces

Identify precise active arrays spanning rented Context domains

mg.query_delivery_nodes

Retrieve explicit Cloud logging tracing explicit Payload criteria

mg.patch_cms_node

Mutate global Web CRM boundaries substituting Draft Document schemas

See how to talk to your AI agent using Magnolia (Enterprise Headless CMS).

Get the node details for path 'tours/bali' from the 'tours_v1' delivery endpoint

Retrieving node '/tours/bali'… I've fetched the JSON mapping. It contains properties like tourName: 'Exotic Bali', price: 1200, and duration: '10 days'. Would you like to see the child nodes or the associated template definition?

List all active JCR workspaces in our Magnolia instance

I've identified the following workspaces: 'website' (Site content), 'dam' (Assets), 'configuration' (System settings), 'imaging' (Image processing), and 'categorization' (Tags). Which one would you like to explore?

Show me the schema definition for template 'mgnl-news-article'

Retrieving schema for 'mgnl-news-article'… This template expects 4 main fields: 'title' (Required, Text), 'body' (RichText), 'image' (Link to DAM), and 'author' (Text). I can help you create a new node implementing this structure.

Yes. Use the `mg.get_delivery_children` tool by providing an endpoint and parent path. Your agent will retrieve exclusively the hierarchical descendants, allowing you to understand the branch nesting and property distribution accurately.

Related Connectors